Claude Prompts for Business: 15 Ready-to-Use Templates for CPAs, Lawyers, and Consultants

The best Claude prompts for business all do the same job: they give the model the context a competent colleague would need before drafting. Who's reading. What they need to decide. The tone, constraints, and what to leave out. The 15 templates below are built around that for CPAs, attorneys, and consultants, with bracketed variables you swap in. Each gets you roughly 80% of the way to a usable draft. The last 20%, the part your client actually pays for, stays yours.

I'll admit I was a skeptic on prompt templates for a long time. They felt like training wheels, the kind of thing you'd outgrow in a week. I changed my mind after noticing I was burning 20 to 30 minutes rebuilding the same setup every time I drafted a client memo from scratch. A template isn't a crutch; it's pre-flight. It automates the setup so your attention goes to judgment, not boilerplate.

Here's why that matters more after 45, not less. If you've got two or three decades of practice behind you, you already know what a good client update or a clean negotiation memo looks like. That knowledge is exactly what makes these templates work, because you can spot the 20% Claude got wrong in seconds. A younger user can't. Your experience isn't a reason to skip the tool. It's the reason Claude produces something you can send after a five-minute edit, and something a junior would still be revising an hour later.

Each template gives Claude the context it needs to produce something you can use rather than something you rewrite from zero. They're grouped by profession, with variables in brackets so you can see exactly where your specifics go. For each one, there's a short note on what to verify first. Claude drafts; you own it. That's not a disclaimer. It's the whole point.

If you want the broader foundation for using Claude in professional work, the Claude AI tutorial for professionals covers the underlying principles. This post is the practical companion: the templates you reach for when there's a deliverable in front of you and 45 minutes to turn it around.

Two Standing Rules Before You Start

Two standing rules apply to every template here, every time.

Rule one: no client documents, no PII, no tax records, no identifying information in the prompt. You can describe a situation in general terms, "a client with a multi-state S-corp and a pending IRS notice on payroll tax deposits," without uploading the notice or naming the client, the EIN, or account numbers. Claude can help you structure a response, draft talking points, and organize your thinking without ever seeing the underlying document. If you want the deeper version of why this matters, The Fiduciary Firewall covers the confidentiality framework in full.

Rule two: treat every output as a first draft, never a final product. Claude doesn't know your jurisdiction's current case law, your firm's house style, your client's specific facts beyond what you gave it, or whether the regulatory ground shifted last Tuesday. This is the 80/20 Rule for a leveraged practice: the templates get you an 80% draft in minutes. The last 20%, the part that requires your judgment and protects your client, is your job, and it's what you're paid for.

When to Use a Template (and When to Skip It)

Before the templates themselves, a quick decision aid. The fastest way to waste time is to use Claude for a task you'd finish faster by hand. My rule: if you'd normally bill at least 0.3 hours to think and structure the work, it's worth running through a template. Here's how I sort it.

CPA and Finance Templates

The five below address the work that eats disproportionate time in most accounting and finance practices. A typical pattern I see: a 52-year-old FP&A lead spends an afternoon turning numbers into a deck for the board, a task Claude can rough out in 10 minutes if you frame the request correctly. For how these tools apply across a practice, the AI tools for accountants overview is worth reading alongside this.

Template 1: Client Plain-English Summary

Use case: Translate a complex tax or financial situation into language your client can actually read and act on.

Template:

"I need to explain the following situation to a client in plain English. The client is [describe client: e.g., 'a business owner with no accounting background' or 'a physician who understands business basics but not tax mechanics']. The situation is: [describe the technical issue in your own words, no client names, no identifying details]. The key point they need to understand is [state the core conclusion]. The decision or action they need to take is [state what you need them to do]. Write a 2–3 paragraph summary that's clear, accurate, and professional. No jargon. Don't be condescending. Assume the reader is intelligent but not a tax professional."

What good output looks like: A tight, readable explanation that leads with the client's situation, states the implication clearly, and ends with a specific action. No hedging sentences. No technical terms without an immediate plain-language translation.

Always check: Accuracy of the technical description. Claude writes fluently, so confirm it wrote correctly. Verify any specific numbers, rates, or deadlines you included before the summary goes out.

Template 2: Variance Explanation Memo

Use case: Turn a set of financial variances into a narrative explanation suitable for a management report or board communication.

Template:

"Write a variance explanation memo for the following results. Period: [month/quarter/year]. Context: [brief description of the business unit or entity]. Variances to explain: [list each variance, e.g., 'Revenue: $2.1M actual vs. $2.4M budget, unfavorable $300K', use generalized or anonymized figures]. Known drivers: [list what you know: pricing pressure, volume shortfall, timing difference, one-time item, etc.]. Tone: [e.g., 'factual and neutral for a board audience' or 'direct and solution-oriented for an operations review']. Format: short narrative paragraphs by variance category. Don't editorialize beyond the facts I've provided."

What good output looks like: Organized paragraphs by variance, with clear causal language and no speculation beyond the drivers you supplied.

Always check: That the narrative matches the numbers exactly. Claude can flip a favorable/unfavorable direction or misstate a causal relationship if your input was ambiguous.

Template 3: Engagement Letter Opener

Use case: Draft a professional, appropriately-toned opener for a new client engagement letter.

Template:

"Write the opening two paragraphs of an engagement letter for an accounting/advisory engagement with these parameters. Client type: [individual, business entity, family office, etc.]. Services: [describe in general terms, tax compliance, financial review, advisory, etc.]. Tone: [formal and conservative / professional but warm / concise and transactional]. The firm's style emphasizes [any specific notes, e.g., 'brevity and directness' or 'relationship context before scope']. This is a [new client / returning client / expanded scope engagement]. Don't include scope of work, fee, or limitation of liability language, those get added separately."

Always check: That the tone actually matches the relationship. Claude will produce a competent opener. You'll know whether it sounds like your firm.

Template 4: IRS Notice Response Structure

Use case: Organize a response to a client IRS notice, structure only, no substantive tax advice from Claude.

Template:

"A client has received an IRS notice regarding [describe the general nature without identifying information, e.g., 'a proposed adjustment to Schedule C income for a prior year']. I need to structure a professional response letter. The response will address: [list the points you intend to make, e.g., 'factual disagreement with the proposed adjustment,' 'supporting documentation being provided,' 'request for 60-day extension']. Tone: [cooperative and factual / firm and assertive / neutral]. Draft the structure and a suggested opening paragraph. I will personally draft and verify all substantive tax positions and factual assertions before this goes out."

Your job: The entire substantive content. Claude is organizing structure and drafting professional language. The actual tax positions, facts, and regulatory citations are yours to supply and verify.

Template 5: Quarterly Review Talking Points

Use case: Build a structured agenda and key talking points for a client quarterly review meeting.

Template:

"Build a structured set of talking points for a [60/90]-minute quarterly review with [describe client type, 'a high-net-worth individual with a business interest and investment portfolio' or 'a manufacturing company CFO']. Key topics: [list 3–5]. Items requiring a decision or client action: [list any]. Open items carried forward from last quarter: [list if relevant]. Tone of the meeting: [e.g., 'routine and efficient' or 'there are some difficult conversations about underperformance']. Format as a structured agenda with 2–3 talking-point bullets per section."

Always check: That every item requiring client action is clearly flagged. Claude organizes well, so verify nothing decision-critical is buried mid-section.

Attorney Templates

These five address the high-volume, time-intensive writing that consumes attorney hours without necessarily requiring attorney judgment: client updates, internal case summaries, and structured thinking on negotiation and strategy. The AI tools for lawyers overview covers the broader context, and the confidentiality guide for attorneys addresses the professional responsibility framework in detail.

Template 6: Client Update Email

Use case: Draft a post-hearing or post-call client update that communicates decisions, next steps, and the right tone.

Template:

"Draft a client update email following [a court hearing / a call with opposing counsel / a mediation session]. The key outcome: [state what happened, e.g., 'the court denied the motion to dismiss; we have 30 days to respond']. Next steps on our side: [list]. Next steps requiring client input or action: [list]. The client's emotional state on this matter is [e.g., 'anxious and needs reassurance' or 'sophisticated and wants just the facts']. Tone: [e.g., 'direct and reassuring' or 'neutral and factual']. Don't include any legal advice or strategic recommendations, those get added by me before sending."

Always check: Deadlines. If you included one in the prompt, confirm it appears accurately in the output and is appropriately prominent.

Template 7: Deposition Preparation Brief

Use case: Organize an examination strategy and structure anticipated responses for deposition prep.

Template:

"I'm preparing to [take / defend] the deposition of [describe the witness by role only, e.g., 'a corporate officer of the defendant' or 'a damages expert for the plaintiff']. The key issues involve [describe in general terms, no identifying information]. My primary goals: [list 2–3, e.g., 'establish timeline inconsistencies,' 'lock in damages methodology,' 'limit scope of expert opinion']. Organize a deposition prep brief with: (1) examination themes in priority order, (2) areas of anticipated resistance and suggested approach, (3) documents or prior statements to reference. Format as structured sections with brief bullets. All specific questions and factual assertions will be drafted and reviewed by me."

Verify: That the structure reflects your actual strategic priorities. Claude organizes what you gave it, so confirm the emphasis is right for this matter.

Template 8: Internal Case Summary

Use case: Produce an anonymized case summary for internal review, strategy discussion, or supervision.

Template:

"Write an internal case summary for team review. This is anonymized, no client names, entity names, or identifying details. Matter type: [e.g., 'commercial breach of contract dispute']. Current posture: [e.g., 'discovery phase, motion practice pending']. Key facts: [describe in general terms]. Open strategic questions: [list 2–3]. Risks and exposures: [describe without specifics]. Format: structured memo, about one page, suitable for an internal strategy discussion. Tone: analytical and direct."

Always check: Confirm no identifying information crept into the output. Claude works with what you gave it, so if your input accidentally included a name or figure, it may appear in the output.

Template 9: Retainer Letter Opener

Use case: Draft a professional engagement letter opening for a new legal matter.

Template:

"Write the opening section of a retainer letter for a new legal matter. Matter type: [e.g., commercial litigation / estate planning / M&A advisory]. Client profile: [individual / business / institutional]. Tone: [formal and reserved / professional and accessible / transactional and efficient]. The firm's style preference is [brief description, e.g., 'plain English, no Latin, no legalese' or 'formal and traditional']. Include: a brief opening acknowledging the representation, a one-sentence description of the general scope (stand-in wording I'll complete), and a transition to the terms that follow. Don't draft the substantive terms."

Always check: That the scope description, even as stand-in wording, doesn't inadvertently narrow or expand what you intend to cover.

Template 10: Negotiation Position Memo

Use case: Structure your BATNA, walk-away position, and anticipated counterparty moves before a negotiation.

Template:

"Help me structure my negotiation position for [describe the negotiation in general terms, e.g., 'a contract renewal with a key vendor' or 'a settlement discussion in a commercial dispute']. My ideal outcome: [state it]. My BATNA (best alternative if no deal): [state it]. My walk-away position: [state the line]. What the other side likely wants: [describe their interests as you understand them]. Where I anticipate resistance: [list 1–3 areas]. Format as a one-page negotiation prep memo with sections for: my position and rationale, their likely position, areas of potential agreement, and suggested sequencing of issues."

Always check: That the memo reflects your actual walk-away position, not a softened version. It's easy to understate constraints in a prompt, so make sure the output reflects the real limits.

Universal Professional Templates

These five apply across every professional practice. They address the coordination and communication overhead that eats time regardless of discipline. If you're newer to using Claude for professional work and want to build the underlying habits first, the foundational how-to guide is the right starting point.

Template 11: Meeting Recap to Action Items

Use case: Convert rough meeting notes into a clean recap with clearly assigned action items.

Template:

"Convert the following meeting notes into a professional recap. Notes: [paste your rough notes, remove any client names or identifying information if this will be shared externally]. Format: (1) brief meeting context (one sentence), (2) key decisions made, (3) action items with owner and deadline, (4) open items or parking lot. Tone: [internal / client-facing]. If owner or deadline is unclear from the notes, flag it as '[TO CONFIRM]' rather than guessing."

Confirm: Every action item for accurate ownership and deadline. Claude will flag gaps if you instruct it to, so make sure those flags are resolved before distribution.

Template 12: Project Status Update

Use case: Produce a crisp project status update for a client or internal audience.

Template:

"Write a project status update for [describe the project in general terms]. Audience: [client / internal team / leadership]. Current status: [on track / at risk / delayed, with brief explanation]. Completed since last update: [list]. In progress: [list]. Upcoming milestones: [list with dates]. Issues requiring attention or decisions: [list]. Format: structured memo, concise. Tone: [matter-of-fact / reassuring / direct about risks]. Don't soften problems, if something is at risk, say so plainly."

Always check: That risk items aren't buried. A good status update surfaces problems, so confirm Claude didn't bury your risk flags in neutral language.

Template 13: Proposal Structure

Use case: Build a logical structure for a professional services proposal before drafting the content.

Template:

"Outline the structure for a professional services proposal for the following engagement. Prospect/client type: [describe without names]. Services being proposed: [describe]. Key business problem they're trying to solve: [describe]. Our differentiators for this engagement: [list 2–3]. Any known sensitivities or objections to address: [list]. Format: a structured outline with section headers and 1–2 sentence descriptions of what each section should accomplish. Don't write the proposal, just the architecture I'll use to write it."

Always check: That the structure addresses the prospect's actual stated concerns, not a generic version of their problem type.

Template 14: Board Pre-Read Brief

Use case: Prepare a concise pre-read brief for a board meeting or executive committee.

Template:

"Write a board pre-read brief for the following meeting. Meeting purpose: [state it]. Key topics: [list 3–5]. For each topic, include: (1) one sentence of context, (2) the decision or input needed from the board (if any), (3) recommended action (if any). Background information I'll provide: [paste relevant non-identifying context]. Format: clean, structured, readable in under 10 minutes. Tone: direct and analytical. Board members are senior professionals who don't need context they already have, be concise."

Always check: That each agenda item has a clear ask or outcome. A pre-read without a clear purpose for each item wastes board time. If Claude produced informational sections without a decision or input request, add one.

Template 15: Knowledge Capture from Transcript

Use case: Extract structured, reusable knowledge from a call transcript, interview, or recorded session.

Template:

"The following is an edited transcript or set of notes from [a client interview / an expert call / an internal debrief]. I need to extract structured knowledge from it. [Paste the transcript, remove all identifying information first.] From this, produce: (1) key insights organized by theme, (2) specific methodologies or frameworks mentioned, (3) open questions or gaps in the information, (4) recommended follow-up actions. Format as a structured knowledge brief. Flag anything that appears contradictory or unclear rather than resolving the contradiction yourself."

Always check: The flagged contradictions. Claude surfaces them as instructed. Resolving them is judgment work that belongs to you, not to Claude.

Three Habits for Better Output

Three practices will visibly improve your results across all fifteen.

Give Claude the audience first. Before you describe the task, tell it who's reading. "The reader is a CFO who was a former auditor" produces different language than "the reader is a founder with no financial background." Claude calibrates tone and vocabulary to the reader you describe, so use that.

Tell Claude what not to do. If there are things you don't want in the output, speculation, hedging, legal advice, cost estimates, say so. Claude responds to negative instructions as well as positive ones. "Don't include any forward-looking projections" is as useful as specifying what to include.

Iterate in the same session. If the first output is close but not right, don't start over, tell Claude what to adjust. "Make the opening paragraph less formal" or "the second section is too long, cut it by half" are legitimate follow-ups and usually beat a complete restart, because they preserve the context you already loaded.

If you're ready to build the habit rather than reach for the occasional template, The Leverage Club offers monthly systems, prompts, and workflows for practitioners who want to stay current.

For specific disciplines, the domain programs, The Leveraged CPA and Finance Professional, The Leveraged Attorney, and The Leveraged Consultant, go considerably deeper than templates, with full workflow systems built around how each practice actually operates.

The templates here are a starting point, not a destination. Use them, adapt them to your practice, and build your own variations over time. So pick one before you close this tab, run a real deliverable through it today, and save the version that worked under a name you'll remember. That single saved template is the first piece of a system that quietly doubles what you can ship in a week.