How we scope a project in 24 hours without guessing

Most agencies take a week or more to come back with a scope, and the delay is rarely laziness. It is that scoping feels like it requires certainty, and certainty takes time to manufacture. So the estimate waits for a discovery call, then a follow-up, then a conversation with whoever knows the legacy system.

Meanwhile your client is waiting for a number, and someone less careful has already sent them one.

We turn scopes around in a day. Not by being clever, but by being strict about what a first-day scope is allowed to contain.

Separate the known from the unknowable

Any brief splits into three piles. Things we can size confidently because we have built them many times. Things we can size with a range because the shape is clear but the details are not. And things nobody can size yet because they depend on information that does not exist.

The failure mode is treating all three as one pile and padding the total until it feels safe. That produces a number that is simultaneously too high to win and too vague to defend.

We price the first pile firmly, bracket the second with an explicit range, and carve the third out as a named investigation with its own small fixed cost. Three numbers, clearly labelled, is more useful to an agency owner than one number with a shrug attached.

What we ask for up front

A day is enough because we ask for very little, and what we ask for is specific:

• Whatever already exists — a Figma file, a brief, a deck, a Loom, even a voice note
• The outcome the client has actually been promised, in their words not yours
• The deadline, and whether it is real or aspirational
• Any stack constraints — their hosting, their CMS, their existing codebase
• What has already been tried, if anything

We do not ask for a requirements document. If one exists we will read it, but requiring one pushes the work of scoping onto the person asking for a scope, which defeats the point.

The part that makes it fast

The genuine accelerant is that we are not estimating from scratch. A bench that ships similar work repeatedly accumulates a reference library of what things actually took, as opposed to what they were quoted at. A marketing site with a headless CMS and six templates has a known shape. So does a design system with forty components, or a React Native build with social auth and payments.

Speed does not come from thinking faster. It comes from having already thought about something very similar.

When a brief falls outside the library, we say so, and that project does not get a 24-hour scope. It gets a short paid discovery instead. Pretending otherwise would just be guessing with more confidence.

What you get back

The deliverable is deliberately short — one page that an agency owner can forward to a client with minimal editing:

• A fixed scope with what is explicitly excluded, which matters more than what is included
• A milestone schedule with dates, not durations
• The name of the person who will lead the build
• The price, split into firm and ranged components
• Assumptions, listed plainly, so a wrong one can be corrected before it becomes expensive

That assumptions list is the part clients and agencies both skim and both regret skimming. Almost every scope dispute we have seen traces back to an assumption that was written down, never read, and later contradicted. Read it. It takes two minutes and it is the cheapest risk reduction available.

Fast is not the same as loose

A 24-hour scope is a commitment, not a sketch. If we get it wrong on something we said was firm, that is ours to absorb. That constraint is exactly why the three-pile split matters — it keeps us honest about what we are actually willing to stand behind on day one.