Recently I spent time doing a deep dive on an enterprise AI platform — features, integrations, pricing model, implementation requirements, real-world reviews. The kind of research that takes hours and gives you an actual informed opinion rather than a surface-level take.
The conclusion was: don't do it.
Not because the platform is bad. It's actually well-built, and for the right organization — a large, multi-location operation with an existing enterprise software stack and a significant support volume — it might make a lot of sense. But for the client conversation I was preparing for, it just wasn't the right fit. The pricing floor was steep, the implementation timeline was long, and there was a simpler path that would solve the actual problem without the overhead and vendor dependency.
Here's the thing: I could have gone the other direction.
There was a version of this where I say "let's explore it" — where I position myself as the person who helps implement it, manages the integration, owns the engagement. More scope, more revenue, more months of work. I'm a consultant. That's a real option. But it wouldn't have solved the problem. The client would have spent significant money, gone through a long implementation, and ended up with a platform that was designed for a different kind of organization. And I would have known that going in. So I couldn't recommend it.
There's a particular kind of relief in being able to say that clearly and without hesitation. Not "I'm not sure this is the right fit" or "there are some considerations to weigh" — just "I looked at this thoroughly, and this isn't the path." The research earned the confidence. The honesty was just the delivery.
I think this is rarer than it should be. Most consultants don't say no because saying no feels like leaving money on the table. There's always a way to scope something, frame something, make a project out of something. The incentives in consulting push toward yes.
But business owners and leaders know this. They've worked with advisors who are really just salespeople with a longer timeline. They've paid for recommendations that served the advisor more than the business. They know what it feels like to be told what they want to hear.
What they're actually looking for — even if they don't always say it out loud — is someone who will disappoint them when necessary.
Someone who will come back after doing real research and say "this isn't the answer, and here's why." Someone who treats their budget like it matters. Someone who is willing to make the relationship slightly uncomfortable in the short term because that's what actually helping looks like.
That kind of advisor is hard to find. It requires a certain confidence to say no when yes would have been easier, a certain integrity to prioritize the client's outcome over the size of the engagement.
It's also, in the long run, the only kind of advisory relationship worth having.
The technology research is the table stakes. Almost any competent consultant can evaluate a platform and understand whether it fits. The differentiator is what you do with the conclusion — whether you shape your recommendation around what's actually true, or around what's most convenient.
I'd rather be the person you call when you need a straight answer than the person you call when you want someone to make a decision feel inevitable.
Those are different jobs. I'm only interested in one of them.
If you're working through a technology decision and want someone who will give you an honest read — not a sales pitch — that's what I do. Let's talk!
