Blog
Scope creep is work that enters a project without a matching change to the price or the programme. These posts cover how to spot it, price it and stop it becoming your problem.
Turn implementation unknowns into testable scope exclusions, then route each failed assumption into discovery or a priced change request.
Unscoped integration work is any interface the signed scope never named. Here is how to count them all before signature, and what to do the day an undocumented one appears.
The money is lost in the ninety seconds between a client asking for a change and a trade starting it. Here is the pause, price and confirm sequence that closes it.
Stage 3 closes, the client approves, and three weeks later they want the roof pitch changed. Here is how to tell a revision from a new instruction, and what to charge.
A deliverable written as a noun has no edges. Give each one a count and an acceptance test, and there is nothing left for a client to widen.
A revision round becomes billable the moment it stops matching the proposal. Define a round properly, then price the extra ones from what delivering one costs.