How to write a proposal in under an hour

Everybody wants to know how to write a proposal fast, and almost everybody tries to solve it by typing quicker. That is not where the hour goes. The hour goes into writing the sections nobody reads, and then into rewriting them because they did not feel finished.

Cut those and the proposal takes about forty minutes. Here is the structure, the three questions to ask before you start, and the list of things to delete.

Three questions before you write a word

If you cannot answer all three, you are not ready to write. You are ready to make another phone call, which is annoying but considerably faster than writing a proposal that misses.

1. What happens if they do nothing? This is the whole proposal. If doing nothing is genuinely fine, there is no deal here and you have saved yourself an hour. If doing nothing is expensive, that cost is the first paragraph and everything else supports it.
2. Who signs? Not who you have been talking to — who signs. If those are different people, your proposal has a second reader who has not been on any of the calls and knows none of the context. Write for that person.
3. When do they need it working? Not when they want the proposal. When the thing needs to be running. That date sets the timeline section and it is the question that most often reveals the project is more urgent, or far less urgent, than the conversation suggested.

Three questions, four minutes on a call. They save more time than any template.

The six-part structure

In this order. The order is doing as much work as the content.

Seven hundred words. Two to four pages with headings and white space. If yours is running to ten pages, the scope is not clear enough yet — and sending it will produce questions rather than a signature.

Lead with their words

Section one should read like the notes from your call, because it should be the notes from your call. Use their phrasing, including the slightly awkward phrasing. If they said “the follow-up just falls off a cliff after the first week”, write that, not “suboptimal pipeline nurture cadence”.

The reason is not flattery. It is proof of listening, delivered in the first ten seconds of reading, which is roughly how long you have before the reader decides whether this document was written for them or assembled from a folder.

Outcomes, not activities

“Weekly reporting and ongoing optimisation” is an activity. “You will know every Monday morning which leads went cold last week and why” is an outcome. The first describes what you will be busy doing. The second describes what changes for them, which is the only thing they are buying.

What to cut

All of this. Without exception, and without the small pang you will feel about the third one.

• Company history. Founded in 2019, grown to a team of twelve. Nobody has ever bought anything because of this paragraph.
• The methodology diagram. Discover, Define, Deliver, Delight. Four boxes with arrows that describe every professional service ever sold.
• Any sentence starting “We are passionate about”. Passion is not a differentiator, it is a minimum. Nobody advertises indifference.
• The team page. Unless a specific named person is part of what they are buying, in which case it belongs in section three, not in an appendix of headshots.
• Testimonials from a different industry. A glowing quote from a dental practice does not reassure a freight broker. It reads as evidence you have not done this before.
• Terms and conditions. These go in the contract. Putting them in the proposal turns a persuasive document into a legal one, and legal documents get sent to somebody else to read, which is where proposals go to die.

The hour, timed

Assuming the three questions are answered and you are not starting from a blank page.

1. 0–10 min — sections one and two. Straight from call notes. Do not edit while writing; you will lose ten minutes polishing a paragraph you may cut.
2. 10–25 min — section three. The phases. This is the only part requiring real thought, which is why it goes third rather than first.
3. 25–35 min — price and timeline. Slow down here. This is where errors are expensive and where every minute is well spent.
4. 35–45 min — the cut. Delete everything on the list above. Then read section one aloud. If it does not sound like their problem, fix that and nothing else.
5. 45–55 min — format and proof. Headings, spacing, a final read for the sentence that says “insert client name here”. It happens to everyone once.
6. 55–60 min — send, and diary the follow-ups. Three business days, then a week. Put both in the calendar as you press send.

That last step is the one people skip and the one that costs deals. A proposal with no follow-up date attached is one you have already lost track of — and there is no “afterwards” in which you will remember to do it.

Which half of this is delegable

Most of it, and probably not the half you would guess.

The judgement stays with you: the price, and how you frame the problem in section one. Those are the two places where being wrong is expensive, and they are the two places your specific knowledge of the client actually earns its fee.

Everything else is assembly — pulling scope from call notes, dropping in the right examples, applying the structure, formatting, proofreading, sending, and chasing on day three and day ten. That is where forty-five of the sixty minutes go, and it is entirely handleable by an assistant who has the template and the notes. In practice that turns an hour of your time into about fifteen minutes.

The same principle runs through delegating the inbox: keep the judgement, hand over the assembly. And if your proposals are going out fast but the follow-up is where things stall, the fix is a cadence rather than a template — that is the nine-touch sequence, which works on proposals as readily as on property leads.

If proposals are currently a Sunday-evening activity, that is a solvable problem. Twenty minutes, and you leave with a scope and a start date.