How to Use Claude as a Consultant: Workflows, Prompts, and Templates

Set up one Project per engagement

A Claude Project should work like a clean engagement folder: the right context, a clear role, reusable instructions, and boundaries that protect client confidentiality. Create one Project per client engagement rather than one for the whole firm, and use Workspaces to group clients or service lines.

You are supporting a consulting engagement for [client].

Your role: help synthesize research, draft client-ready deliverables, identify risks, and prepare meeting materials.

Working rules:
- Use the uploaded source material first.
- State assumptions before making recommendations.
- Separate facts from interpretation.
- Flag anything that needs human review before it goes to the client.
- Keep client data confidential and never invent proof points.

Setup checklist

• Create one Project per client engagement, not one Project for the whole firm.
• Use Workspaces to group clients or service lines.
• Upload approved source material and remove stale drafts after each phase.
• Add a standard QA prompt that checks claims, tone, and decision usefulness.

Confidentiality should be easy to maintain by design. Keep each client in a separate Project, upload only the files needed for the current phase, and remove obsolete drafts when the engagement moves on.

• Keep each client in a separate Project.
• Upload only the files needed for the current phase.
• Remove obsolete drafts when the engagement moves on.
• If several consultants share source material, agree on a naming and review convention.

Turn research into defensible synthesis

The value of research is not the volume of notes, it is the quality of synthesis. The risk is a writeup that sounds more certain than the evidence allows. Ask Claude to keep a working evidence table with the source, the quote or note, your interpretation, a confidence level, and the recommended client implication. That gives you a review trail and keeps findings honest.

Synthesize this research for a consulting client.

Decision supported: [decision]
Audience: [audience]
Sources: [paste or attach]

Rules:
- Separate evidence from interpretation.
- Group findings into 4 to 6 themes.
- Include contradictory evidence instead of smoothing it over.
- Do not make claims without source support.
- End with strategic implications and open questions.

Synthesis quality check

• Every major claim has source support.
• Contradictions are preserved instead of smoothed over.
• Findings are phrased as business implications, not generic observations.
• The output distinguishes what is known, inferred, and uncertain.

Design and debrief strategy workshops

Claude is useful before and after a workshop, not as a replacement for facilitation. Use it to sharpen the agenda, pressure-test exercises, and turn messy notes into outputs. The fastest post-workshop method is a two-pass synthesis: first ask Claude to organize raw notes into decisions, open questions, risks, and owners without rewriting the language, then give it your read of the room and ask for the executive recap.

Design a 2-hour strategy workshop for [client or team].

Goal: [decision or alignment outcome]
Participants: [roles]
Context: [background]
Constraints: [time, politics, data, budget]

Create:
1. Agenda with time boxes
2. Pre-work
3. Facilitation questions
4. Breakout exercise
5. Decision framework
6. Output template and follow-up workplan.

Workshop output checklist

• A decision or shortlist, not just discussion notes.
• Named owners and due dates.
• Explicit unresolved questions.
• A one-page executive recap.
• A follow-up workplan the client can approve.

Write proposals that sound specific, not generic

Claude can speed up proposal writing, but only if you give it the raw ingredients: client pain, the decision process, scope boundaries, proof, the delivery approach, pricing logic, and risks. Otherwise it produces polished generic copy. Feed it the client's exact phrases from discovery, the business trigger behind the work, and the cost of doing nothing, then ask it to cut any sentence that could apply to any company.

Draft a consulting proposal from these discovery notes.

Client: [client]
Buyer: [buyer]
Problem: [problem]
Desired outcome: [outcome]
Constraints: [constraints]
Proof points: [case studies or credentials]
Scope boundaries: [in and out]

Output:
1. Executive summary
2. Current situation
3. Recommended approach
4. Deliverables and timeline
5. Pricing rationale (placeholders)
6. Assumptions and risks.

Proposal QA checklist

• The first page names the client's problem in their language.
• Deliverables are concrete enough to price.
• Assumptions and exclusions are explicit.
• The proposal explains outcomes, not just activities.
• No proof point is invented or exaggerated.

Report to clients every week

A consistent weekly update is the cheapest way to keep a sponsor confident. Keep it concise and decision-focused, and let Claude turn your raw notes into the same clean format every time.

Turn these project notes into a weekly client update.

Audience: [sponsor, steering committee, or working team]
Tone: concise, direct, no hype
Inputs: [paste notes, metrics, risks]

Output:
1. Executive summary
2. Completed this week
3. Decisions needed
4. Risks and blockers
5. Next week plan
6. Owners and dates.

Two prompts worth keeping on hand

One more that earns its place in every consultant's toolkit is a strategy options generator. Replace the brackets, attach source material, and ask Claude to state assumptions before it concludes anything.

Given this client context, generate 3 strategic options.

For each option include:
- What it means in plain English
- When it is the right choice
- Required capabilities
- Risks and tradeoffs
- 30-day next steps
- What evidence would change the recommendation

End with a recommended option and a short rationale.

THE CLAUDE INSIDER

Get the Claude playbook in your inbox.

One weekly email for Claude and Claude Code users. Real workflows, no hype. Subscribe and we send you The Claude Power-User Cheatsheet.