Claude Prompts: 30 Templates for Solopreneurs (2026 Guide)

Good claude prompts turn Claude from a generic chatbot into a real business assistant. This guide gives you 30 ready-to-copy templates for solopreneurs, plus the four rules that make any prompt work better. You will find prompts for marketing, sales, admin, strategy, and automation. Copy one, swap in your own details, and use it today.

Running a one-person business means you wear every hat. You write the newsletter, chase invoices, plan the roadmap, and answer support emails, often in the same hour. Claude can take real work off your plate for each of those tasks, but only if you ask it the right way. A vague prompt gets a vague answer. A specific prompt gets something you can actually use.

Nearly 60% of small businesses now use AI tools in some part of their operations, according to the U.S. Chamber of Commerce (2026). Prompting well is the skill that decides whether that time actually gets saved.

Key Takeaways

• Good claude prompts give Claude a role, a task, context, and a format. Skip any of these and the output gets vaguer.
• The 30 templates below cover five jobs: content and marketing, customer and sales messages, admin and operations, research and strategy, and coding and automation.
• Save your best prompts inside a Claude Project so you reuse them instead of rewriting them every time.
• Pair a prompt with an automation tool like n8n when you run the same task on a schedule.
• Claude Code uses a different prompting style than Claude chat. Use plain, step-based instructions there instead of persona-based prompts.

Want more prompts and workflow breakdowns like this one? Join the newsletter for a short weekly email, no fluff, just what’s working.

What Makes a Good Claude Prompt

Most disappointing Claude answers trace back to one missing ingredient in the prompt, not a limit in the model. Anthropic’s own prompt engineering documentation lays out the techniques that move the needle most: being clear and direct, giving Claude a role, providing examples, and structuring longer prompts with plain tags.

Four elements turn a weak prompt into a strong one:

A role. Tell Claude who to be for this task: “You are a copywriter for a boutique skincare brand” gives it a voice and a standard to write to.

A clear task. State exactly what you want, not the general topic. “Write three subject lines” beats “help with email marketing.”

Context. Paste in the actual details Claude needs: your product, your audience, your past examples, your constraints. Claude cannot read your mind or your website unless you give it the text.

A format. Tell Claude how to structure the output: a numbered list, a table, a short paragraph, a specific word count. This alone cuts most of the back-and-forth editing.

Every template below builds in these four pieces so you can copy, paste, and fill in the brackets.

Here’s the difference in practice. A weak prompt: “Write me a marketing email.” Claude has no role, no product, no audience, and no format to work from, so it guesses at all four and hands back something generic. A strong version of the same request: “You are an email copywriter for a candle brand. Write a 150-word promotional email for our new autumn scent, aimed at repeat customers, with a subject line and one clear call to action.” Same task, four extra pieces of information, and a far more usable result on the first try.

This pattern holds for almost every business task, not just writing. Even a strategy question improves once you frame Claude’s role and give it real numbers instead of asking it to work in the abstract.

The 30 Claude Prompts for Solopreneurs, Organized by Job

These claude prompts are grouped into five categories that match the actual jobs a solopreneur juggles in a normal week. Copy the prompt text, replace anything in brackets with your own details, and paste it into a new Claude chat.

Content and Marketing Prompts

1. Blog post outline. “You are a content strategist. Write a blog outline for an article titled ‘[title]’ aimed at [audience]. Include an intro hook, five H2 sections, and a closing call to action.” This gives you a structure before you write a single sentence.
2. Email subject lines. “You are an email copywriter. Write 10 subject lines for an email about [topic]. Keep each under 50 characters and avoid spammy words like ‘free’ or ‘guaranteed’.” Short, testable options beat one guess.
3. Social post repurposing. “Turn this blog post into five short LinkedIn posts, each under 150 words, each with a different angle: [paste post].” One asset becomes a week of content.
4. Product description. “You are an ecommerce copywriter. Write a 100-word product description for [product] that highlights [top three benefits] and ends with a clear next step.” Feed it your own bullet points, not a blank slate.
5. Newsletter draft. “Write a 300-word newsletter for solopreneurs about [topic]. Open with a specific story or example, then give three practical takeaways.” Specific beats generic every time.
6. Ad copy variations. “Write five versions of a Facebook ad for [product], each testing a different hook: curiosity, fear of missing out, social proof, a direct offer, and a question.” Running variants is how you find what actually converts.

Customer and Sales Prompts

7. Cold outreach email. “Write a 75-word cold email to [role] at [type of company] introducing [your service]. Reference a specific pain point: [pain point]. End with a one-line ask, not a full pitch.” Short outreach gets read; long outreach gets deleted.
8. Objection handling. “A prospect said: ‘[objection]’. Write three different responses I could use on a sales call, each under 40 words.” Practicing responses in advance means you never freeze on a call.
9. Follow-up sequence. “Write a three-email follow-up sequence for a prospect who went quiet after a proposal. Space them one week apart and increase urgency slightly with each one.” Most deals die from lack of follow-up, not lack of interest.
10. Customer complaint response. “A customer wrote: ‘[complaint]’. Write an empathetic response that acknowledges the issue, offers a specific fix, and keeps the tone calm and professional.” Claude is genuinely good at defusing tense messages.
11. Testimonial request. “Write a short, low-pressure email asking a happy customer for a testimonial. Include two example questions I could ask them to answer instead of leaving it open-ended.” Specific questions get better testimonials than “any feedback?”
12. Pricing page copy. “Write three plan descriptions for a pricing page: [plan names and prices]. Keep each under 50 words and lead with the outcome, not the feature list.” Outcomes sell better than feature lists.

The 30 Claude Prompts, Continued: Admin, Research, and Automation

Admin and Operations Prompts

13. Meeting notes to action items. “Turn these raw meeting notes into a clean list of action items, each with an owner and a rough deadline: [paste notes].” This alone saves most solopreneurs an hour a week.
14. Invoice reminder email. “Write a polite but firm payment reminder email for an invoice that’s [X] days overdue. Keep it under 80 words and include a specific payment link placeholder.” Firm and short works better than long and apologetic.
15. Standard operating procedure. “Turn this rough process description into a numbered SOP a new hire or contractor could follow without asking questions: [paste process].” Documenting once saves re-explaining forever.
16. Job post draft. “Write a job post for a [role] at a small business. Include responsibilities, three must-have skills, and a short line about company culture: [details].” A clear post filters out bad-fit applicants early.
17. Contract summary. “Summarize this contract in plain English, highlighting payment terms, deadlines, and any clause I should review with a lawyer: [paste contract].” Not a substitute for legal advice, but a fast first pass.
18. Weekly priority list. “Given these 15 open tasks, help me sort them into ‘this week,’ ‘next week,’ and ‘not urgent,’ based on impact and deadline: [paste tasks].” Claude is a useful second opinion on your own priority calls.

Research and Strategy Prompts

19. Competitor comparison. “Compare [my product] against [competitor] on price, features, and target audience. Present it as a table and flag one clear differentiation angle.” A table format forces a clean, scannable comparison.
20. Market research summary. “Summarize the current state of the [industry] market for a solopreneur audience: main trends, biggest pain points, and one underserved niche.” Good for a fast gut-check before you commit time to an idea.
21. SWOT analysis. “Run a SWOT analysis for [my business idea], written for someone with no business degree. Keep each section to three bullet points.” Plain language beats jargon when you’re the one acting on it.
22. Pricing strategy. “Given these costs and this target market: [details], suggest three pricing models with pros and cons for each.” Seeing the tradeoffs laid out beats guessing at a single number.
23. Content calendar. “Build a four-week content calendar for [platform] around the theme of [topic], with one post idea per day and a mix of formats.” A full calendar in minutes, not an afternoon.
24. Customer persona. “Build a customer persona for [product] based on these details: [details]. Include their main frustration, what they’ve already tried, and what would make them buy today.” A sharper persona means sharper copy everywhere else.

Coding and Automation Prompts

25. n8n workflow logic. “I want an n8n workflow that does [task]. Walk me through the nodes I’d need in order, and flag any step that needs an API key.” Useful groundwork before you open the n8n canvas. See our guide on connecting Claude to n8n for the full setup.
26. Spreadsheet formula. “Write a Google Sheets formula that does [task], and explain what each part of the formula does in plain English.” No more copy-pasting formulas you don’t understand.
27. Data cleanup script. “Write a short Python script that takes this messy CSV structure and cleans it up: [describe columns]. Add comments explaining each step.” Even non-coders can run a script Claude explains line by line.
28. Automation debugging. “This automation is supposed to [expected behavior] but instead it [actual behavior]. Here’s the relevant config: [paste]. What’s the most likely cause?” A good first triage step before you dig in manually.
29. Email triage rules. “Design a set of rules for sorting incoming email into ‘urgent,’ ‘can wait,’ and ‘ignore,’ based on sender and subject patterns I’ll describe: [describe patterns].” This is the same logic behind our n8n email triage automation build.
30. Website copy audit. “Review this homepage copy and flag anything unclear, too long, or missing a clear next step: [paste copy].” A second set of eyes, on demand, at any hour.

How to Customize These Prompts for Your Business

Every template above is a starting point, not a finished script. Swap the bracketed placeholders for your real product, audience, and numbers. The more specific your input, the more useful Claude’s output gets.

Save the prompts you use most inside a Claude Project. Projects keep your brand voice, past examples, and key documents in one place, so you stop re-explaining your business every time you open a new chat. Our guide on how to use Claude Projects walks through setup in five steps.

If you’re new to Claude generally, start with the basics of what it’s good at and where it fits into a small operation. Our Claude for small business guide covers that ground before you go deeper into prompting.

Treat your first draft of a prompt as a starting point, not a final answer. If the output misses the mark, don’t start over. Tell Claude what’s wrong in plain terms: “make this shorter,” “this doesn’t sound like our brand,” or “add a specific number here.” Claude keeps the conversation in mind, so a quick correction almost always gets you closer than writing a brand-new prompt from scratch. Over a few uses, you’ll notice which of your own added details actually change the output and which ones don’t matter, and your prompts get shorter and sharper as a result.

Combine Claude Prompts With Automation

Typing a prompt by hand works fine for one-off tasks. For anything you do weekly or daily, connect Claude to a tool like n8n so the prompt runs on a schedule or a trigger, without you opening a chat window.

A support-inbox triage prompt, for example, becomes far more useful running automatically every time a new email arrives than typed fresh each morning. That’s exactly the kind of workflow covered in our Claude and n8n integration guide, which walks through connecting Anthropic’s API into an automation stack step by step.

A good rule of thumb: if you’ve pasted the same prompt into Claude more than three times this month, it’s a candidate for automation. Meeting-notes cleanup, invoice reminders, and email triage are the three templates above that solopreneurs tend to automate first, because the input arrives on its own schedule and doesn’t need a human to kick it off.

Claude Prompts vs. Claude Code Prompts

The templates above are written for Claude’s chat interface: Claude.ai, the desktop app, or the API through a tool like n8n. Claude Code, Anthropic’s coding-focused tool, rewards a different style.

In Claude chat, a role and a persona help. In Claude Code, plain and literal instructions work better: “read this file, find the bug on line 40, and fix it” beats “you are a senior engineer, please assist.” Claude Code also responds well to breaking a big task into small, checkable steps, since it can run commands and check its own work as it goes, unlike a chat window that only ever gives you text back.

If you’re a solopreneur who occasionally touches code, website tweaks, or spreadsheet macros, it’s worth knowing both styles exist before you get frustrated with one tool for not behaving like the other. If you’re deciding which coding assistant fits your workflow, our Cursor vs Claude Code comparison breaks down the practical differences.

Frequently Asked Questions

What is the best way to write a Claude prompt?

Give Claude a role, a specific task, real context about your situation, and the exact format you want back. Vague prompts get vague answers; specific prompts get usable ones.

Are Claude prompts different from ChatGPT prompts?

The core structure is similar, but Claude tends to respond well to plain tags for organizing long prompts and to explicit examples of the output you want. Both models improve sharply with more context and a clear format request.

How many prompts can I save in Claude?

There’s no fixed cap on saved prompts, but Claude Projects give you a practical place to store your most-used ones alongside reference documents, so you’re not hunting through old chats to find them.

Can I use these prompts with the free version of Claude?

Yes. All 30 templates work on Claude’s free tier. Higher usage limits and longer context come with a paid plan, but the prompting technique itself doesn’t change.

Do I need to know how to code to use the automation prompts?

No. The n8n and spreadsheet prompts are written so Claude explains each step in plain English. You can run them without a technical background, though a basic grasp of your tools helps.

Why does the same prompt sometimes give different results?

Claude, like any language model, varies its wording slightly between runs even with an identical prompt. The core content should stay consistent if your prompt is specific. If answers swing wildly, that’s usually a sign the prompt is too vague and needs more context or a tighter format request.

Sources: U.S. Chamber of Commerce, “Empowering Small Business: The Impact of Technology on U.S. Small Business,” 2026. Anthropic, “Prompt engineering overview,” Claude Platform Docs, 2026.