How to write an offer people understand

An offer that only exists in conversation changes shape every time you describe it. You add a bit here to be helpful, you leave out a condition there because it felt awkward, and three weeks later you and your customer have two different ideas about what was agreed. Writing it down is not paperwork. It is the thing that keeps the work finishable.

One page, six parts

1. 01Who it is for. One line, specific. If a reader cannot tell whether it means them, it is too vague.
2. 02What they get. The outcome in their language, not a description of your process.
3. 03What is included. A short list of concrete deliverables.
4. 04What is not included. Shorter than you think and more important than everything above it.
5. 05How long it takes and what you need from them. Most delays are caused by waiting on the client, so say what you need and when.
6. 06What it costs and how payment works. The number you arrived at, when it is due, and in how many parts.

That is the whole document. It fits on one page. If it runs to five, you are writing a contract, which is a different thing you may also want, but not instead of this.

What one looks like

Continuing the earlier example, so the format is concrete rather than abstract.

It is unglamorous, and that is the point. A reader can tell in ten seconds whether it is for them, what they will have at the end, what you will not be doing, and what it costs. Nothing in it requires a follow-up email to understand.

The exclusions are the useful part

Writing down what you are not doing feels unfriendly and is the single highest return paragraph on the page. Every project that went badly for someone you know went badly in the gap between what the client assumed and what the supplier assumed.

• How many rounds of changes are included, and what happens after that.
• What you need them to provide, and what happens to the timeline if it arrives late.
• What is a separate piece of work rather than part of this one.
• What happens if they want to stop halfway.

How the scope actually grows

Rarely in one large request. Almost always in small ones that are each individually reasonable, which is why saying no to any single one feels petty. Knowing the pattern is most of the defence.

• While you are in there, could you also. The most expensive sentence in service work.
• A new person joins the project halfway through and has not read the offer, so their expectations are whatever they imagined.
• A small change that requires redoing something already approved, described as a small change.
• Delay on their side that quietly becomes urgency on yours.

The response is the same for all four and it is not a confrontation: that is outside what we agreed, here is what it would cost and what it does to the date, shall I add it? Said early and without irritation, it is simply information, and most clients say either yes or never mind. Said three weeks late, after you have absorbed four of them, it is a grievance.

Payment terms, briefly

• Take something up front. Half is normal for a fixed piece of work, and it filters out people who were never going to proceed.
• Say when the rest is due, tied to an event rather than a mood: on handover, not on satisfaction.
• Say what happens if it is late, even if you never intend to enforce it. Having written it is what makes the reminder easy.
• For anything ongoing, bill in advance rather than in arrears. Chasing money for work already delivered is the worst part of this business and is avoidable.

Write it in their words

Go back to the notes from your twenty conversations and use the exact phrases people used. If three people said the handover is a nightmare, your offer should say something about the handover not being a nightmare. Not 'streamlined transition processes'. The words they actually used.

This is not a copywriting trick. It is evidence that you listened, and it is the fastest way for a reader to recognise their own problem on a page written by a stranger.