Proposals
How to write business proposals with AI
Proposals are where most service businesses leak revenue — too slow, too generic, or too cheap. This guide shows the structure, the AI workflow, and the follow-up cadence that consistently converts.
Start from the discovery call, not a template
Open every proposal by mirroring the client's exact words back to them. Pull the three biggest pains they mentioned, the outcome they described, and the constraints that came up. AI can structure all of this — but only your call notes can make it feel personal.
The proposal structure that converts
Use the same six-section spine for every proposal. Consistency makes you faster and the document easier to scan.
- Situation — the client's current state, in their words
- Outcome — the measurable change they want
- Approach — your method, in plain language
- Scope & timeline — what's in, what's out, and when
- Investment — pricing tied to outcomes, not hours
- Next step — one specific action with a date
Price on outcomes, not hours
Hourly pricing punishes you for being good. Package work into fixed-fee outcomes and show the value gap clearly. AI is excellent at drafting three-tier pricing options once you've decided your floor.
Build a reusable proposal library
Save every proposal you send as a template in your dashboard, tagged by service type. Over a quarter, you'll cut new proposal time from hours to under thirty minutes — and the quality goes up because each new draft starts from your strongest previous one.
Recommended workflow
Tools used in this workflow
Frequently asked questions
How long should a business proposal be?
Long enough to remove doubt, short enough to be read in one sitting. For most service work that's 3–6 pages: problem, approach, scope, timeline, pricing, and next step. Anything longer should move to an appendix.
Should I send pricing in the proposal or after a call?
Always include pricing once you've had a discovery call. Sending without it creates another back-and-forth and signals you haven't scoped the work. Include it before discovery only when you have fixed packages.
Can AI write proposals that don't sound generic?
Yes, when the inputs are specific. Feed the AI the client's exact pain points from your discovery call, not a generic industry description. Generic input is the only thing that produces generic output.
What's the best structure for a winning proposal?
Start with the client's situation in their words, mirror back the outcome they want, then propose your approach. Pricing comes after value is established, never first.
How do I follow up without being pushy?
Three touches over two weeks: a same-day thank-you, a 4-day check-in with one extra insight, and a 10-day final note that closes the loop politely. Use the Email Writer to keep tone consistent.
Continue reading
Recommended stack for this workflow
Tools we'd reach for next — value first, never a popup.
Claude Pro
Long-context reasoning and analysis when the workflow gets dense.
Copy.ai
Workflow-based AI writing built around GTM teams.
Jasper
Brand-aware long-form drafting when one output isn't enough.
Some links on this page are partner recommendations. If you sign up we may earn a small commission — at no cost to you. We only recommend tools we'd use ourselves.