The Practical Proposal Workflow

AI Proposal Writing: How to Write Client Proposals Without Sounding Generated

AI proposal writing, in one sentence: paste your past wins, your pricing logic, and the client's own RFP language into ChatGPT or Claude, get a first draft in your voice, then apply the human judgment pass before anything goes out. This guide walks through that workflow step by step, with the exact prompts.

1-on-1 with Pete Enestrom, on your actual work

Pete Enestrom

Written by Pete Enestrom

Yale & Columbia, ex-Microsoft & Intel — 1-on-1 AI coaching for executives

Pete Enestrom — executive AI coach and Zaigo co-founder

Your coach’s background

YaleCOLUMBIAUNIVERSITYMicrosoft

Most proposals a services firm sends are written under time pressure, by the person who should be running the work, starting from a blank page. That is exactly the situation AI proposal writing fixes well. The mistake is asking the tool to “write me a proposal.” A generic request produces a generic proposal, and generic proposals lose. The method that works is the reverse: you bring the raw material—your past wins, your pricing logic, the client's actual request—and the AI assembles a first draft around it.

A client of mine runs a twelve-person consulting firm. Responding to a serious request for proposal used to take him the better part of a week, which meant he declined more opportunities than he answered. Now the first draft takes an afternoon. Not because the AI writes his proposals—because it reads the RFP, organizes his record, and drafts in his voice while he spends his hours on the two things that actually win work: the diagnosis of the client's problem and the pricing judgment. That division of labor is the whole idea.

This is written for founders and executives of services and consulting businesses—business proposals, in other words. If you are writing grant proposals for a nonprofit, that is a different discipline with different rules, and I've covered it separately on the AI for nonprofits page. Everything here assumes a real client, a real request, and a reputation you cannot afford to embarrass.

How to write a proposal with AI: the six-step workflow

This is the sequence I teach, and it works in ChatGPT, Claude, or Gemini on any plan. Budget an afternoon the first time; it gets faster every proposal after that.

  1. Gather the raw material before you open the chat window

    Collect three things: the client's request or RFP, one or two past proposals you are proud of (won or lost), and a rough note on your pricing logic for this kind of engagement. AI proposal writing is only as good as what you feed it, and ten minutes of gathering beats an hour of regenerating bland drafts.

  2. Paste the RFP and have the AI read it back to you

    Before any drafting, paste the client's request and ask the AI to identify what the client is actually asking for, what they seem worried about, and what the evaluation criteria imply. Clients often reveal their real priority in the language of the RFP, and a fresh reader catches it more reliably than a busy founder skimming at midnight.

  3. Feed it your past wins and your pricing logic

    Paste your best past proposal and tell the AI, in plain terms, how you price: day rates, fixed fee, value-based, whatever you actually do. You are not handing over judgment—you are giving the tool your record and your rules so the draft reflects your firm instead of the average of the internet.

  4. Ask for a structure, not a finished proposal

    Have the AI propose an outline mapped to the RFP's own sections and language, then adjust that outline yourself. This is the step people skip, and it is where proposals are won or lost. A structure you approved produces a draft worth editing; skipping it produces a document you fight with for hours.

  5. Draft section by section, in your voice

    Work one section at a time—understanding of the problem, approach, relevant experience, team, timeline, pricing. Push back on every draft: “too formal,” “this claim is too strong,” “make the second paragraph half as long.” The third version of a section is usually the one worth sending.

  6. Run the human judgment pass before anything goes out

    Read the full document aloud. Verify every number, every client name, every claim about your record. Check that the proposal answers the RFP's actual questions and sounds like you on a good day. This pass is non-delegable—your name is on the document, and the client's procurement team reads proposals for a living.

The exact prompts, ready to copy

These are the prompts I hand to clients, in the order the workflow uses them. Replace the brackets with your material. The prompts are plain on purpose—your pasted context is what makes the output worth reading.

Read the RFP like a skeptical partnerPrompt

Here is a request for proposal we received: [paste the RFP]. Before I respond, tell me: what is this client actually asking for, in one paragraph? What do they seem most worried about, based on the language they use? What do their evaluation criteria imply about how they'll choose? And what questions should I ask them before I commit to a price?

Run this before you write a word. Most losing proposals answer the RFP as written instead of the problem behind it.

Turn your record into a win-pattern briefPrompt

Below are two past proposals of mine—one we won, one we lost: [paste both]. Identify the patterns: how do I describe our approach, what evidence do I lean on, and where does the losing one go wrong? Then write a one-page brief on 'how we write proposals' that I can reuse as standing context for future drafts.

That brief becomes a permanent asset. Paste it at the top of every proposal session from now on.

Calibrate the voicePrompt

Here is a proposal I'm proud of: [paste]. Study how it sounds—sentence length, level of formality, how directly it makes claims. From now on in this conversation, draft in that voice. Never use the words “leverage,” “synergy,” or “we are excited to.”

Banning your least favorite consultant-speak does more for the draft than any style adjective.

Draft one section against the outlinePrompt

Using the outline we agreed on and everything I've pasted, draft the 'Understanding of the Problem' section. It must restate the client's problem in their own language from the RFP, show we've solved this exact problem before [paste the relevant engagement summary], and run under 250 words. If anything I've given you doesn't support a claim, flag it instead of inventing one.

The last sentence is what keeps AI-assisted proposals honest. Steal it for every section.

The procurement red teamPrompt

You are the client's procurement committee evaluating the proposal below: [paste your near-final draft]. Score it against the RFP's stated criteria: [paste criteria]. Where is it weak? What would make you pick a competitor? What questions would you put to me on a call? Be harsh—I'd rather hear it from you than lose.

Run this the day before the deadline, not the hour. You'll want time to fix what it finds.

What about AI proposal generator tools?

If you search this topic, you will land on template and generator tools—Proposify, Venngage, Canva, and the like. They solve a real problem, and for some businesses they are the right answer: if your firm sends a high volume of near-identical, productized proposals, a template system with a content library will serve you well. I have clients who use them happily for exactly that.

But a services or consulting firm selling judgment—where every engagement is shaped to the client—wins on the specificity of its record, not on the polish of its template. That is why I teach the paste-your-context method in ChatGPT or Claude instead. The tool reads the client's actual RFP language, your actual past wins, and your actual pricing rules, and drafts around them. A generator fills a template; this method argues your case. For design-heavy delivery, you can still drop the finished text into whatever template tool you like—the writing is the part that wins or loses.

The pre-send checklist

Before any AI-assisted proposal leaves your outbox, run this list. It takes fifteen minutes and has saved my clients from every embarrassing failure mode I know.

  • Every number verified against the source—pricing, dates, team size, past results. AI drafts are fluent and occasionally wrong.
  • Every client name and company checked. Leftover names from a pasted past proposal are the classic failure.
  • The proposal answers the RFP's actual questions, in the client's own language, not a paraphrase of them.
  • Claims about your record are ones you can defend on a call. If the draft oversells, tone it down—you own it.
  • Read aloud start to finish. If a sentence doesn't sound like you on a good day, rewrite it.
  • Someone who didn't write it reads the pricing section. Fresh eyes catch what familiarity hides.

What never to delegate to the AI

Two parts of a proposal are yours alone. The first is the diagnosis—your read of what the client actually needs, informed by conversations the AI wasn't in. The draft can restate the client's problem beautifully, but deciding what the problem is remains your job; that judgment is what the client is buying.

The second is pricing. Let the AI format the pricing section, explain the options, and check the arithmetic—but the number itself is a strategic decision about your firm, your pipeline, and this client, and it belongs to you. The same is true of the final judgment on whether to pursue the work at all. A fast, good drafting process makes declining easier, too: when a proposal costs an afternoon instead of a week, you can answer more requests and walk away from the wrong ones with less pain.

When the proposal volume outgrows the method

Everything in this guide works solo, free, this week—and for many firms that's enough. The ceiling appears when proposals become a system problem rather than a writing problem: multiple partners drafting at once, a content library nobody maintains, win/loss patterns nobody analyzes. At that point the question is no longer how to write one proposal with AI but how your firm's whole pursuit process should work, and in what order to rebuild it.

That's where a human teacher—not an AI coach bot—earns its keep. In 1-on-1 coaching over video, we work on your real pipeline: your past proposals, your pricing logic, your actual win patterns, and the prompts and habits built around them. This guide is the map. Coaching is walking it on your terrain, with your deadlines on the table.

1-on-1 coaching

Want a teacher, not another tutorial?

Guides get you started. A 1-on-1 session gets you fluent—built on your actual work, at your pace.

Format1-on-1Sessions
LocationNYCor Remote
Duration2-4 hrsFocused
ResultClarityWalk away ready
Pete Enestrom in a 1-on-1 coaching session

Your coach

Coached by Pete Enestrom

Yale and Columbia grad, former Microsoft and Intel, and a venture-backed exited founder. Pete has spent the last four and a half years going deep on every major AI tool, and he teaches the way operators learn: on your real work, at your pace, with nothing assumed.

YaleCOLUMBIAUNIVERSITYMicrosoft
Pete Enestrom's signature

Common questions

Straight answers, the way I'd give them across a table.

Keep reading

Beyond coaching

When the workflow needs to be encoded, not just learned — that's what our team at Zaigo builds.