Why we estimate after discovery, not before

Every engagement starts with a question the client cannot answer and most suppliers will not: how long is this going to take? The honest answer at first contact is that nobody knows, because nobody has watched the work happen yet.

The common response is to give a number anyway. It sounds decisive, it wins the meeting, and it is a guess. The gap shows up in month three, when the thing nobody asked about turns out to be the hard part.

We do it in the other order. Discovery is a short, self-contained engagement that produces a measured map of how the process actually runs and a written estimate for whatever you decide to do next. You can take that map elsewhere. Several clients have, and one came back with our own document annotated by a competitor.

Two things make the estimate land close. The first is that we are estimating work we have already looked at rather than work we have imagined. The second is that we estimate on the conservative side on purpose: an operation planning around a delivery date would rather hear a longer number and get it early than hear a shorter one and rearrange twice.

Scope still moves — it always does. What we will not do is let you find out at the deadline. Anything that changes the schedule gets a revised estimate before the work happens, so the news arrives while you can still act on it.

The part clients underestimate is how much the map itself changes the conversation internally. A measured picture of the current process is something a finance director can read and a supervisor can argue with. Those arguments are cheap in week two and expensive in month four.