Most agencies say yes to almost anything with a budget attached. I stopped doing that, and it made the work better for the clients who remained — not because saying no is virtuous, but because a mismatched engagement produces worse outcomes for everyone in it, including the agency.

The pattern that changed my mind

Early on, I took every project that could pay. Somewhere around the fortieth or fiftieth client, a pattern became undeniable: the projects that struggled hardest weren’t the technically difficult ones — they were the ones where the founder and I disagreed on what “done” meant, or where the founder wanted a yes-person instead of someone who’d push back on a bad scoping decision. Technical difficulty is solvable. Misalignment on what actually matters isn’t, and it poisons everything built on top of it — this is the same root cause covered in Founder Clarity: The Hidden Cost of Confusion in Startups.

What “bad fit” actually looks like in practice

It’s rarely dramatic. It’s a founder who wants every competitor feature copied instead of validating their own hypothesis. It’s someone who needs a yes to every request regardless of cost or timeline impact, because pushing back reads as unhelpful to them. It’s a founder who hasn’t done any of the validation work covered elsewhere on this site and wants to skip straight to a full build — which usually means building the wrong thing well, which is worse than building the right thing imperfectly.

None of these are moral failings. They’re mismatches between what a founder needs and what this specific working relationship is built to deliver.

Why this benefits the clients who stay

Every hour not spent managing a mismatched engagement is an hour spent on a project that’s actually going somewhere. Selective intake isn’t about exclusivity for its own sake — it’s a direct trade: fewer, better-fit projects get more attention, faster decisions, and an advisor who can be honest without worrying about losing the account over a hard truth.

The questions I actually ask before taking a project

Not “what’s your budget” first — that comes later. First: has this been validated with real people, or is it still an assumption? Second: are you looking for someone to execute your exact spec, or someone to push back when the spec is wrong? Third: what happens to this relationship if I tell you something you don’t want to hear in week three? The answers to these matter more than budget size for predicting whether an engagement will actually work.

What I turn down, specifically

Projects with no validation and no interest in doing any before building. Founders who’ve already decided the exact solution before understanding the problem, who want a builder rather than a thinking partner. Budgets that don’t match the stated scope, where accepting the project would mean cutting corners that would come back to hurt the founder later. Turning these down isn’t picking winners — it’s being honest about what a good outcome actually requires from both sides.

Want an honest read on where your project actually stands? Send me a few lines about what you are building. Free 30-minute call, no pitch, no obligation. Available for founders in India and Australia. Book a Free Call →

Frequently asked questions