Write a Proposal That Closes
The one-page structure, scoping that survives contact with reality, and pricing a pilot that leads into an ongoing engagement.
Why most proposals fail
They describe the technology instead of the outcome, they leave scope open, and they arrive too long. A buyer reading about your architecture is a buyer being asked to evaluate something they cannot judge, and the safest verdict on anything unjudgeable is no.
The proposal is not a sales document. It is the artefact your champion forwards to someone more senior, and it has to survive being read without you in the room. That means it must answer, in the first paragraph, what they get and what it costs.
Length works against you. One page that a finance director reads and approves beats twelve pages that sit in an inbox. If you cannot state the engagement on one page, the scope is not clear enough yet, and sending it anyway just moves your confusion onto the customer.
The one-page structure
Open with the outcome in their words, taken from the discovery call: "Security questionnaires returned within one business day instead of five." Then the current cost, as they described it, so the price has something to sit against. Never open with what you will build.
Follow with what you will deliver as a short list of things that will exist and work, then the timeline in weeks, then what you need from them, then the price and payment terms. Finish with what is explicitly out of scope. Nothing else belongs on the page.
The "what we need from you" section does more work than founders expect. Naming the access, the sample data, and the named contact turns their delays into shared responsibility rather than your late delivery, and it surfaces the security review that would otherwise ambush you in week three.
4 more sections in this article
- Scope that survives contact with reality
- Pricing the pilot and what follows
- Terms that protect both sides
- Sending it and following up
This is Pro content
Get Agent Factory Pro - a one-time payment for lifetime access to full articles, complete build prompts, and everything new.
Use it
The parts of the library that put this article to work.
Published 14 August 2026. Last reviewed 17 August 2026. We re-read this library on a schedule and date every article, so you can see for yourself how current it is.