A proposal is not a brochure with numbers in it. It is a decision document. The person reading it is trying to work out three things in order: does this supplier understand what is wrong, can they be trusted to stop where they said they would, and is the number defensible to someone above them. Most proposals answer none of the three, because they open with company history.
The structures below all follow the same spine. Problem before capability, because a buyer checks for understanding first. Scope with an explicit boundary, because unbounded scope reads as future conflict. Pricing that maps to the scope, because a number that cannot be traced back to the work looks arbitrary. Then what happens next, with a date attached.
Why proposals stall
In our testing across thirty days of business documents, four habits accounted for most proposals that went quiet.
- Opening with the supplier. Two paragraphs about the firm before the buyer's situation appear. By then the reader has decided they are being sold to.
- Scope described by activity rather than by boundary. "We will work closely with your team" has no edges. "Three rounds of revision on up to twelve pages" does.
- Pricing presented as a single figure. One number invites one question — why that number — with no structure to answer it.
- No next step with a date. "Let me know if you have questions" transfers the work to the buyer, who has other things to do.
The parts every one of these needs
Regardless of structure, six elements should be present. The problem in the buyer's words, ideally repeating phrases from their brief. What changes — the measurable or observable difference. Scope, including what is excluded. Timeline with milestones. Price mapped to scope. What happens in the next seven days.
The seven structures
1. Fixed-scope project
Use when: the deliverable and the end point are both definable up front.
You described [specific problem from the buyer's brief]. As it stands, [current state and its cost — time, money, or risk].
We will deliver [deliverable], covering [included item 1], [included item 2] and [included item 3]. The work runs [start date] to [end date], with review points on [date] and [date].
Not included: [excluded item 1], [excluded item 2]. We are glad to quote these separately.
[Deliverable 1] · [price]
[Deliverable 2] · [price]
Total · [total], [payment terms]
Next step: [action] by [date].
2. Retainer or ongoing work
Use when: the value is in continuity rather than a single deliverable.
Your team needs [recurring need], currently handled [how it is handled now], which takes about [time] per [period].
Each [period] we will [recurring deliverable] and [recurring deliverable], with a [frequency] review against [measure].
[Monthly fee] per month, [commitment length], cancellable with [notice period] notice.
Next step: [action] by [date].
3. Three-option pricing
Use when: the buyer has not yet decided how much to spend, and you would rather shape that decision than guess it.
The work breaks into three levels. Each is complete on its own; the difference is scope, not quality.
| Option | Includes | Timeline | Fee |
|---|---|---|---|
| [Option A name] | [deliverable] · [deliverable] | [duration] | [fee] |
| [Option B name] | Option A plus [deliverable] | [duration] | [fee] |
| [Option C name] | Option B plus [deliverable] and [deliverable] | [duration] | [fee] |
Use when: sending to a buyer who will forward it internally — three options give someone else something to react to.
4. Milestone-based engagement
Use when: the project is long enough that the buyer needs evidence of progress before releasing the next payment.
The work runs [total duration] across [N] milestones:
| Milestone | Deliverable | Date | Fee |
|---|---|---|---|
| 1 · [name] | [deliverable] | [date] | [fee] |
| 2 · [name] | [deliverable] | [date] | [fee] |
| 3 · [name] | [deliverable] | [date] | [fee] |
Payment falls due [terms] after each milestone is accepted. If a milestone slips because of [dependency], subsequent dates move by the same amount.
5. Response to a formal RFP
Use when: the buyer has issued a structured request and will score responses against it.
Mirror their numbering exactly. Where the request asks for [requirement], our response is [response], supported by [evidence: named client, figure, certification, sample].
Where we do not fully meet [requirement], we propose [alternative] and note the difference: [what is different and what it means].
Commercials are in [section or attachment], valid until [date].
Use when: the evaluation is scored. Deviating from their structure costs points even when the content is stronger.
6. Renewal or expansion
Use when: extending existing work, and you can point at what the last period produced.
Over [period] we [what was delivered], which resulted in [outcome with a number]. [N] items remain open: [item], [item].
For [next period] we propose [scope], retaining [what stays the same] and changing [what changes and why].
[Fee] per [period], [change from current fee, with reason].
7. Pilot engagement
Use when: the buyer wants proof before committing, and the proof can be produced in a fixed, short window.
Before committing to [full scope], we suggest [duration] pilot covering [delimited scope].
At the end you will have [concrete output] and a decision on [the specific question the pilot answers].
Pilot fee [fee], credited in full against [the larger engagement] if you proceed within [period].
What to leave out
Three things consistently reduce response rates. Company history on page one — move it to an appendix where it belongs. Testimonials without names, roles and context, which read as invented. Hourly rates presented without a multiplier, which invites negotiation on the rate rather than the outcome.
How to send it, and when to follow up
Send the proposal, then send one follow-up on a stated date — naming it in the proposal ("I will follow up on [date]") removes the awkwardness from both sides. A second follow-up is reasonable; a fourth is not. If there is no reply after two, the answer is no, and the useful move is to ask why in one sentence, which sometimes produces the real objection.
Draft the structure, keep the specifics
Use a tool to get the skeleton onto the page. The problem section is yours — it will not survive being generated.
Try Rytr →Frequently Asked Questions
How long should a business proposal be?
Long enough to cover problem, scope, boundary, timeline and price — usually two to four pages. Longer proposals get skimmed, not read.
Should I include pricing tiers?
When the buyer has not stated a budget, three options give them something to react to. When they have stated one, a single figure mapped to scope is clearer.
Is it fine to say what is not included?
Yes, and it helps. An explicit exclusion prevents the assumption that everything adjacent is covered.
Can AI write the whole proposal?
It can produce the skeleton and the standard sections. The problem statement and the scope boundary need your own knowledge of the buyer.
How many times should I follow up?
Two. State the follow-up date inside the proposal so the first one is expected rather than awkward.
Do I need a signature block?
For fixed-scope and milestone proposals, yes — include space for both parties and a validity date on the pricing.