About 18 months into building GenRes, we got an inquiry that looked perfect on paper.
Established business. Clear budget. Defined timeline. The kind of brief that would have made for a good case study if it had gone well.
We got three calls in before we admitted to each other what the discovery process was telling us: this project wasn't a good fit.
Not because the client was difficult. They weren't. Not because the scope was technically beyond us. It wasn't. But because what they were describing as the problem wasn't the actual problem—and building what they asked for would have produced something that looked successful and didn't work.
The real issue was upstream of the product. They needed to fix how their team handled client requests before building a client-facing system on top of that process. The system they wanted would have automated a broken workflow and delivered it faster.
We said that. They pushed back. We said it again. They were committed to the original brief.
We declined the project.
That conversation cost us a significant contract and took about three weeks to stop feeling bad about.
Here's what it taught us:
Saying yes to the wrong project is not neutral. It costs you the time you could have spent on the right one. It costs your team the energy that gets spent managing a misaligned engagement. It costs you your reputation if the outcome is mediocre—even if it was technically what was asked for. And it costs the client, who ends up with something that doesn't solve their actual problem.
The hardest version of this is when the client is good, the budget is right, and the misalignment is subtle. When you have to articulate—to yourself first, then to them—exactly why the brief is solving the wrong problem and why you can't in good conscience take it as written.
That requires knowing what you're building things for. Not just technically. But in terms of what a successful outcome actually means.
At GenRes, we've built that into every engagement: a discovery phase that's specifically designed to find the gap between what's being asked for and what's actually needed. Sometimes they're the same thing. Sometimes they're not.
When they're not, we say so, even when it's expensive to say it.
We think that's the only version of this work worth doing.
