The Difference Between an AI Vendor and an AI Advisor - and Why It Matters More Than the Technology

What the last year of implementations taught me about what CEOs actually need from an AI partner

There’s a question I’ve started asking myself at the beginning of every client engagement, and it’s not a technical one. It’s this: are we here to build what the client asked for, or are we here to help them figure out what they actually need?

The answer to that question determines everything - the shape of the project, the nature of the relationship, and ultimately whether the implementation delivers lasting value or simply delivers what was scoped.

The vendor mindset is seductive in its simplicity. Client arrives with a brief. You assess feasibility, agree a price, build the thing, deliver it. Success is measured by whether the deliverable matches the specification. It’s clean, contractually straightforward, and completely inadequate for AI implementation.

Here’s why. As I’ve written about across this series, AI projects have a particular characteristic that distinguishes them from almost every other technology implementation: the client’s understanding of what they need changes fundamentally in the process of getting it. Requirements don’t just evolve - they expand, as the technology reveals possibilities that weren’t visible before the build began.

None of these outcomes are failures. But none of them are things a vendor relationship is designed to handle. A vendor delivers the brief. An advisor helps navigate what happens when reality turns out to be more complex and more interesting than the brief.

The shift in posture is significant. An advisor brings a perspective that the client doesn’t have - not because the client lacks intelligence, but because they’re too close to their own operations to see them clearly. When stakeholders give conflicting descriptions of the same process, someone needs to hold that tension and work toward resolution rather than simply picking one version and building to it. When a working prototype reveals that the original scope was too conservative, someone needs to have the honest conversation about what the project should actually become.

What does that actually look like in practice? It looks like a series of conversations that go beyond the technical. It looks like asking a CEO not just what they want to automate, but what they’re trying to achieve in the next two years and whether automation is actually the right path to get there. It looks like flagging when a client’s internal processes need attention before AI can do anything useful with them. It looks like being willing to recommend a smaller, faster solution when the instinct of the room is toward something more impressive but less likely to deliver.

It also looks like staying in the room when things get difficult - which, as I described in the last piece, is ultimately where the character of a relationship is decided.

The CEOs I’ve worked with who have gotten the most from AI implementation share a common characteristic. They weren’t looking for a technology supplier. They were looking for someone who understood the technology deeply enough to tell them the truth about what it could and couldn’t do for their specific business - and who had enough invested in the outcome to say the difficult things when the difficult things needed saying.

That kind of relationship doesn’t come from a sales process. It comes from demonstrated judgement over time - from being right about the things that turned out to matter, and being honest about the things that didn’t go as planned.

The technology in AI is advancing faster than most businesses can track. What isn’t changing is what good advisory looks like: someone who knows more than you do about a consequential decision, has your interests genuinely at heart, and will tell you what you need to hear rather than what you want to hear.

If you’re evaluating AI partners right now, I’d suggest the most useful question you can ask isn’t about their technical capabilities. It’s about the last time they told a client something the client didn’t want to hear - and what happened next.