How to Write a Fixed-Scope Service Proposal (Six Sections)

What a proposal is for

A proposal sells one defined scope at one price. It's not a contract, and it's not a brochure. Its only job is to make a yes easy for someone who already had a good discovery call with you.

A clear proposal won't make a poor-fit client a good one. It removes doubt for the ones who do fit.

The six sections

Self Employed's freelance proposal guide keeps a proposal to six sections. Here's that structure, set up for a fixed-scope offer.

1. Their situation, in their words. Two or three sentences from your call notes. If they don't recognize their own problem, they won't read on.
2. Your approach. How you'll solve it, in plain steps. Keep the method short (the detail is what they're paying for).
3. Scope, deliverables, and what's not included. List each deliverable with quantity and format, then a "Not included" list. Self Employed recommends an explicit Out of Scope subsection. Your one-page scope of work can sit here or be attached.
4. Timeline and what you need from them. Dates for each stage, plus the feedback assumption. Self Employed's example: the timeline assumes client feedback within three business days of each milestone, and slow feedback pushes delivery back.
5. One price and the payment schedule. The fixed price, the deposit, and when each payment is due. Set those terms with the payment terms guide.
6. Terms and the next step. Link or attach your terms, add an expiry date for the price and timeline, and state one action: "Reply yes and I'll send the deposit invoice. Work starts on [date]."

Keep it short and keep it to one price

How long? Self Employed puts it at one to three pages. Long enough to remove doubt about scope and price. Short enough for a decision-maker to read in one sitting.

For a productized service, quote one price for one scope. Options added only to look flexible make the client do your scoping for you. If you sell tiers on purpose, give each tier its own explicit scope.

Close the scope-creep gaps before you send

Most scope arguments start with a line that could be read two ways. Check for these:

• Pin down vague deliverables. "Website copy" becomes "copy for five pages: home, about, services, contact, one landing page".
• Add the exclusions. Write the "Not included" list, even for things that seem obvious.
• Cap the revisions. State how many review rounds are included.
• State the change rule. One line: "Requests outside this scope are quoted separately before work starts." The out-of-scope guide covers what to say when it happens.

Send it within a day, then check it

Self Employed suggests sending within 24 hours of the discovery call. Agree the send date on the call so the client expects it.

Before you send, check:

• Their problem is stated in their words.
• Every deliverable has a quantity and format.
• The "Not included" list exists.
• The timeline names the feedback you need and by when.
• There's one price, a payment schedule, and an expiry date.
• The last line asks for one specific action.

Illustrative example (fictional)

A freelance copywriter proposes a "website copy refresh" for a small accounting firm. The proposal restates the firm's problem from the call, lists five pages with two review rounds, excludes design and blog posts, assumes feedback within three business days, gives one fixed price with a deposit, and ends: "Reply yes by the 20th and I'll send the deposit invoice."

Kit & File works the same way on its own services page: written scope first, accepted in writing, then the invoice. Once the proposal is out, use the proposal follow-up guide. When the client says yes, move to onboarding.

Skip the deck and the one-line price, and send the page in between.