The proposal document: what to include and what to leave out

The call went well. The client says: send me something in writing.

What most freelancers send back is a brochure. Fourteen pages, a spread about their creative philosophy, stock photography of people high-fiving in a co-working space, and a rate card on page twelve. It is neither a pitch nor a contract, and it takes four hours to produce.

A proposal is a priced offer. It is the last document before money moves, and in most engagements it is also the document that sets your payment terms, your revision count and your margin, whether or not you noticed yourself setting them.

One illustration runs through this whole post: a fixed-price brand refresh and five-page website, quoted at €6,000, for a company you spoke to once. The numbers are invented for the example. The structure is not.

Everything in the document is either priced or it is decoration

Here is the test. For each section, ask: if a dispute happened in week six, would this section decide it?

Outcome, scope, exclusions, timeline, price, payment terms, expiry. Those decide things. Your origin story does not. Neither does the page listing your tools.

The good version of the €6,000 proposal is three pages. Two if the client already knows you.

Open with the outcome, because it is the only line the buyer rereads

The first paragraph should state what the client will have when you are finished, in their words, not yours.

Not "a comprehensive brand identity system." Instead: "By 14 November you will have a logo, color and type system, and a five-page site your team can update without calling me, so the new pricing page can go live before your Q1 push."

That sentence does two jobs. It proves you listened, and it puts a date and a business reason in front of the person who has to justify the spend to someone else. If a finance approver reads only one line of your proposal, it is this one.

The scope boundary is the paragraph that decides your margin

Scope is not a list of nice things you will do. It is a countable boundary.

Count everything that can multiply: pages, concepts, rounds, stakeholders, calls, file formats, languages. Each of them has a number, and the number is the difference between a €6,000 project that takes 60 hours and the same project taking 105.

For the illustration:

Included: one route to concept (not three), two rounds of revision on the chosen route, five page templates, one stakeholder review call per milestone, final files in Figma plus SVG and PNG exports.

Two rounds is a real boundary. "Revisions until you're happy" is not a boundary, it is an open credit line drawn against your calendar.

Exclusions are the cheapest insurance in the document

The exclusions section is where new freelancers flinch. They think it reads as defensive. It reads as experienced.

Write it as plain sentences about what happens if the thing is wanted, not as a wall of "not included":

Not included, and priced separately if you want it: copywriting (€X per page), photography, ongoing hosting or maintenance, a third concept route (€X), stakeholder workshops beyond the one review call per milestone, and content migration from the old site.

You have not refused anything. You have priced it. When the client's marketing lead asks in week four whether you can also do the product photography, the answer already exists in writing and does not require an awkward conversation.

Your timeline is really a list of client dependencies

Every freelance timeline slips for the same reason, and it is almost never the freelancer.

So write the timeline with the client's obligations in it, dated, alongside yours:

Then one sentence underneath: "Dates shift by the number of working days any input is late."

That sentence has saved more freelance projects than any contract clause I can name, because it moves the conversation from blame to arithmetic. Feedback arrived nine days late; handover moves nine working days. Nobody argues.

One price gets a yes or a no. Options change the question

A single number asks the client to make a binary decision about you. Three options ask them to make a decision about which version of the work they want, and you are no longer part of the question.

For the €6,000 project:

• Core, €4,200 — logo and type system, three page templates, one revision round.
• Standard, €6,000 — the scope above. Marked as recommended.
• Extended, €9,400 — everything in Standard plus copywriting for five pages, a component library, and a 90-day support window.

Three effects follow. The top option resets what "expensive" means before they reach your real number. The bottom option gives a budget-constrained buyer something to say yes to instead of going quiet. And the middle option, which is the one you actually want to sell, now looks like a judgment rather than an ask.

Build the options so the cheap one is genuinely thinner, not the same work with your margin removed. If Core is Standard at a discount, you have just published a discount.

You can produce a clean priced version of this in a browser with the Worklyn proposal generator, which outputs a branded PDF with scope, pricing and payment terms, with no signup and no watermark on the file.

Payment terms belong here, not on the invoice

This is the part that costs freelancers real money, and it is almost always omitted from the proposal on the grounds that it is "an invoicing thing."

It is not. By the time you send an invoice, the terms were settled weeks ago by whichever document said something about them. If your proposal was silent, the client's accounts payable default applies, and that default is frequently 45 or 60 days.

State four things:

40% on signature, 30% at build complete, 30% on handover. Invoices are payable within 14 days of receipt. Work is scheduled on receipt of the deposit, not on signature. Late payment carries statutory interest and fixed recovery costs.

That last line is not a threat, it is a description of law you already have. In the UK, the Late Payment of Commercial Debts (Interest) Act 1998 sets statutory interest at Bank of England base rate plus 8%, which is 11.75% for 1 July to 31 December 2026, plus a fixed sum of £40, £70 or £100 depending on the size of the debt. In the EU, Directive 2011/7/EU makes 30 days the default B2B period, caps agreed terms at 60 days unless expressly agreed and not grossly unfair to you, and gives you at least €40 of fixed recovery compensation per late invoice plus interest at the ECB reference rate plus at least eight percentage points.

Which produces a genuinely counterintuitive rule: a proposal that says nothing about payment terms is better than a proposal that agrees to net 60. Silence leaves you the statutory default. Agreement waives it.

The full mechanics of getting from delivered work to cleared cash are in the guide to getting paid on time; the proposal is where that chain starts.

The valid-until date, and why it is not a pressure tactic

Put an expiry on the price. Give it thirty days.

This quotation is valid until 30 October 2026. After that date I am happy to requote against current availability.

Two reasons, neither of them urgency theater. First, you are holding capacity you cannot sell twice, and a proposal accepted in March at a price you set in October is a project priced with last year's cost base. Second, an expiry date gives you a legitimate, non-needy reason to follow up: "this one runs out on the 30th, do you want me to extend it or requote?"

If you want the expiry to sit on a formal priced document rather than inside a narrative proposal, the quote generator has a valid-until field alongside line items, tax and discount, and produces the PDF in the browser.

What to cut, specifically

Your life story. One paragraph of relevant credential, positioned after the price rather than before it. Nobody has ever bought because of paragraph two.

Stock photography. It signals template. So does a cover page with the client's logo stretched across it.

A rate card. This one matters most. Publishing your hourly rate inside a fixed-price proposal invites the client to reprice the project by arguing about hours, and it converts a conversation about outcome into a conversation about your time being worth less than they thought. Quote the work, not the hours.

Terms and conditions in eight-point type. Either the terms matter, in which case they go in the contract you both sign, or they do not, in which case delete them.

The follow-up nobody sends

Send the proposal, then send one short message three working days later. Not "just checking in." Something that adds information:

Quick note on the 12 September start — I have that slot held until the 30th and then it goes to another project. If the timing is the issue rather than the scope, say so and I'll show you what a November start looks like.

That reopens the conversation on scheduling, which is a much easier thing for a hesitant buyer to answer than "did you decide."

A note on proposal tooling

You do not need software for this. A well-structured document in whatever you already write in will beat a beautiful template with no exclusions section.

What software changes is the handoff. The reason to keep proposals, contracts and invoices in one place is that a signed proposal should become a contract and then an invoice without anyone retyping the scope or the payment terms, which is where the terms usually get lost. That is the argument for a connected workflow, and it is worth comparing honestly on price: Dubsado sells Starter at $335 a year, Bonsai starts at $15 per user per month, and Worklyn Pro is €19.99 a month with the whole chain included, which is the comparison the Dubsado alternative page sets out in detail. Worklyn's own proposal builder tracks when a proposal is opened and converts an accepted one into a contract or an invoice in one click.

Your next thirty minutes, and the rest of the month

In the next thirty minutes: open the last proposal you sent and find the exclusions section. If there isn't one, write six lines of exclusions for that project from memory, and notice how many of them already happened. That is the list you were absorbing for free.

This month: rebuild your proposal as a three-page skeleton with seven fixed sections — outcome, scope with counted boundaries, exclusions with prices, timeline with client dependencies, three price options, payment terms with a deposit, and a valid-until date. Send the next three proposals from it unchanged, then compare the close rate and the revision count against the last three you sent the old way.

Worklyn's Scope Watch flags a project against its budget while there is still time to re-quote, so the gap between the scope you wrote and the scope you are delivering shows up in week three rather than at handover.