Every new engagement at Cilantrobyte opens with two weeks of doing almost no building. No sprint planning, no tickets, no commits. Just reading, listening, and writing. It is the single most valuable thing we do, and it is the single most often questioned by clients who are in a hurry.
The pitch we hear most often is some version of: "We already know what we want built — can you skip the discovery and start shipping?" The honest answer is no, and the less honest answer is: yes, but you will pay for it three times over before the end of the quarter.
Here is what those two weeks actually contain. We interview between six and twelve people on your team, across functions. We read whatever strategy docs, PRDs, and decision histories exist. We audit the code if there is any. We talk to your users — sometimes five, sometimes fifty, depending on the phase. And we write. A lot.
At the end of two weeks you get a written recommendation that almost never matches the brief you came in with. Sometimes it is bigger — we found a dependency that means we cannot start here, we need to do this other thing first. Sometimes it is smaller — the thing you thought needed a rebuild actually needs a three-week intervention. Sometimes it is different entirely.
That written recommendation is the artefact that earns us the right to do the next six months of work. If we got it wrong, you walk away at a fraction of the cost of a failed engagement. If we got it right, the next six months have a chance of actually working.
The temptation to skip this is enormous — for clients, for us, for the whole industry. But every senior engineer and designer you have ever worked with has a collection of scars from the time the discovery was skipped. That collection is what makes them senior. It is also what makes them careful.