Consultants produce deliverables. Discovery reports, process designs, business cases, implementation plans. These are the visible outputs of the work.

They’re also the easy part.

The hard part is everything around them. Understanding why the organization works the way it does. Getting the right people to care about changing it. Navigating the politics that determine whether a recommendation gets implemented or filed away. Building enough trust that people tell you what’s actually going on rather than what they think you want to hear.

I’ve been consulting on CRM and revenue operations for over ten years. The projects that succeeded were never the ones with the best documents. They were the ones where I understood the organization well enough to position the work correctly. And the ones that failed usually had solid analysis that nobody acted on — because the groundwork wasn’t there.

Understand why things are the way they are

Before you propose a change, understand why the current situation exists. Not as a problem to diagnose, but as a series of choices that made sense at the time.

A manufacturer with a five-day quote turnaround didn’t end up there by accident. At some point, someone decided that sales engineers should validate every configuration. That made sense when the company had 20 customers and three products. The process stuck. People were hired into it. Nobody revisited the decision because it became invisible — just “how we do things here.”

A company without a renewal process didn’t forget to build one. They prioritized acquisition. Every budget cycle, retention operations lost to something that felt more urgent. That pattern tells you what leadership values and what kind of argument will land.

If you skip this step and walk in with “your process is broken, here’s how to fix it,” you’re implicitly telling everyone involved that they’ve been making bad decisions. That’s not how you build trust. That’s how you create resistance before the work has started.

The better approach: recognize that the current state was a reasonable outcome of previous priorities. Then make the case that the priorities need to shift. The business has grown. What worked at €10M doesn’t work at €50M. The argument isn’t “you were wrong.” It’s “the situation has changed.”

Get close enough to see what’s really happening

The sanitized version of a client’s operations is what you get in kickoff meetings and stakeholder presentations. The real version is in the spaces between.

How do people actually work? Not the process on the slide deck. The actual daily reality. Which tools do they use and which do they avoid? Where do they keep the information they actually rely on — and it’s rarely where it’s supposed to be. What workarounds have they built?

The gap between the official process and the real one is where most of the value of consulting lives. You can’t find it from a meeting room. You find it by sitting next to the person who does the work. Watching them build a quote. Listening to how they explain pricing to a customer. Noticing that they have a personal spreadsheet that tracks things the CRM should be tracking but doesn’t.

Ask to sit in on sales calls. Ask to see how a renewal actually gets processed, step by step, by the person who does it. Ask to look at the CRM the way a rep sees it — not the way an admin configured it. The difference between those views is usually where the biggest opportunities are.

Listen to the language

Every organization has its own vocabulary. The words people use reveal what they value, what they resist, and what kind of change they’ll accept.

If leadership talks about “customer lifetime value” and “retention,” your recommendations should use those terms. If they talk about “pipeline velocity” and “win rate,” frame them there. If they talk about “operational efficiency,” you’re in cost-savings territory and you’ll need to bridge gradually toward a revenue argument.

Listen for the phrases that get repeated. “We’re a sales-driven organization” tells you where the power sits. “We tried something like this before and it didn’t work” is the objection you need to address before proposing anything new. “We need to be more customer-centric” is a door you can walk through.

Listen for the stories too. Every organization has myths: the project that went badly, the tool that nobody adopted, the consultant who didn’t understand the business. These stories shape how your work will be received. If the last CRM implementation failed, your approach needs to address why this time is different before it addresses anything else.

You can also introduce language. If you consistently frame problems in terms of revenue impact rather than cost savings, that framing starts to spread. Language shapes how people think about their business. Using it deliberately is one of the most underrated tools a consultant has.

Change at two speeds

Some recommendations align with how the organization already thinks. The sales team wants faster quoting. Finance wants discount visibility. The channel team wants dealers to self-serve. These run with the grain. Your job is to clarify the path and help them execute.

Other recommendations challenge existing beliefs. Shifting investment from acquisition to retention. Introducing discount governance where there’s been none. Restructuring how teams hand off customers. These run against the grain. They require changing how people think, not just what tools they use.

Both kinds of change are necessary. But they move at different speeds and require different approaches.

With-the-grain work is fast. Build it, show the results, move on. This is where you establish credibility.

Against-the-grain work is slow. It’s a campaign, not a presentation. You’re trying to shift mental models that have been in place for years.

A few things I’ve seen work:

Surface evidence gradually. Before proposing a change, start sharing data points in regular conversations. “I noticed our renewal rate drops for accounts where nobody engages until 30 days before expiry. Is that something you’re tracking?” Don’t present the solution yet. Establish the problem first. Let it become a recognized issue before you propose how to fix it.

Let the people closest to the problem speak. The account manager who tracks renewals in a spreadsheet. The dealer who calls every week to check on a quote status. The support rep answering the same question 30 times a day. Their frustration is more convincing than your analysis. Give them the data that quantifies what they already feel, and they become advocates for the change. Internal advocates always carry more weight than external consultants.

Bring the outside in. People inside an organization go blind to their own processes. What customers say in churn conversations. What competitors offer in their portals. How industry benchmarks compare to internal metrics. External evidence breaks the normalization. It shows that the world outside the building has moved, even if the internal process hasn’t.

Build on each win. Each successful initiative creates permission for the next one. The first project builds the track record. The third project runs on trust.

Pay attention to what gets deferred

The things an organization has postponed tell you more about its priorities than the things it has done.

If a company has operated for fifteen years without a structured renewal process, that’s not an oversight. Every year for fifteen years, something else was more important. Understanding what those things were tells you how leadership thinks about the business.

A company that consistently prioritizes acquisition has a set of beliefs about where growth comes from. Proposing a retention-first strategy isn’t just a process change. It’s a challenge to how they’ve thought about growth for years. That’s a slow argument. It requires data, external evidence, and small wins before the bigger proposal will feel natural.

Don’t assume these patterns are mistakes. Assume they were deliberate, or at least felt deliberate to the people who made them. Work with that understanding rather than against it.

The deliverable and the relationship

Early in my career, I spent most of my energy on the deliverable. Making the analysis sharp. The recommendation bulletproof. I assumed that if the work was good enough, it would speak for itself.

It doesn’t. Good work that nobody acts on is worthless. And mediocre work that’s positioned correctly within an organization that’s ready for it can create massive change.

The balance shifted over time. The deliverable still matters. Sloppy analysis undermines credibility. But the deliverable is maybe 30% of what determines whether a consulting engagement succeeds. The other 70% is understanding the organization, building trust with the right people, timing the recommendations correctly, and creating the conditions where change feels like the obvious next step.

The best compliment I’ve received from a client wasn’t about a document or a system. It was: “It felt like the team came to this conclusion on their own.” That’s the goal. Change that feels internally driven actually sticks. Change that feels imposed from outside gets reversed the moment the consultant leaves.

The document is never the hard part. Getting an organization to want what the document recommends — that’s the work.