Skip to content

Claude Code for Non-Developers: 15 Real Use Cases by Job

Claude Code for non-developers: 15 concrete use cases for marketing, sales, operations, finance and content, each with a prompt you can copy and run today.

By Yotam DahanUpdated 11 min readClaude Code

On this page
  1. Before you try any of these
  2. The 15 use cases at a glance
  3. Marketing
  4. Sales
  5. Operations
  6. Finance
  7. Content
  8. Connect the tools you already use
  9. A safety checklist for non-developers
  10. What to do next

Claude Code is useful for non-developers because most office work lives in files: spreadsheets, PDFs, documents, folders of photos, exports from the tools you already use. You describe the result you want in plain English, and Claude Code reads those files, does the work and saves the output back into the same folder. Below are 15 use cases grouped by job, each with a prompt you can paste and adapt.

None of these use cases require you to write code. They do require two habits: describing the finished result clearly, and checking that result before you rely on it, so each entry ends with what to check.

Before you try any of these

How to run any use case on this page
  1. Copy the files

    Put copies in a new folder, one folder per task

  2. Open Claude Code there

    In the terminal or the desktop app's Code tab

  3. Plan first

    Use plan mode for anything that changes many files

  4. Fill the brackets

    Replace every [PLACEHOLDER] with your own details

In the terminal, press Shift+Tab until the status line says plan mode. In the desktop app, pick Plan from the mode selector next to the send button, and you see the plan before a single file changes.

The 15 use cases at a glance

#JobUse caseYou provideYou get back
1MarketingCompetitor snapshotNames or website addressesA comparison with source links
2MarketingMonthly ad reportCSV exports from your ad platformsOne table plus a written summary
3MarketingOne article, five formatsA blog post or transcriptSocial posts and a newsletter paragraph
4SalesCRM cleanupA contact exportA deduplicated file and a list of issues
5SalesFollow-up draftsYour call notesOne email draft per call
6SalesQuote from your price listA price list and a client requestA quote with the math shown
7OperationsFolder tidy-upA copy of a messy folderRenamed, sorted files and a log
8OperationsProcedure from a voice noteA transcriptA step-by-step procedure
9OperationsSmall internal toolA calculation your team repeatsA one-file tool that runs in a browser
10FinanceInvoices to a spreadsheetA folder of PDF invoicesOne spreadsheet with a check column
11FinanceSpending by categoryA bank exportA categorized file and a summary
12FinanceSupplier quote comparisonTwo to five quotesA side-by-side comparison
13ContentContent calendarThemes, channels and datesA calendar file you can import
14ContentTranscript to articleA video or podcast transcriptAn article and show notes
15ContentLanding pageYour offer and detailsA page you can publish

Marketing

1. Competitor snapshot

Claude Code can search the web and read public pages, then save what it finds as a file you keep.

Competitor snapshot
Research these competitors: [NAMES OR WEBSITE ADDRESSES]. For each, find their main offer, their starting price if it is published, who they target, and how they describe themselves in one sentence. Save a comparison table to competitors.md with a source link next to every fact. Write "not found" instead of guessing.

Check: open a handful of the source links. Prices and offers change often, so put the date at the top of the file.

2. Monthly ad report from CSV exports

Monthly ad report
The files in /exports are this month's ad reports from [PLATFORMS]. Combine them into one table by campaign with spend, clicks, leads and cost per lead, and save it as ad-report.csv. Then write a five-bullet summary in summary.md comparing it with @last-month.csv. Show the formula you used for every calculated column.

Check: compare total spend with each platform's own dashboard. If you want a visual, ask for a simple chart page you can open in your browser.

3. One article, five formats

One article, five formats
Read @article.md. From it, write one LinkedIn post, three short social captions and a newsletter paragraph, in the tone described in @voice.md. Keep every claim from the article and add no new facts or statistics. Save each piece as its own file in /drafts.

Check: read every draft for claims the article doesn't support. The guide to Claude Code for marketers covers full marketing workflows, from briefs to reporting.

Sales

4. Clean up a CRM export

CRM cleanup
contacts.csv is an export from our CRM. Create contacts-clean.csv: merge exact duplicates, write phone numbers in the format [FORMAT], split full names into first and last name columns, and add a column flagging rows with no email. Don't delete any rows. Then tell me how many rows you merged and how many you flagged.

Check: the original row count should equal the clean row count plus the merged rows.

5. Follow-up drafts from call notes

Follow-up drafts
/notes has my notes from this week's sales calls, one file per call. For each call, draft a short follow-up email that thanks them, recaps what they told me in their own words, and proposes the next step we discussed. Save the drafts in /followups. Don't send anything, and flag any call where the next step is unclear.

Check: make sure no draft promises a price, date or feature you didn't agree to.

6. A quote from your price list

Quote from a price list
Using @price-list.csv and the client request in @request.txt, prepare quote-[CLIENT].md with line items, quantities, prices, subtotal, tax at [RATE]% and total, plus our standard terms from @terms.md. Show the math for every line. List anything the client asked for that isn't on the price list under "needs pricing".

Check: recalculate the total yourself the first few times. Once the numbers are right, ask for a PDF version for the client.

Operations

7. Tidy a messy folder

Claude Code can look at images and read PDFs (tools reference), so it can name files by what is inside them, not only by their current names.

Folder tidy-up
/inbox is a copy of my scanned documents and photos. Propose a folder structure and a naming pattern like YYYY-MM-DD_type_description, and show me the plan for the first 10 files before you move anything. After I approve, rename and sort everything, and save a log of every old name and new name in rename-log.csv.

8. A procedure from a voice note

Procedure from a voice note
@transcript.txt is me explaining how we onboard a new client. Turn it into onboarding-procedure.md: numbered steps, who does each step, which tools they use, and a checklist at the end. Keep my wording where it is specific, and list anything that sounded unclear as questions for me.

Check: hand the procedure to the person who actually does the job and ask what is missing.

9. A small internal tool

One-file pricing tool
Build calculator.html, a one-file page our team can open in a browser to price [SERVICE]. Inputs: [LIST THE INPUTS]. Use the pricing rules in @pricing-rules.md and show a total that updates as you type. It must work without an internet connection or any accounts. Include three test cases from the rules and show that each gives the right total.

Check: run your own test cases, worked out by hand, before anyone uses it with a customer. Owners who want more operations ideas will find them in Claude Code for small business.

Finance

10. Invoices into one spreadsheet

Invoices to a spreadsheet
/invoices contains supplier invoices as PDFs. Extract the supplier, invoice number, date, net amount, tax and total from each into invoices.csv, one row per invoice. Add a column with the file name, and a "check" column that marks any invoice where net plus tax doesn't equal the total or a field was unreadable.

Check: compare a sample of rows with the PDFs. Claude Code reads short PDFs whole, but documents over 10 pages need a free tool called poppler (brew install poppler on a Mac), and it tells you if that is missing.

To make this run every month without you, see how to automate invoices with AI.

11. Spending by category

Spending by category
transactions.csv is a bank export for [PERIOD]. Add a category column using these categories: [LIST]. Put anything you are unsure about under "Review". Then write summary.md with total spend per category and the 10 largest transactions. Don't change any original amount or date.

Check: the category totals must add up to the total of the export.

12. Compare supplier quotes

Supplier quote comparison
/quotes has [NUMBER] quotes for [WHAT YOU ARE BUYING]. Build a comparison table in quotes-compared.md with unit price, total, delivery time, payment terms, warranty and exclusions. Highlight differences in what is included, not only in price, and quote the exact line from each document for every number.

Check: the quoted lines make spot-checking fast, so check a few against the documents before you negotiate.

Content

13. A content calendar you can import

Content calendar
Create a content calendar for [MONTH] as calendar.csv with the columns date, channel, topic, format, hook and call to action. Use the themes in @themes.md, plan [NUMBER] posts a week on [CHANNELS], and skip [DATES]. Keep each hook under 12 words.

Check: a CSV opens in any spreadsheet app, and many scheduling tools can import one. Read the hooks out loud before you schedule anything.

14. Transcript to article and show notes

Transcript to article
@episode-12.txt is the transcript of my podcast episode. Write a blog article of about 1,000 words that keeps my examples and opinions, then show notes with five key points and the timestamp where each one comes up. Don't add facts that aren't in the transcript.

Check: search the transcript for each timestamp, and cut anything that sounds like you but isn't something you said.

15. A landing page for an offer

Landing page for an offer
Build a one-page landing page for [OFFER] aimed at [AUDIENCE]: a headline, three benefits, what's included, the price, an FAQ and a sign-up button that links to [LINK]. Use only the facts in @offer.md. Ask me questions first, and plan the sections before you write any files.

Check: click every button and read every claim against your offer. Publishing it is a separate step, covered in the guide to building a website with AI.

Connect the tools you already use

Files in a folder are only the start. Four features let these use cases reach further:

Ways to take these use cases further

Connectors

Sign in with a claude.ai account and the connectors you add on claude.ai, including Anthropic-hosted ones for Gmail, Google Calendar and Microsoft 365, appear in Claude Code automatically (connector docs).

Your browser

With the Claude in Chrome extension, Claude Code works in sites you're logged into and hands control back at login pages and CAPTCHAs.

Skills

Once a prompt works well, save it as a skill and rerun it by name. Browse ready-made ones in our Claude Skills directory.

Schedules

The desktop app can run a task on a schedule on your machine, and cloud routines (a research preview) run while it's off.

Connectors are built on MCP, the open standard for plugging AI tools into other apps; our explainer on what MCP is and the MCP directory show what is available. For a larger library of tested prompts and multi-step workflows, see the Claude Code prompts and templates.

A safety checklist for non-developers

0 of 7 done

Quick check0 of 2 correct

Before running the folder tidy-up, what should you do first?

The invoice spreadsheet looks right. What should you still check?

What to do next

Pick the one use case that would save you the most time this month, prepare a folder with copies of the files, and run the prompt in plan mode first. Check the result line by line the first time, then decide whether it is worth turning into a habit or a skill. If you want to learn this properly rather than prompt by prompt, the Claude Code course covers setup, prompting habits that catch mistakes early, and real builds such as an agent that sends your invoices to your accountant.

Use case adapter sheet

Fill-in prompt skeletons for all five job areas, a checklist for preparing your files, and three questions to pick which use case to try first.

Enter your email and the full section opens right here. You also get a free lesson from the course.

No spam. One click to unsubscribe. We use your email to send you the course and AI tips.

Frequently asked questions

Do I need to use the terminal for these tasks?

No. Every use case here also works in the Code tab of the Claude desktop app, where you pick a folder and type your request in a normal text box. The terminal adds a few extra commands, but none of these tasks depend on them.

Which Claude plan do I need for these use cases?

Any paid plan includes Claude Code, so Pro is the cheapest way to try them. If you run large batches every day and keep hitting your limits, a Max or Team plan gives you more room, since your usage is shared with your Claude chats.

Can Claude Code work with Excel files and PDFs?

Yes. It reads PDFs and images directly, and when you sign in with a claude.ai account it also loads Anthropic's built-in document skills, such as pdf and xlsx. For data from other apps, a CSV export is usually the most reliable starting point.

Can Claude Code send emails or post on social media for me?

It can act inside apps you connect, through connectors or the Claude in Chrome extension, and your permission mode decides what it may do without asking. For anything a customer will see, have it prepare drafts and do the sending yourself until you trust the process.

How is this different from asking Claude in the chat app?

Chat gives you an answer to copy. Claude Code opens the files in your folder, does the work and saves the result there, which matters once a task involves many files or several steps.

Keep reading