Draft Project Proposals in Under 20 Minutes

You'll end up with: A structured, client-ready project proposal you can send today—with clear scope, pricing, timeline, and a single next step

Overview
15-20 min
Intermediate
Free
2 tools
Cost breakdown
Claude (deal checklist, commercial frame, draft, de-template)Free
Google Docs (formatting and send-ready doc)Free
TotalFree
Common mistake

Polishing paragraphs before locking commercial shape (single fee vs tiers vs phased) and measurable deliverables. You get a pretty doc that either under-prices, over-promises, or reads like a generic template. Fix: complete steps 1–2 before any narrative; in step 3, require named deliverables and a binary next step; in step 4, strip template phrases and add client responsibilities plus change-order language.

Before you start
  • One real opportunity in mind (who they are, what they want, rough budget or unknown)
  • Rough price floor you will not go below (or a single target price)
  • Delivery timeline you can honestly hit
  • List of in-scope vs out-of-scope bullets (even if rough)
  • Claude open in one tab; Google Docs (or Apple Notes or Notion) for the final doc
1

Capture deal parameters (mirror only, no proposal prose)

Turn your rough facts into a tagged checklist—no client-facing wording yet.

ClaudeFreeOpen Claude
Exact action

1. Open https://claude.ai and start a new chat (keep everything in this single thread through step 4). 2. Paste the block below. Fill every bracket with your real deal facts. --- I need to prep a client-facing project proposal fast. Do NOT write proposal wording yet. First mirror my inputs as a checklist. Client (name + company if any): [...] What they asked for (one paragraph): [...] Success definition — what done looks like for them (one sentence): [...] Constraints (timeline, budget signal if any, tech stack, stakeholders): [...] My intended approach (one line): [...] Commercial posture — describe ONE of: single target price OR three tier NAMES only (no numbers yet) OR phased deposit plus milestone: [...] Hard no — what I will NOT include in this proposal: [...] Biggest unknown that could blow up scope: [...] Reply with ONLY: (A) A checklist of every item above, each line tagged EXACTLY one of: CONFIRMED / ASSUMED / MISSING—ask client before sending (B) Up to 3 clarifying questions for anything MISSING (C) No executive summary, no bullets that sound like client copy, no pricing paragraph. --- 3. Answer Claude's clarifying questions in-chat if you can. If you must ship now, reply which MISSING lines you will accept as ASSUMED anyway (name each assumption in one clause). 4. If Claude writes ANY client-facing proposal prose, stop and re-send: Mirror only — no proposal text.

Every MISSING line is either resolved, re-tagged ASSUMED with your stated assumption, or you consciously accept one crisp TBD you will ask the client after send.
Claude wrote executive-summary tone, pricing language, or a pitch — restart with the line: Do not write any client-facing wording in this message. Only mirror and ask for missing context.
2

Lock the commercial frame and tier table shell

Pick one fee structure and output a markdown price table shell you will paste into the proposal.

ClaudeFreeOpen Claude
Exact action

In the SAME chat, paste: --- Using ONLY the checklist from my previous message (treat ASSUMED as fixed unless I contradict you), choose exactly ONE commercial structure for THIS proposal. Allowed structures: single flat fee | two-tier | three-tier Good/Better/Best | phased (deposit + milestone) Rules: - Return exactly TWO sentences of justification only (why this structure fits THIS deal). - Then output a markdown table with columns: Tier or Phase | What's included | Price | Payment terms - In What's included: max 3 short bullets per cell, no fluff adjectives. - Use placeholder [$X] or TBD in Price cells. One short phrase per cell for Payment terms. - Tiers must differ by named deliverables OR timeline — not by vague more support. --- If tiers only differ by support level, reply: Rebuild the table — each tier differs by named deliverables or timeline, not adjectives.

You can read the table aloud and it matches how you actually sell — not fantasy scope.
Tiers differ only by vague support — re-prompt: Each tier must differ by named deliverables or timeline, not adjectives.
3

Generate the full proposal draft (paste-ready Markdown)

One document with fixed headings: scope, timeline, investment, assumptions, next step.

ClaudeFreeOpen Claude
Exact action

In the SAME chat, paste: --- Using the checklist from step 1 AND the investment table from step 2, write ONE markdown document (paste-ready) with EXACTLY these headings in this order: # [Client] — Project proposal ## Executive summary (max 5 bullets) ## Goals ## Approach (keep short) ## Deliverables (bulleted; each bullet starts with a verb; include a nested sub-list titled Out of scope with at least 2 items) ## Timeline (total weeks + TWO named milestones with dates or week ranges) ## Investment (paste the table from step 2 verbatim; if single fee, keep one row) ## Assumptions ## Client responsibilities (at least 3 bullets) ## Change orders (one short paragraph: how scope changes get priced and approved — no new free work) ## Next step (exactly ONE sentence; binary decision OR a booking-link placeholder like [CALENDLY]) Banned phrases anywhere (if any appear, rewrite before finishing): world-class, best-in-class, synergy, we're excited to, leverage, robust, holistic, ongoing support (unless you include explicit hours per month and cadence). ---

Every deliverable is observable (checkboxable); Next step names one action; Investment matches the step 2 table.
You see ongoing partnership, unlimited revisions, or vague maintenance — reply: Rewrite: either delete or convert to hours per month and SLA.
4

De-template, tighten risk, and sharpen the ask

Strip template voice, add engagement risks, and lock a two-sentence send email.

ClaudeFreeOpen Claude
Exact action

In the SAME chat, paste: --- Edit the markdown you produced in the prior message. Do not add new scope or new tiers. (a) Rewrite ONLY: the first paragraph under Executive summary AND the first sentence under Investment — plain human voice, no stacked adjectives. (b) Insert a new section AFTER Assumptions titled Engagement risks with exactly 3 bullets. Each bullet format: Risk: ... | Mitigation: ... (mitigation must point to something already in Assumptions or Client responsibilities). (c) Output TWO email subject lines (each ≤60 characters). (d) Output a cover email body: exactly 2 sentences, then a new line with only: Attached: proposal. Ban in the email: apologies, new discounts, happy to discuss anything, hedging that re-opens negotiation. One clear action only. ---

Opening sounds like you; risks feel specific to this client; email drives one decision without softeners.
Email apologizes, adds a discount, or re-opens negotiation — reply: Remove softeners; keep a single ask.
5

Finalize in Google Docs (format, bracket sweep, send-ready)

Move Markdown into a polished doc, sweep placeholders, optional last typo pass.

Google DocsFreeOpen Google Docs
Exact action

1. Open Google Docs and create a new document titled: [Client] — Proposal — [DATE] 2. Paste your final markdown from Claude (step 3 with edits from step 4). Apply Title or Heading 1 for the # line and Heading 2 for each ## section. 3. Replace every [bracket] placeholder and [$X] with real numbers or intentional TBD. Optional: paste only the Next step + Investment sections back into Claude and ask: List up to 5 template tells or typos — then fix them in Docs. 4. Read aloud once. Run Find for the wrong client name, TODO, or TBD — every TBD should roll up to at most one crisp question you will ask after they say yes.

One scrollable doc you would attach to a real client; placeholders are facts, prices, or a single explicit follow-up question.
Wrong client name or stray internal placeholders remain — run Find/replace before sending.

All done!

You now have: A structured, client-ready project proposal you can send today—with clear scope, pricing, timeline, and a single next step

Explore more guides

Want this workflow built for your business?

Book a free audit