How to structure a proposal for a service business

These two documents get conflated and they do different jobs. A quotation answers what it costs and what is included; it is a commercial offer, and precision is the whole virtue. A proposal for service work has to do something a price list cannot: establish that you have correctly understood a situation you were told about once, and make it plausible that you can change it. For a product, the buyer can evaluate the thing. For a service, the thing does not exist yet, so the proposal is the only evidence available about how you think.

That is why structure matters more here than in almost any other sales document. The buyer is reading for signals — whether you listened, whether you have done this before, whether the risks have been considered — and those signals come from the order and emphasis of what you wrote as much as from its content. A proposal containing all the right information in the wrong order will lose to a shorter one that opens with the buyer's own problem, because the first thing a reader decides is whether this document is about them.

The first section states the situation as the client described it, using their vocabulary, including the specifics they mentioned. If they said enquiries are being missed on weekends and their team is spending an hour every morning working out which ones were answered, write that. Resist the urge to translate it into your own framing — the value of this section comes entirely from the buyer recognising their own account of the problem, and a professionalised restatement destroys that recognition.

This section does two things beyond flattery. It is a checkpoint: if you have misunderstood, this is where the client can say so before the rest of the document is built on the error, and being corrected here is far cheaper than discovering it in month two. And it does the internal-selling work, because a colleague who was not in the meeting can read this section alone and understand why anyone is proposing to spend money. If the proposal gets forwarded — which it usually does — this section is doing most of the persuading, and the pages describing your method will not be read at all.

The approach section explains how you intend to get from their situation to the outcome, and its main risk is length. Detail here reassures the writer far more than the reader. The buyer needs enough to believe there is a considered method rather than improvisation, and to understand what will be required of them — access, decisions, materials, time. They do not need the whole methodology, and there is a real reason to withhold it: the approach is a substantial part of what they are paying for, and a proposal that fully documents it is a document that can be handed to somebody cheaper.

Deliverables are the opposite: be exhaustive and concrete. This is what will exist that did not exist before, with dates or elapsed times attached. "Improved processes" is not a deliverable. A written procedure, a configured system, four training sessions, a monthly report in an agreed format — those are things whose presence or absence is not a matter of opinion. Every vague deliverable is a future disagreement about whether the work is finished, and the client's version of that disagreement will not match yours.

A proposal that opens with price asks the reader to evaluate a number before they have any framework for judging whether it is reasonable. Anchored against nothing, the number is compared with their vaguest expectation, which is usually low — and once that reaction has happened, the sections establishing value are read defensively rather than openly. Order is doing real work here, and it is not a trick: understanding what a thing involves genuinely does change what its price means.

Break the price into phases or milestones that each produce something the client can see. This makes the total less abrupt, gives the client a way to start smaller if the full figure is difficult, and ties your payments to demonstrable progress, which is fairer to both sides. Each phase should be coherent on its own — a first phase whose output is useless without the second is not a phase, it is an instalment plan. State clearly what is not included and what recurring costs continue after the work ends, because a client who discovers an ongoing cost after signing remembers it as something concealed rather than as something they missed.

This section covers the conditions the price depends on, and its purpose is to make renegotiation possible without acrimony. The assumptions are the facts you have taken as given: that decisions will come within a stated number of working days, that existing data is in a usable format, that access will be available during working hours, that one named person can approve on the client's behalf. When one of these turns out to be false — and on service work one usually does — you have a written basis for adjusting rather than an argument about who should have known.

Keep it in plain sentences and keep it short. A page of clauses in legal register invites the client to send the proposal for review, which adds weeks, and it does not actually protect you better than three clear sentences. Include what happens in the situations that genuinely arise: the project pauses, the scope changes, either side wants to stop, an invoice is late. Those four cover most real disputes. Anything more elaborate belongs in a contract, and if the engagement is large enough to need one, say so here and let the contract carry that weight.

The final section is the one most often wasted on a paragraph thanking the client for their time. Its job is to remove any ambiguity about what happens next, and the test is whether the reader could act on it in the next two minutes without asking a question. Reply to confirm and the first phase starts on a stated date. Or: a fifteen-minute call to walk through the phasing, with two specific slots offered. A proposal that ends with "we look forward to hearing from you" ends with the buyer having to invent the next step.

It is also worth naming what the client should do if the answer is a partial yes, because that is a common and under-served outcome. If the budget is difficult, say which phase can stand alone. If the timing is wrong, say how long the pricing holds. Giving a buyer somewhere to go other than yes or silence converts a proportion of would-be non-responses into a conversation — and a smaller engagement that starts now is worth considerably more than a complete one that stays under consideration indefinitely.