How I Scope a Project Now That a Prototype Takes an Afternoon

A client watched a rough version of what they wanted come together in an afternoon, then asked, reasonably, why the whole thing would take weeks. It is a fair question, and it made me realise my old way of scoping did not have a good answer anymore.

The old estimate leaned on how long the building would take, because building was the expensive part. When the building collapses to an afternoon, an estimate built on it falls apart, and you are left looking like you are padding a number to protect a fee.

And the client is not being unreasonable. They watched the thing appear. From where they sit, the hard part visibly already happened, in an afternoon, in front of them. Any number I attach to the rest now has to survive the memory of that afternoon, and none of the old how-long-will-it-take reasoning survives it. I had to find a genuinely different way to talk about where the time goes.

So I had to get honest, with clients and with myself, about where the time really goes. Almost none of it is the first working version. The weeks are everything between a thing that runs in a demo and a thing you can put in front of real users without wincing.

The decisions about what it should actually do. The edge cases the demo skipped. The integration with the messy system the client already has. The part where one real user does something nobody imagined and it has to not fall over. And the quiet, unglamorous work of being sure it is right before it touches anyone. The prototype proves the idea is possible. The weeks are the distance to it being safe.

That distance did not shrink when the building got fast. If anything it got more visible, because it used to hide inside the long build and now it stands alone, plainly, as the only part that still takes real time. A prototype and a product look similar and are separated by everything that actually matters.

I stopped estimating the build and started estimating the decisions and the risk. I ask what still has to be decided, where the real integration pain is, what happens on the paths the demo did not walk, and how sure this has to be before it ships. Those are the things that take time now, and naming them is what makes an estimate defensible when the client has just watched the easy part happen in an afternoon.

I have also started showing clients the rough version early on purpose, and then being explicit that the gap between this and done is the work I am actually quoting for. It reframes the conversation before the "why so long" question arrives. The demo is not the thing you are buying. It is the cheapest, most visible slice of it.

The reframe does more than protect the fee. It sets the client up to value the right thing. If they think they are paying for the building, every week feels slow. If they understand they are paying for the decisions and the safety, the weeks make sense, and the conversations get easier, because we are both looking at the same real work instead of arguing about a number.

The uncomfortable upside is that this exposes anyone whose value was mostly in the building. If that was the offer, it is genuinely under pressure now, because the building is the part that got cheap. What survives is being able to say, clearly, what the rest of the work is and why it is worth the weeks.

That is not a bad place to end up. It pushes you toward the part of the work that was always the point and was easy to hide behind billed hours. When the hours get cheap, you have to be able to name the value directly, and the people who can will be fine.

It also changes what you are selling. The old pitch was capacity: so many people, so many weeks of building. The new pitch is judgment: I will work out what actually needs to exist, make it survive contact with your real users, and be answerable for it. That is a harder thing to put on a rate card and an easier thing to be proud of, and it happens to be the part the tools cannot do for either of us.

So if a prototype now takes you an afternoon too, the real question is the one your client is about to ask: can you say plainly what the weeks after the afternoon are actually for?