A project rarely dies from the work you agreed to. It dies from the work that shows up later.
You scope a web app. The build starts. Two weeks in, a new request lands. "While you're at it, can we also add SSO?" Then a second one. "While you're at it, can the dashboard export to CSV?" Each is small. Each sounds reasonable. None of them were in the deal.
This is the "while you're at it" problem. It is the most common way fixed-price work turns into a slow-motion dispute. Nobody is acting in bad faith. The client has real needs. The engineer wants to be helpful. But the line items pile up, and at some point someone has to absorb the cost. Usually it gets absorbed quietly, until the relationship is sour and neither side can say why.
Why "yes" is the expensive answer
The trap is that saying yes feels free. SSO is "just" an integration. CSV export is "just" a button. The marginal request always looks cheaper than it is.
But every add-on has a real cost. SSO means an identity provider, callback handling, session logic, and a test matrix you did not plan for. CSV export means pagination, formatting, large-file streaming, and an edge case where the data has commas in it. The work is not the button. The work is everything behind the button.
When you say yes without writing it down, three things happen. The timeline slips and nobody recorded why. The budget erodes and nobody decided to spend it. And the original scope quietly stops being the agreement, so when you ship, the client measures you against a deal that was never written.
The scope-change letter
The fix is boring and it works. When a new request lands, you do not say yes and you do not say no. You write a scope-change letter.
It is short. Three or four sentences. It names the new work, names what it costs in time and money, and names what it pushes. Then it asks one question: do you want this, and do you accept the new timeline and price?
Here is the shape of it.
> Request: add SSO via your Okta tenant.
> Effort: roughly 1 week, billed as a change order at our standard rate.
> Impact: pushes the original ship date by 5 business days.
> Decision needed: approve, defer to a later phase, or drop. Reply to confirm before we start.
That is the whole tool. No legal language. No ceremony. It turns a vague "while you're at it" into a small, explicit decision with a price tag the client can see.
What the letter actually protects
The letter protects the client more than it protects you. Most clients have no idea their casual request just cost a week. The letter tells them before the money is spent, not after. They get to decide. Defer the SSO, ship on time, add it in phase two. That is a fine outcome, and it only exists because someone wrote the trade-off down.
It protects the build, too. The original scope stays intact. New work becomes new work, tracked separately, with its own yes. When you deliver, you deliver against the agreement everyone actually signed.
And it protects trust. The fastest way to lose a client is to surprise them with a bill or a slipped date. The scope-change letter removes the surprise. Every change is a decision they made, on the record, with eyes open.
How we run it
We price every engagement fixed. A Web App is a fixed number, scoped up front, delivered in a fixed window. An OpenClaw install or a RAG chatbot works the same way. Fixed price, defined scope, you own the code, we exit when it ships.
Fixed price only works if scope holds. So when a new request comes in mid-build, it gets a scope-change letter. Small ones we often just absorb and say so. Real ones get the letter, a price, and a decision. We are a 2-person team that shipped 17 production products, 10 of them in our first 7 months. We did not hit that pace by letting every project quietly double in size.
The discipline is simple. Name the work. Name the cost. Let the client choose. Do it in writing, before the work starts, every time.
If you have an idea with edges that are still moving, that is normal. We can scope it together and tell you straight what fits in a fixed price and what does not. Book a free 30-minute call and we will walk through it.