Writing a Proposal That Closes Without a Call

Make the proposal a decision document, not a brochure

A proposal should make the buyer feel understood before it starts selling credentials. Open with the problem, current consequence, and desired outcome using language from the discovery notes. Then define deliverables in observable terms: number of pages, concepts, analyses, workshops, files, integrations, or review rounds.

Put assumptions beside the scope—client supplies copy by a date, data access is available, one stakeholder owns feedback—because those dependencies are what protect the schedule from pretending everything is under your control.

Put schedule assumptions beside the scope

Put assumptions beside scope. If the price assumes one decision-maker, access by a certain date, or client-supplied copy, make that visible before a delay turns into an argument.

Offer options only when the buyer is choosing real differences

Use options when there are genuinely different levels of value or scope. Three arbitrary price tiers with nearly identical work create confusion rather than anchoring.

Show deposit, milestone, and invoice mechanics before the contract

State payment mechanics in the proposal even if the contract will repeat them: deposit, milestone timing, invoice due date, payment methods, and what happens when a payment is late.

Define a revision before you promise a number of rounds

Limit revisions by round, deliverable, or hours and explain what a revision is. New pages, new audiences, or a changed strategy are additions, not endless revisions to the original work.

End with a visible acceptance action

Pricing belongs next to the thing being bought. If you offer options, make them genuinely different in scope or value instead of three arbitrary price points. State deposit or milestone timing, invoice due dates, revision boundaries, proposal expiry if capacity matters, and the exact next step.

The proposal can remain commercial and readable while the contract handles heavier legal terms. The final line should tell an interested client exactly how to proceed: sign, approve, or pay the deposit. A proposal that ends with 'let me know what you think' creates one more decision for the buyer and one more follow-up for you.

How to make the buyer see the decision quickly

A strong one-page proposal should let a buyer answer five questions without scheduling another call: what problem are we solving, what exactly will be delivered, how will we know it is accepted, when will it happen, and what will it cost? Open with two or three sentences using the client’s own language from discovery, not a biography about the freelancer. Then list deliverables as observable outputs: ‘three 1,500-word articles delivered in Google Docs’ is clearer than ‘content support.’ Add assumptions and exclusions where misunderstanding is likely. If the client supplies inputs, put dates on them. Tie each project phase to an approval event so the timeline shows what happens when feedback arrives late. For options, make them meaningfully different—such as research-only, full implementation, or implementation plus maintenance—rather than three arbitrary price tiers.

Commercial terms belong in the proposal even if a separate contract follows. State the fee, deposit or milestone schedule, invoice timing, payment method, included revision rounds, expiration date, and the next acceptance step. If intellectual-property transfer depends on final payment, say that consistently with the contract. If travel, stock assets, ad spend, printing, or subcontractors are extra, identify who approves them. Add a simple change path: work outside the listed scope requires written approval of price and schedule before it starts. Bonsai’s contract guidance emphasizes this kind of scope/payment/change-control clarity because disputes often come from assumptions, not from the headline rate. Before sending, remove every sentence that could describe any client. A proposal should prove you heard this buyer’s situation and translated it into a bounded transaction.

Before sending, run a ‘stranger test.’ Give the proposal to someone who did not join the discovery call and ask them to identify what is included, what the client must provide, the total price, the payment timing, the delivery date, and the approval step. Any answer that requires oral context is a future dispute candidate. Keep proof claims specific and truthful: ‘reduced reporting time from four hours to one for Client X’ is stronger than ‘we deliver world-class transformations,’ but only use a result you can substantiate and have permission to share. Finally, make acceptance unambiguous—signature, approved e-signature workflow, purchase order, or another method consistent with the contract process. A proposal that is persuasive but cannot be operationalized cleanly is still incomplete. Add one internal estimate that the client never needs to see: expected hours by phase, external costs, and margin at the proposed fee. If that private model already fails before the proposal is sent, a polished client-facing document cannot rescue the economics.

Proposal pass before you hit send

1. Mirror the client's stated problem.
2. Make every deliverable countable or observable.
3. List dependencies and exclusions.
4. Show price, payment timing, and revision boundaries.
5. Give one clear acceptance action.

Proposal questions that improve close quality