Writing the thing that prevents the argument

Every bad freelance experience is a scope failure

Not a technical failure. Somebody expected something that somebody else did not intend to deliver, nobody wrote it down, and by the time the difference is visible there is money and pride attached to both readings.

A proposal is not a sales document. It is the artefact that makes the disagreement happen in week zero, cheaply, instead of in week eight, expensively.

The seven sections

Two pages, plain language, no design.

1. What I understand your problem to be. In their words, from the conversation. Three or four sentences. This section alone catches a startling number of mismatches, because clients read it and say “no, that is not really the issue”.

2. What I will do. The approach, briefly.

3. What you will get. The deliverables, named as objects. Not “improved reporting” but: “a dbt project in your repository with twelve models and tests; three dashboards; a one-page handover document; a two-hour walkthrough.”

4. What is not included. The most valuable paragraph in the document. Name the things a reasonable person might assume: ongoing maintenance, training beyond the walkthrough, changes to source systems, mobile layouts, migrating historical data, support after handover.

5. What I need from you, and by when. Access, a named decision-maker, review turnaround. Write the consequence: ”Assumes read access to the warehouse by day two. Each week of delay moves delivery by a week.” This is not aggression; it is the only thing that prevents a delay caused by the client becoming a delay attributed to you.

6. Timeline and milestones, with payment attached to each.

7. Price, validity and how changes are handled. A quote should expire (thirty days is normal) so a client cannot accept in five months at last year’s rate.

Milestones that protect both sides

A shape that works for a six-week project:

Phase 1 — discovery and written assessment      30%  on start
Phase 2 — build, delivered for review           40%  on delivery
Phase 3 — revisions, handover, documentation    30%  on acceptance

Two details do the work. Acceptance must be defined (“acceptance means the three dashboards match the agreed metric definitions on the test period; two rounds of revisions are included”) otherwise “done” is whatever the client feels on the day. And revisions are numbered. Unlimited revisions is not generosity; it is an unbounded liability, and it makes you resentful of a client who is behaving reasonably.

The change request, and the tone

Scope creep almost never arrives as a demand. It arrives as “while you are in there, could you also…”, and each request is small and reasonable. Three of them is a week.

The move is always the same, and it is a yes:

“Yes, we can do that. It is outside the current scope, so I will send a short change note with the cost and the new date, probably about two days. Shall I?”

You have agreed, priced it, and moved the date, in one sentence, without a confrontation. Clients respect this; what they resent is a freelancer who silently absorbs three changes and then delivers late.

Keep a written log of every change, even the ones you waive. “Included at no charge: two extra dashboards (worth ₹40,000)” on the final invoice is the most effective goodwill you can generate, and it prevents the free work from becoming the new baseline.

The kill clause

Both sides should be able to end it. A termination clause saying either party may end the engagement with two weeks’ notice, with completed milestones payable and work in progress billed at the day rate, protects the freelancer from a client who goes quiet and the client from a freelancer who is not working out.

Nobody enjoys writing this and everybody who has been through a bad engagement has one.

The limitation

Some clients read a detailed scope as rigidity, particularly smaller ones used to informal arrangements. The answer is tone, not substance: keep the document short and human, lead with the understanding of their problem rather than with your exclusions, and say out loud that the purpose is so neither of you is surprised.

If a client is unwilling to define what “done” means, that is not a document problem. That is the client, and the information is worth having before you start rather than in week eight.