On Saying No to Certain Client Engagements — By Prashant Chaudhari

One of the most counterintuitive lessons I've learned running ITD GrowthLabs is that saying no to certain client engagements is the highest-leverage business decision I make. It sounds obvious. It isn't — most services company founders say yes to almost everything, and most services companies underperform as a result. Here is my thinking, unfiltered.

The Default Trap: Say Yes To Everything

The default mode in services is to say yes to any engagement that pays. Growing companies especially. You need the revenue, the team needs the work, and every 'no' feels like leaving money on the table. This works fine for the first ₹10-20 Cr of revenue. Past that, it silently destroys everything: team morale, project quality, retention, referrals, culture. Companies I've seen fail past ₹40 Cr almost all trace their failure to a period of saying yes indiscriminately.

The Fit Assessment We Actually Do

Before we take on any engagement above a certain size, we ask five questions:

1. Do we respect the founder / CEO? Not 'do we like them.' Do we respect how they think, decide, and communicate?
2. Is the work in our zone of genuine competence? Not adjacent competence. Real competence.
3. Are the economics healthy? Will this engagement produce healthy margin and healthy work-life balance, or will it be a grinding low-margin drag?
4. Is the client's operating model compatible with ours? Do they want a partner or a vendor? Are they willing to trust our judgment or will every decision become an approval cycle?
5. Would this engagement make us better at what we do? Would we learn, level up, sharpen our capability — or just cash the cheque?

If we can't clearly answer yes to at least four of five, we don't take the engagement.

The Engagements We Have Turned Down

Founders whose decision-making we didn't respect. Projects clearly outside our zone of competence (very deep specialised hardware, for example). Engagements where the fee felt fine but the operational drag was obvious. Clients who wanted us to work through 3-4 approval layers on every decision. Projects that would be interesting for 3 months and then be maintenance-drag for 3 years.

What Happens When You Say No

The immediate cost is real — foregone revenue, awkward conversation, sometimes disappointed prospects. The compounding benefit is much larger. Team stays fresh. Quality on the engagements you take is dramatically higher. Retention improves. Word-of-mouth referrals from good clients bring more good clients. Culture stays strong. Everyone stays motivated.

The Reverse Recommendation

The engagements you say yes to should feel obvious. Founder you respect, work you're excellent at, healthy economics, compatible operating model, learning opportunity — the yes should be a 'hell yes,' not a maybe. Every 'maybe' engagement I've said yes to over the years, I've regretted. Every 'hell yes' has compounded.

What This Means for How We Sell

We invest more time in the sales conversation than most services companies do. Not to close harder — to figure out if the fit is real. Sales meetings sometimes turn into us telling the prospect why they'd be better off with a different partner. This costs revenue in the short term. It builds a filter that produces our best engagements over years.