How to Write a Client Proposal With Claude: Four Prompts, Not a Weekend

You know the feeling. A brief lands on Wednesday, the client wants a full proposal by Friday, and your week already has eight meetings and a sleep deficit. A ten-page document slides into Saturday, and sometimes it never ships at all because the client stopped waiting and signed with whoever answered first.

Claude will not replace a sales team. It will turn eight hours of drafting into one. The trick is not the prompt "write me a proposal from this brief." The trick is splitting the work into four separate prompts, each doing exactly one thing.

What to load before the first prompt

Open a Project in Claude (Projects is a Claude.ai feature where uploaded files stay in the context of every chat inside that project) and drop in three things:

• The client brief: the email, meeting notes, the RFP (request for proposal), a link to their site.
• Two or three of your own winning proposals from previous deals. Not templates off the internet, real documents that closed. Claude copies your voice from these faster than you can describe it in words.
• Your price list, discount rules, hard limits. The numbers you will not move.

Skip these three files and you get a generic press release. Include them and you get a document a client actually reads to the last page.

Prompt one: unpack the brief

Do not ask for text yet. Ask for structure:

You are a business analyst. Read the client brief (file brief.pdf) and pull out: 1) the pain they name out loud, 2) the pain that sits between the lines, 3) the budget or absence of it, 4) deadlines, 5) who signs off, 6) what they tried before that did not work. Return a table, one line per point, with a direct quote from the brief.

One minute later you have a six-row map that normally takes two discovery calls to build. Eyeball it. If Claude invented something, cut it. From this point on you work off the corrected table, not the raw brief.

Prompt two: skeleton, not text

Now the map of sections, still no prose:

Using the table above, draft a proposal skeleton in six sections: our understanding, proposed approach, phases of work, team and track record, price and timeline, next step. Under each section give three bullets to cover, one line each. No filler.

The skeleton pivots on the client's brief, not on your default template. Same section names, different emphasis every time. That is why two proposals for the same service can read like completely different documents.

Prompt three: expand one section at a time

Now Claude writes. One section per prompt:

Expand the "Our Understanding" section around those three bullets. Match my voice from the previous proposals (files proposals-2025.pdf). Paragraphs of three to four lines, no marketing noise, use the client's own words from the brief. 250 to 350 words.

Work section by section. Long single-shot answers thin out; a section at a time keeps the text dense and cuts your rewrite time to almost zero.

Do not hand Claude the "Price and Timeline" section. Write that one by hand. Numbers are the one place where a Claude mistake costs real money.

Prompt four: polish

Paste everything into one document and ask for a critical pass:

Read the whole proposal. Find: ideas repeated across sections, filler phrases like "innovative solutions", sentences longer than 25 words, any spot where I promise more than in my earlier proposals. Return a list of "before, after" edits without rewriting the whole document.

You skim the list in five minutes and accept or reject each edit. Faster than re-reading the whole proposal hunting for weak lines.

What to keep out of Claude's hands

• Numbers: price, timeline, team composition. Anything Claude can invent in a way that sounds plausible.
• Legal wording: guarantees, liability, penalties. That belongs to a lawyer or to your own tested language.
• Named client case studies. Claude does not remember specific names and can drop in a company that does not exist. Paste those in yourself from your own folder.

How to ship the PDF

Ask Claude for an Artifact (Artifacts is an interactive block in the right pane of the chat with working HTML or Markdown): "Assemble every section into one HTML document with a cover page, table of contents, and A4-ready layout. Minimal style, Inter font, accents in black." Download the HTML, open it in a browser, print to PDF.

If you live in Google Docs: ask for Markdown, paste into a fresh doc, apply your styles. Less polish, more speed.

FAQ

What if I have no winning proposals yet? Load two or three public proposals whose tone you like. Claude will pick up the style. But start building your own library from your first sale: in six months your Claude writes like you, not like an average freelancer from the internet.

What if the brief runs to 50 pages? Load the whole file into the project. Claude handles long context. In prompt one, also ask for a page number next to every quote. You can cross-check any claim in seconds.

Can I automate this end to end, brief in, proposal out? You could, and you should not. Those intermediate stops (checking the table, hand-writing the price) are your quality gate. Skip them and one day you send a client a proposal that promises something you cannot deliver. One such case costs more than a month of manual work.

How much time does this actually save? A mid-size proposal now takes a single evening instead of the whole weekend. The saving is not in any single step. It is in the fact that you stop switching between thinking and typing.

Want to build these Claude workflows systematically, not one prompt at a time? Read our free guides and try the first interactive lesson: meet UNIT.

AGINE Academy is an independent product, not affiliated with Anthropic. Claude belongs to Anthropic.