Key points
- Scoping means agreeing with the buyer which work you'll take on, which you won't, and how you'll both know it's finished. Weak scoping is the leading cause of disputes, overruns and dissatisfied clients.
- Anchor the work to one problem the buyer has raised and one figure that should move, such as weekly hours. Have the buyer log that figure before anything changes; without a baseline, nobody can prove the project worked.
- When neither side understands the job enough to cost a build, offer a short, fixed, paid discovery that ends in a recommendation. Make the findings usable without you, so the discovery is easier to buy and trust.
- Buyers count everything as included unless you say otherwise. So list the usual gaps: links to any system not named, cleaning or reshaping their information, training past a stated number of sessions, ongoing costs of tools, AI models and hosting, support after a set date, and changes after sign-off. That list prevents arguments and shows forethought.
- A tool no one uses is worthless, so price training, help for staff adapting their routines, and handover to the buyer's owner as distinct, priced parts of the job.
- At times the best fix is something the buyer already pays for, an off-the-shelf tool, a process change, or plain automation without AI. Say so: you may earn less, but you win trust and, often, the next job.
- Scope will shift. Settle early how changes are raised and priced, and who at the buyer signs them off. A brief written note per change usually suffices.
- One problem, one measure, written limits, an agreed route for change. Read Scope the work in full.
Transcript
Scoping means agreeing with the buyer which work you'll take on, which you won't, and how you'll both know it's finished. Weak scoping is the leading cause of disputes, overruns and dissatisfied clients. Anchor the work to one problem the buyer has raised and one figure that should move, such as weekly hours.
Have the buyer log that figure before anything changes; without a baseline, nobody can prove the project worked. When neither side understands the job enough to cost a build, offer a short, fixed, paid discovery that ends in a recommendation.
Make the findings usable without you, so the discovery is easier to buy and trust. Buyers count everything as included unless you say otherwise. So list the usual gaps: links to any system not named, cleaning or reshaping their information, training past a stated number of sessions, ongoing costs of tools, AI models and hosting, support after a set date, and changes after sign-off.
That list prevents arguments and shows forethought. A tool no one uses is worthless, so price training, help for staff adapting their routines, and handover to the buyer's owner as distinct, priced parts of the job. At times the best fix is something the buyer already pays for, an off-the-shelf tool, a process change, or plain automation without AI.
Say so: you may earn less, but you win trust and, often, the next job. Scope will shift. Settle early how changes are raised and priced, and who at the buyer signs them off. A brief written note per change usually suffices. One problem, one measure, written limits, an agreed route for change.
Read Scope the work in full.