The most valuable hour of any project

The most expensive mistakes I've seen on projects were all made in the first week, before a line of code existed. Someone said yes to a vague brief, everyone assumed they meant the same thing, and the gap didn't surface until it was expensive to fix. The cheapest place to solve a problem is a conversation. The most expensive is production.

So the first real hour I spend with any client isn't about design or tech. It's about pinning down what we're actually building, and just as importantly, what we're not.

Most people arrive with a feature list. My job is to get underneath it to the outcome they actually want, because the feature list is usually wrong in small ways that matter. Someone asks for a booking system when what they need is fewer no-shows. Someone wants a dashboard when they really want one number, emailed to them every Monday. Build the request instead of the need and you can ship exactly what was asked for and still miss completely.

The other half of the hour is cutting. Every project wants to grow, and a good scope is mostly a list of things you've agreed to leave for later. That conversation is uncomfortable, because everything feels essential to the person whose idea it is. But protecting a first version from its own ambition is one of the most useful things I do for a client, even when they don't notice it happening.

Clients rarely point to scoping as the valuable part. They remember the launch, the design, the thing they can show people. But the launch went smoothly because of an unglamorous hour at the start where we decided, together and out loud, exactly what success looked like. I've come to think that hour is the real work. Everything after it is just execution.