Client work rarely goes over budget in one step. It grows through small requests: one more round of edits, an extra format, a call that turns into a workshop. Each request is reasonable on its own. Together they can turn a profitable project into one that barely covers its cost.
The free PLYNT business scan asks about this directly: how many projects start with a written, agreed scope, and how often the scope grows without anyone billing for the extra work. The second question carries the highest weight in the scan’s Money category, because that is where the money is lost.
Why extra work goes unbilled
- There is no baseline. Without a written scope nobody can say what is extra, and the conversation becomes a matter of opinion.
- The request reaches the wrong person. A designer or developer agrees a small change directly with the client, and the account lead hears about it after the work is done.
- Nobody sees the effort. If time is not recorded against the specific task, the extra hours disappear into the project total.
- Asking feels awkward. Teams avoid raising money for small changes, then discover at the end that the small changes added up.
A routine that catches it
- Write the scope down before work starts. A short list of deliverables, the number of revision rounds and what is out of scope is enough. Keep it with the project, not in an email thread.
- Send every change through one door. Client requests go into a request with an owner, not straight to whoever is doing the work. The owner decides: included, extra or declined.
- Price the change before you do it. An estimate in hours or money, even a rough one, turns “can you just…” into a decision the client makes knowingly.
- Get the approval on record. A written reply attached to the request, not a verbal yes, so it can be found when the invoice goes out.
- Record time against the change. Approved hours on the task show whether the estimate was right and improve the next quote.
- Review the scope at every milestone. Compare what was agreed with what is being delivered. Small differences are easier to discuss early than at the final invoice.
What to say to the client
The conversation is easier when it is about the work rather than the money. “This is outside what we agreed and takes about six hours. Shall we add it to this phase or plan it for the next one?” gives the client a choice and a reason. Most clients prefer a clear option to a surprise on the invoice.
Retainers drift in the same way
A monthly retainer agreed a year ago often covers more work today than it did at the start. Once or twice a year, compare the approved hours and direct costs of the last months with the retainer fee. If the work has grown, you have a factual basis for a new price or a narrower scope.
Signs that scope is leaking
- Projects regularly finish later than planned without any change to the agreement.
- Time on client projects is logged to “general” or “admin” tasks.
- Invoices match the original quote even when the work clearly grew.
- Prices have not changed in more than two years. The scan treats this as a risk as well, because old prices absorb rising costs.
How PLYNT supports this
In PLYNT the agreed scope sits with the client and the project. Each request has an owner and a recorded decision, an accepted request becomes a task with the client and files attached, and approved time on that task shows what the change cost. Read more about requests and approvals and finance and costs.
To see where your business stands, take the free business scan: 21 questions, no account or email.