Glossary
What does it mean to scope a custom build?
Scoping a build is defining the smallest, clearest version of a tool that solves one real problem — what it will and won't do — before any code is written, so the project stays tight and ships working.
Scoping is the up-front work of deciding exactly what a custom tool should do — and, just as importantly, what it shouldn't. It turns a vague wish ("we should automate this") into a defined problem with a clear boundary, so the build stays small and finishes rather than sprawling.
We treat a build like an engineering project: find the routine work that's eating someone's time, define the smallest thing that genuinely solves it, build it to fit the way you already work, and hand it over working. The aim is the tightest useful version — not the most impressive thing that could be made.
Good scoping is also where the honest 'no' happens. Sometimes the right answer is that an off-the-shelf product fits better, or that nothing is worth building yet. Saying so is part of the job.
See also
Tell us what’s eating your time
A free 30-minute call. We’ll tell you honestly whether there’s something worth building — and what it would take.