On scoping AI projects when building has never been cheaper.
Building software used to be the expensive part. It took months, it took a team, and it took money you couldn't get back. So it made sense to be sure of what you were building before anyone started, because the cost of being wrong was paid in burnt quarters. That logic ran the industry for decades, and most teams still carry it around. The trouble is it has quietly inverted, and the instinct it produced now points the wrong way.
The inversion nobody priced in
When building was the bottleneck, a rough brief was survivable. You would discover the holes during the build, slowly and expensively, but you would discover them. The long grind of construction forced the questions into the open. Generation has removed the grind. A capable team can now have a working prototype by Friday. And the moment building stops being the hard part, the hard part becomes the thing building used to smuggle in for free: knowing what is worth building. That is the one job a generator cannot do for you. So cheap generation did not lower the value of discovery. It raised it. The demo is cheap now. The judgment is the asset. You do not have to take my word for it: DORA's 2026 research found the same thing from the other direction, that as AI speeds up code generation the bottleneck moves to specification, and the spec stops being overhead and becomes the scarce resource.
I am not preaching from above this. I like opening the laptop and making something. The pull to skip the talking and get to a prototype is one I feel more than most, because building is the part of the work I enjoy most. So when I argue for discovery I am not arguing against an instinct I lack. I am arguing against one I have to manage in myself.
What a working demo tells you
I watched that instinct play out from the outside not long ago. A fast-growing company came to me already certain what it wanted built. They had sketched the architecture themselves and had lessons from a previous tool; what they wanted from me was a partner to help ship it. To their credit, they moved. They ran a quick, scrappy version of the idea and got a spread of working demos across different parts of the business. The energy in the room was real. The question I asked them afterwards was not whether the demos were impressive. It was whether any of it had shipped, or whether it had stayed in demo form. Because those are different outcomes, and the distance between them is where the work lives.
That distance is the whole point, and it is worth being precise about why it opens up. A working prototype answers one question well: can we build this? But that was almost never the question that mattered. The question that mattered was whether you should, and whether the thing you built is even what you wanted once it exists in front of you. Building tests feasibility. It does not test desirability, and the two feel similar right up until you are holding something that works and realising it solves a problem you do not have.
Why round two goes bigger and lands flatter
Novelty hides this for a while. The first version carries a charge simply from being new, which is why a second attempt so often goes bigger and lands flatter. The novelty has worn off, and no structure was underneath it. By structure I mean the unglamorous things a one-off skips: a clear view of whose work changes, what the prototype is supposed to replace rather than merely demonstrate, and how you would know in a month whether it stuck. A quick build can dazzle without any of that, because for one afternoon the excitement does the load-bearing. The version that compounds has decided, before it builds, what it is willing to be measured against. Fast generation lets you reach the disappointment sooner when that decision was never made. It feels like speed. It is a longer road, because now you are unpicking a built thing instead of rethinking an idea, and you are attached to it.
The better use of a cheap generator
So what should a team do with all the time and money that cheap building has handed back? The temptation is to spend it building more, and faster. The better move is to spend it sparring. The same tool that will generate the thing for you will also argue with you about whether the thing should exist. That second use is worth far more in the phase where you are most tempted to skip it. Point the generator at your own reasoning rather than your output, and make it earn the idea before you build it. That is discovery, done in an afternoon, for free, and it is the part nobody wants to pay for precisely because it does not produce anything to demo.
Which is why discovery is the line item clients most often want to cut, and the one I hold. Not because the deliverable is impressive to look at. Because it is the only part of the engagement that decides whether the impressive part was worth building.
What is left when building is free
The cost of building collapsed. The cost of building the wrong thing did not move at all. That is the whole of it. The discipline worth paying for was never the construction. Construction was only ever a proxy for the thing we wanted: something worth having built. Generation made the proxy cheap and left the real thing exactly as hard as it always was. It is no longer hidden inside the months it used to take to find out. Knowing what deserves to exist is still the job.
