Templates · Proposals

Consultant Proposal Template
with AI — 30-Minute Draft.

Most consultants spend 3–6 hours writing proposals. Here's the system that cuts that to 30 minutes — the discovery call structure, the AI prompt, and the proposal template that closes at a higher rate than a generic document.

Updated: May 2026 · 14 min read ★ Most shared article on SoloClientStack

Proposals are broken in two places.

The first break is the discovery call — most consultants don't capture the information they need in the right format. The second break is the writing — starting from scratch every time instead of a proven structure.

Break 1

Unstructured discovery notes

You remember the vibe of the call but not the specific numbers, pain points, or success criteria the client mentioned. The proposal ends up generic because you're reconstructing from memory rather than from structured input.

Break 2

Blank page every time

Even experienced consultants start fresh for each proposal. The structure is roughly the same, the language patterns are the same, the risk sections are the same — but it gets written from scratch anyway.

The fix: capture discovery calls in a structured format that feeds directly into an AI prompt. The AI drafts the proposal. You edit for accuracy and voice. Total time: 25–40 minutes for a first draft that reads as though you spent a day on it.


The six things you need from every discovery call.

Take notes in this structure during the call — not stream-of-consciousness. Each field feeds directly into the proposal AI prompt.

DISCOVERY CALL CAPTURE TEMPLATE

01 — The current situation
What is the client doing today that isn't working? Get specifics — not "our sales are weak" but "we're closing about 15% of discovery calls and we think it should be closer to 30%."
[ Current situation notes — be specific, use their language ]
02 — The cost of the problem
What is this problem costing them — in revenue, time, or opportunity? This becomes the ROI section of your proposal. "We estimate this is costing us $X/year" is infinitely more useful than "it's a real problem."
[ Cost in dollars, hours, or missed opportunity ]
03 — The desired outcome
What does success look like in 90 days? 6 months? Get the specific metric or outcome they're targeting. This becomes the "what we're aiming for" section of your proposal and the benchmark for measuring your work.
[ Specific outcome, metric, or deliverable they want ]
04 — Constraints and context
Budget range (even rough), timeline, team involvement, existing tools they're committed to, political constraints, previous attempts that failed. Every constraint shapes your proposal's scope and pricing.
[ Budget, timeline, team, tools, previous attempts ]
05 — Decision process
Who else is involved in the decision? What do they need to see? What's the timeline? Is there a competing proposal? Knowing this shapes what you emphasize and how you structure your risk section.
[ Decision maker, other stakeholders, timeline, competing bids ]
06 — Their language
The exact words and phrases the client used to describe the problem. Copy these verbatim into your proposal — clients read proposals and think "this person understood exactly what I was trying to say." That's the most powerful close.
[ Verbatim quotes and phrases from the call ]

Use Fathom or Otter.ai to transcribe the call automatically. After the call, extract these six fields from the transcript. Takes 10 minutes and produces far more useful input than trying to take structured notes while listening.


The Claude prompt that drafts your proposal.

Copy this prompt. Fill in the six fields from your discovery call notes. Paste into Claude. You'll get a complete first-draft proposal in under 2 minutes — then edit for accuracy and voice.

CLAUDE PROPOSAL PROMPT — COPY THIS
You are a senior consultant writing a project proposal for a client you have spoken with. Write a complete, professional proposal draft in my voice — direct, specific, and focused on outcomes rather than activities. Use the following discovery call notes: CURRENT SITUATION: [Paste field 01 notes here] COST OF THE PROBLEM: [Paste field 02 notes here] DESIRED OUTCOME: [Paste field 03 notes here] CONSTRAINTS AND CONTEXT: [Paste field 04 notes here] DECISION PROCESS: [Paste field 05 notes here] CLIENT'S OWN LANGUAGE (use these phrases verbatim): [Paste field 06 notes here] MY BACKGROUND: [One paragraph describing your relevant experience and credentials] PROPOSED APPROACH: [Brief description of how you'd approach this engagement — your methodology or process] INVESTMENT: [Your fee or fee range for this scope] Structure the proposal with these sections: 1. The situation (their words, not yours) 2. What's at stake (cost of the problem, opportunity) 3. The outcome we're targeting (specific and measurable) 4. How I'll approach this (your methodology — 3-5 steps max) 5. What you'll receive (deliverables, timeline) 6. Why this approach (brief credibility + differentiation) 7. Investment (fee, what's included, what's not) 8. Next steps (how to proceed — clear and specific) Tone: direct and confident. Use their language in section 1. Avoid consultant jargon. Keep each section tight — proposal readers skim. The whole proposal should be readable in under 6 minutes.
WHAT TO EDIT AFTER THE DRAFT
Check every specific number and detail for accuracy — AI will sometimes infer specifics you didn't provide
Adjust the tone — Claude writes professionally but your voice is different; read it aloud and edit anything that doesn't sound like you
Sharpen the investment section — AI will hedge; be direct about what's included and what isn't
Cut any section that runs long — the best proposals are shorter than you think is professional

The eight sections that close deals.

Every section below has a specific job. Remove one and you leave a question in the client's mind that they have to answer themselves — which they won't. They'll just not respond.

Section 1
The Situation

Job: Show the client you understood exactly what they said. Use their language. They should read this and think "yes, that's exactly it."

Common mistake: Rewriting their problem in consultant language. Don't diagnose. Mirror.

Section 2
What's at Stake

Job: Quantify the cost of not acting. Revenue lost, time wasted, opportunity missed. This creates urgency without you having to ask for it.

Common mistake: Skipping this section. Without it, the client weighs "proposal cost" against nothing — instead of against the cost of the problem.

Section 3
Target Outcome

Job: Define what success looks like in measurable terms. "Increase close rate from 15% to 28%" is a proposal anchor. "Improve sales performance" is not.

Common mistake: Vague outcome language that lets the client move the goalposts. Specificity protects both parties.

Section 4
How I'll Approach This

Job: Give the client confidence that you have a process. 3–5 concrete phases or steps. Not activities — phases with clear inputs and outputs at each stage.

Common mistake: Too much detail. The methodology section should create confidence, not anxiety. If it reads like a statement of work, it's too long.

Section 5
What You'll Receive

Job: Concrete deliverables and timeline. What exists at the end of this engagement that didn't exist before? What does the client actually walk away with?

Common mistake: Deliverables that are activities ("6 strategy sessions") rather than outputs ("Sales process map, recorded training library, and 90-day implementation guide").

Section 6
Why This Approach

Job: Brief credibility and differentiation. Why are you specifically the right person for this? One or two relevant experiences, not a full bio. Why is your approach better than the alternative?

Common mistake: Making this section about you rather than about the fit. "I have 15 years of experience" — so does everyone. "I've solved this exact problem for [similar client] and here's what made it work" — that's a closer.

Section 7
Investment

Job: State the fee clearly and without apology. What's included. What's not included. Payment terms. Don't bury the number or hedge it with "approximately."

Common mistake: "Investment" as a euphemism that makes the section feel evasive. State the number, state what it covers, move on. Clients respect directness.

Section 8
Next Steps

Job: Remove friction from the yes. "To proceed, reply to this email and I'll send a contract" is a next step. "Feel free to reach out with questions" is not — it puts the work on the client.

Common mistake: Ending with an open question ("Does this look right to you?") instead of a clear action. Make it easy to say yes.


Send it right.

A great proposal in a Google Doc link loses deals that the same proposal in PandaDoc would close. Professional delivery signals that working with you is professional.

📄

PandaDoc

Branded proposals with e-signature, payment collection, and analytics on who viewed which sections. Free plan covers 5 documents/month — enough for most solo practices. HubSpot native integration available.

Try PandaDoc Free →
📝

Proposify

Better template library than PandaDoc and stronger content block system — good if you're producing many proposals and want a library of reusable sections. $49/mo but the ROI is clear at 3+ proposals per month.

Try Proposify →
📑

Google Docs

Free and universally accessible. If your clients are in industries where PandaDoc would feel overstyled, a clean Google Doc is perfectly professional. The AI prompt above works for Google Docs output just as well.

No affiliate — it's free

Get the Proposal Automation Playbook

The next step after this template: automate the entire proposal workflow — discovery call → notes → AI draft → PandaDoc → e-sign → onboarding trigger. Subscribers get it first.

  • Full Make automation for proposal workflow
  • Discovery call Fathom → Claude prompt setup
  • PandaDoc template with all 8 sections pre-built
  • Follow-up sequence for non-responses

Free for subscribers

No spam. Unsubscribe any time.


Build the full proposal OS.


Workflow
Discovery Call Automation Workflow
Article
Best CRM for Solo Consultants
Playbook
Client Onboarding Automation
OS
Full Consultant OS →