Why I only take projects I know I can solve
The best thing I ever did for my clients was get comfortable with a two-minute phone call that ends with "this isn't the right fit." Here's why — and what it actually looks like in practice.
Early in my career I took every project. That's what you do. You need the work, you're building a track record, and saying no feels like leaving money on the table. The problem is that taking projects you can't fully deliver on doesn't build a track record — it builds a reputation for almost.
Almost works. Almost on time. Almost what they needed.
Almost is the most expensive word in consulting.
The real cost of a misaligned project
When you take on work that isn't in your wheelhouse, a few things happen. You spend more time than you budgeted trying to get up to speed. The client can tell — not always explicitly, but they feel it in the pace, the questions you're asking, the confidence in your recommendations. And because you're stretched, the parts you are good at get less attention than they deserve.
Everyone loses. The client gets a diluted version of the outcome they were after. You deliver something you're not proud of. And you've spent six weeks on a project that, at best, generates a lukewarm referral and, at worst, a conversation you'd rather not have.
The math doesn't work even when you factor in the invoice.
What "I know I can solve it" actually means
It doesn't mean I've done exactly this before. It means I can trace a clear line from where the client is to where they need to be — and I understand every step in between well enough that there are no hidden variables that could derail it.
For the work I do — AI workflows inside marketing and sales functions — that line is usually visible within the first conversation. The problems I'm built for have a particular shape: a team that already ships, a process that's working but has clear bottlenecks, an outcome that's measurable. When those three things are true, I can tell you roughly what the workflow will look like before we've agreed to work together.
When they're not — when the outcome is fuzzy, or the team isn't ready to adopt new tooling, or the problem is actually a people issue wearing a technology mask — I say so. That conversation is uncomfortable for about two minutes. The alternative is uncomfortable for two months.
How I handle the conversation
I don't wait for a proposal to tell someone it's not the right fit. If I can see it in the discovery call, I say it then. Something like: "Based on what you've described, I don't think I'm the right person for this — here's why, and here's what I think you actually need."
That's it. No apology, no hedging. People respect directness. Most of the time, they appreciate the honesty more than they would have appreciated a mediocre engagement. And occasionally — more often than you'd expect — they come back six months later when the problem is the right shape.
The discipline of saying no is what makes the yes worth something. If I take everything, my involvement signals nothing. If I only take projects I know I can solve, then when I say yes, that carries weight — for the client and for the work.
That's the deal. Boutique by design, not by accident.