What We Look for in a Client Before We Look at the Project
The tech stack rarely kills a project. The relationship does.
Every intake call starts the same way. Someone walks us through the project: the features, the timeline, the budget, sometimes a deck. We listen, we ask questions, we take notes. But we're not really evaluating the project yet. We're evaluating the person describing it.
This isn't a personality test. It's risk management. Complex software takes months, sometimes years, of close collaboration. The spec you start with is never the spec you finish with. What matters more than the initial idea is how a client behaves when the idea has to change, because it always does.
The first thing we look for is whether someone can tell us what they don't know. Clients who have an answer for everything, instantly, tend to be the hardest to build for — not because they're difficult people, but because certainty leaves no room for the discovery that good engineering requires. We'd rather hear "I'm not sure, what do you think" than a confident answer to a question nobody has actually solved yet.
The second thing is how they talk about past vendors or past teams. Everyone has a bad-agency story. But there's a difference between someone who learned something from it and someone who's still relitigating it. We're listening for whether the last failure made them more precise about what they need, or just more suspicious of everyone who might build it next.
The last thing, and maybe the most important, is whether they can sit with an unfinished answer. Complex builds live in ambiguity for long stretches — architecture decisions that won't prove out for weeks, tradeoffs that look wrong until they're right. Clients who need daily certainty either slow the work down demanding reassurance, or push for premature decisions that cost more later. The ones who can hold open questions alongside us are the ones we end up doing our best work for.
None of this shows up on a project brief. It shows up in a forty-minute call, in the questions someone asks back, in what they get anxious about and what they don't. We've learned to weight it heavily, because the technical problems are the part we're actually good at solving. The relationship is the part that decides whether we get the chance.