How to write a fee proposal that gets signed.

Most fee proposals are rejected before the price is read. Not because the number is wrong, but because by the time the client reaches it they still are not sure what they are buying.

A proposal is not a quote with better typography. It is the document that converts interest into commitment, and it is usually the only thing a client will forward to the person who has to approve the spend. That second reader has never met you.

What a proposal is actually for

Three jobs, in this order.

Remove uncertainty. A client who does not understand the process cannot say yes to it. Most hesitation that looks like price resistance is actually scope confusion — they cannot picture what happens after they sign.

Make comparison hard. If your proposal reads like every other proposal, price becomes the only variable. Specificity is the defence: name the deliverables, name the counts, name the dates.

Set the terms of the relationship. What you exclude in the proposal is what you will not be arguing about in month three. This is the section people skip and later wish they had not.

The structure that works

Seven sections. The order matters more than the wording.

1. The understanding. Open by restating the project back to them — the property, the rooms, the constraints they mentioned, what they said they wanted to achieve. Two paragraphs. This does more work than anything else in the document, because it proves you listened.

2. Scope of work. What you will actually do, in plain language. Not "design services" — concept development, space planning, FF&E specification, documentation, site visits. Whatever is genuinely in.

3. The phases. Break the project into three to five phases with what happens in each and roughly how long it takes. This is where uncertainty dies. A client who can see the shape of the next four months is a client who can commit to it.

4. Deliverables. Be specific to the point of discomfort. "Presentation drawings" is vague. "One concept presentation, up to 12 boards; a furniture schedule covering the five rooms listed; three photorealistic renders of the main living space" is a thing someone can approve.

5. The fee. Only now. See below.

6. What is not included. The section that saves you. Site measure beyond one visit, procurement and order management, additional render rounds, contractor coordination, revisions after sign-off. Naming these is not defensive — it is the clearest signal that you have done this before.

7. The next step. One sentence, one action. Not "let me know your thoughts." Something like: reply to confirm and I will send the agreement and the deposit invoice.

How to present the price

The instinct is to soften it. Resist that. Apologetic pricing reads as uncertainty about the value, and clients notice.

Three things help. Show the structure, not just the total — a fee split across phases is easier to accept than one large number, because it maps to work they can see happening. State what triggers each payment, so the schedule feels like a mechanism rather than a demand. And give a comparison inside your own proposal: two or three service levels, with the middle one the obvious fit. A client choosing between your options is no longer choosing between you and someone else.

Do not itemise hourly. The moment a client can see a rate, they start auditing hours instead of judging outcomes.

Three mistakes that lose the job quietly

Sending it as a bare attachment. The email is part of the proposal. Two sentences framing what is inside and when you will follow up doubles the odds it gets opened the same day.

Leaving the timeline out. "We can start soon" is not a plan. Dates create urgency, and vagueness gives permission to postpone.

No follow-up. The most common reason a proposal dies is that nobody chased it. One short message five business days later, offering to walk through it on a call, recovers more work than any redesign of the document.

What to do after it is sent

Note the date. If you have heard nothing in five working days, follow up once — briefly, without apology, offering a fifteen-minute call. If that call happens, most of the remaining resistance dissolves, because objections that feel enormous in writing are usually small when spoken aloud.

And when a proposal is rejected, ask why. Half the time the answer is budget and there is nothing to learn. The other half it is scope, timing or a doubt you could have removed on page two. That second half is the only real feedback loop you have.

The template

Everything above is structure, and structure is reusable. Build the document once with your own language, your own phases and your own exclusions, then change only the understanding section and the numbers each time. A proposal that takes forty minutes rather than four hours is a proposal you will actually send while the enquiry is still warm — and speed converts better than polish.