How to write a business proposal that wins the work

Most small businesses treat the proposal as paperwork. It gets written at nine at night, half of it copied from the last one, and then the client either signs or disappears. When they disappear, the loss is usually blamed on price. That is rarely the whole story. A proposal almost never wins work by itself, because the decision has already been half-made in the conversation before it. What the document does is confirm or quietly destroy the confidence built in that conversation.

Which makes its job narrower and more specific than most people write for. The person reading it is not marking an essay. They are trying to answer three things quickly: does this supplier actually understand my problem, is it clear what I get for my money, and how risky is it to say yes. Anything that helps answer those three questions earns its place. Company history, stock photography and six paragraphs on your values do not. Writing a good proposal is mostly subtraction, plus enough structure to make the decision easy.

What is the difference between a proposal, a quote and a business plan?

These get used interchangeably and they should not be. Sending the wrong document is the fastest way to look like you have misread the situation.

Document	When it fits	What it has to do
Quote	Scope is already agreed and understood by both sides	Price a defined job, with inclusions, exclusions and validity
Proposal	Scope is still being shaped; the buyer is choosing an approach as well as a supplier	Define the problem, propose an outcome, then price it
Tender or RFP response	The buyer has issued a formal request with set criteria	Answer their questions in their format, against their weighting
Business plan	Internal direction, or a lender or investor conversation	Explain the whole business, not one engagement

The distinction that matters most is the first two. If someone asks what it costs to do a job they have already described accurately, send a quote and send it fast. Wrapping a simple quote in eight pages of proposal reads as padding. If the buyer is not yet sure what they need, a bare number with no framing gives them nothing to judge it against, and price becomes the only variable left. That is a bad position to compete in. For the separate exercise of planning the business itself, see how to write a business plan for a small business in Australia.

What should a business proposal include?

Seven sections, in this order. The order is doing real work — it moves the reader from their world to yours, and only then to the number.

1. The problem, in their words. Open by restating what they told you, specifically enough that they could not mistake it for a template. This is the single highest-value paragraph in the document. If it lands, everything after it is read generously.
2. The outcome you are proposing. Not the tasks. What will be true when the work is finished — the reporting that takes an hour instead of a day, the site that survives a sale weekend, the process a new hire can follow.
3. Scope: what is included and what is not. Both halves. The exclusions are not defensive; they are the clearest signal that you have done this before and know where it usually sprawls.
4. Approach and timeline. The stages, what you need from them at each one, and roughly when. Client-side delays are the most common cause of slipped timelines, so name the dependencies plainly.
5. Investment and options. The price, what it covers, payment terms, GST treatment, and how variations are handled.
6. Evidence. One or two genuinely relevant examples of similar work and what changed as a result. Relevance beats volume every time.
7. The next step. One action, clearly stated, with a date. Not three options and a hope.

How long should a business proposal be?

For most Australian small business engagements, two to five pages is plenty. Formal tenders are the exception, because the issuer dictates the format and you answer in it. Everywhere else, length is not a proxy for effort, and it is often read as the opposite: a long document suggests you could not tell what mattered.

A useful test before you send: hand it to someone who was not in the meeting and give them thirty seconds. If they can tell you what problem is being solved, what the client gets and what it costs, the structure works. If they cannot, no amount of design polish will fix it. The same test applies to the email you send it in.

How should you present price in a proposal?

Put the price in the document. Holding it back to force a phone call adds a round trip and signals that you are not comfortable with your own number. Place it after the scope, so the reader has seen what they are buying before they see what it costs.

Two or three options usually outperform a single figure, because they change the question from should we do this to which of these. The discipline is that the difference between tiers must be a real difference in scope or outcome, not a cosmetic one, and the smallest option still has to solve the problem properly. An option you would be embarrassed to deliver is not an option, it is a decoy, and buyers can usually tell.

Option	What changes	Who it suits
Core	Solves the stated problem, nothing beyond it	Budget is tight or the relationship is new
Standard	Adds the adjacent work that usually follows anyway	Most buyers, most of the time
Extended	Adds ongoing support, training or a review cycle	Teams who need the change to stick without you

Whichever structure you use, state clearly whether prices include or exclude GST, how long the price stays valid (14 to 30 days is common), your payment terms, and what triggers a variation. Australian Consumer Law expects the total price to be clear and not misleading, and an unpriced assumption is where most scope disputes begin. If you are still unsure how to set the number itself, that is a separate and harder question — see how to price your services as a small business.

What makes a proposal lose work you had already won?

The failure modes are consistent, and none of them are about writing talent.

• Generic opening. A first paragraph about your company rather than their problem tells the reader this went to four other businesses this week.
• Vague scope. Words like ongoing support or as required feel generous while you are writing them and cost you money later.
• No decision path. Ending with let us know your thoughts puts the work of deciding onto the buyer, and it competes with everything else in their week.
• Sent cold. A proposal emailed without a conversation is a document defending itself in a room you are not in.
• Reflexive discounting. Dropping the price at the first hesitation teaches the client that your number was soft. Reduce scope instead, and say which part you are removing.
• Silence after sending. The most expensive one, and the easiest to fix.

How do you send a proposal and follow it up?

Where you can, walk the client through it live and send it immediately after. The document then has an advocate rather than having to argue on its own. If it must go by email, put a four-line summary in the body of the message — problem, what you propose, price, next step — because a meaningful share of readers will never open the attachment.

Then follow up on a plan, not on a feeling. Silence after a proposal is almost always a stalled internal decision rather than a rejection: budget moved, the sponsor is away, something more urgent landed. A structured cadence that adds something useful each time is the difference between persistent and pushy, and it is covered in detail in how to follow up on a quote without being pushy. When the answer is no, ask what drove the decision and record it. Three or four honest answers will tell you more about your proposals than any template will.

Turn it into a reusable asset

The last step is the one that compounds. Build the seven sections into a template where roughly 60% is fixed — approach, terms, evidence, exclusions — and the rest is written fresh for each buyer. That keeps the personal parts genuinely personal while cutting drafting time sharply, and it is exactly the kind of repeatable process worth writing down properly rather than rebuilding from memory each time.

Have the fixed portion reviewed once by a professional, because an accepted proposal can form part of a binding agreement in Australia. After that you are reusing something already checked instead of improvising terms under deadline. Track a simple win rate by proposal type, and review the losses quarterly. If you want a second read on why good conversations are not converting into signed work, book a consultation and we will look at your last few proposals together. It is the same diagnostic thinking behind our business development and growth services: find the constraint, fix it deliberately, then let the improvement repeat.