Claude Prompt Builder

How to use the prompt builder

1. Choose a task. The templates cover the jobs owners and office teams hand to Claude most often: follow-up emails, review replies, proposals, descriptions, social posts, SOPs, job posts, business plan sections, meeting summaries, and plain-English explanations.
2. Fill in the blanks with real details. The placeholder text shows the kind of detail that helps. Rough notes are fine; Claude is good at turning messy input into clean output. What it can’t do is guess facts you haven’t given it.
3. Pick a tone. “Warm and professional” suits most customer-facing writing. Use “direct and brief” for internal notes and “formal” for lenders, legal, or official letters.
4. Copy it into Claude. Open Claude, paste the prompt, and read what comes back. If something’s off, reply with what to change rather than starting over: “shorter,” “less formal,” or “you got the date wrong, it’s the 14th.”

What makes these prompts work

Every template follows the same four-part structure. Once you see it, you can write your own prompts for any task.

• Context. Who you are, who the output is for, and the situation. “Write a follow-up email” gets a generic email. “Write a follow-up email to Dana, operations manager at Brightline, after our quote meeting” gets something you can send.
• The raw material. Your notes, the review text, the facts about a property, the steps of a process. This is the part most people skip, and it’s the part that matters most.
• The format. Length, sections, and structure. Claude follows formatting instructions well, so telling it “a subject line under 8 words, then a ‘What we agreed’ list” saves you from reformatting later.
• The rules. What it must not do. The most important rule for business writing is not to invent facts. Each template also has task-specific rules, like describing a property rather than who should live in it, or keeping a review reply free of private customer details.

Before and after: the same request, two ways

The one-line version: “Write a follow-up email to my client.” Claude has nothing to work with, so it produces a polite, generic email with placeholders for every detail, which you then rewrite from scratch.

The builder version: the same request, plus who the client is, your actual meeting notes, what you want them to do next, the format (subject line, what we agreed, next steps with owners and dates), a tone, and the rule not to invent anything. Now Claude writes the email you would have written, flags the one date you forgot to mention, and you send it after a quick read.

The second prompt takes a minute longer to fill in and saves ten minutes of rewriting. That trade is the whole idea behind the builder.

The [CONFIRM] guardrail, explained

The most common problem with AI-written business documents isn’t bad writing. It’s a specific, plausible detail that’s wrong: a deadline nobody agreed to, a price you never quoted, a feature the product doesn’t have. These slip through because they sound right.

The guardrail line tells Claude to leave a visible marker, like [CONFIRM: install date], wherever it would otherwise have to guess. Instead of hidden errors, you get a short list of blanks to fill in before you send. It’s the single most useful line you can add to any prompt that produces something a customer, lender, or employee will read.

Tips by type of task

Emails and customer messages

Paste the actual thread or your notes rather than describing them. Tell Claude what you want the reader to do next. For anything sensitive, like a complaint or a price increase, ask for two versions with different tones and pick the one that sounds like you.

Proposals, plans, and documents

Give Claude the numbers and let it write around them. Ask it to list the weakest points a skeptical client or lender would question; it’s often more useful than the draft itself. For longer documents, build them one section at a time, as our guide to writing a business plan with Claude shows.

Marketing and descriptions

List features as plain facts and let Claude make them readable. Tell it not to add features you didn’t list. For real estate, housing, and job ads, describe the property or role, never the kind of person you want, which keeps you on the right side of fair housing and hiring rules.

Processes and internal documents

Describe how you actually do the task, in whatever order it comes to mind. Ask Claude to point out gaps a new person would trip over. An SOP is only useful if someone else can follow it without asking you.

Common mistakes

• One-line prompts. “Write a proposal for a website” can only produce a generic proposal. The fields in the builder exist to stop this.
• Accepting the first draft. The first answer is a starting point. One or two short follow-up instructions usually get you to something you’d send.
• Not checking facts. Read every name, date, number, and promise before anything goes out, even with the guardrail on.
• Pasting sensitive data. Leave out account numbers, Social Security numbers, health information, and anything your clients wouldn’t want shared.

From prompt to habit

If you use the same prompt every week, stop copying and pasting it. Put your business background in a Claude Project so every conversation starts with it, or turn the prompt into a skill that Claude uses automatically. Our Claude skill builder does that with a form, and the guide to Claude skills explains how they work. To learn the broader approach, the free Claude Cowork course walks through real workflows built for owners and operators.

More free tools