In the first article of this series, I wrote about how AI can turn your business and brand into kitsch if you introduce it while your foundations are still shaky. I also explained that digital transformation is about how a company operates, makes decisions, and creates value. Technology is simply the cherry on top.
In the second article, I explained where business transformation begins: always with a blueprint. A CRM Strategy Sprint lays the foundations for that system, bringing your data structure and operational processes together in one place.
Both articles revolved around premium service: exceptional service delivery and an outstanding customer experience. In other words, what guests see and experience firsthand. In this article, I want to address what remains invisible but without which premium service cannot exist: the system of workflows, data, and communication behind every customer interaction. That system is called RevOps, short for Revenue Operations.
If you've been following my articles, you may have noticed that I like using the metaphor of a house to explain how such a system is built. In the second article, CRM was its reinforced concrete foundation. But a foundation is not yet a house. The house still needs to be built. And whether it becomes a warm home or an expensive concrete structure nobody lives in depends on the people.
Let's start with the latter.
A House Nobody Lives In
The foundations have been laid. In other words, the CRM is in place, and processes and rules have been documented. Unfortunately, despite all that, everyday habits still tend to take over.
The sales team keeps returning to Excel because it's "faster and easier". Reports are generated, but nobody reads them, let alone uses them to make decisions. Marketing doesn't know what sales has promised the customer. Customer support spends its time putting out fires instead of becoming a place where additional sales opportunities are created. Meanwhile, new employees learn their jobs from colleagues, picking things up as they go, rather than following documented rules and processes.
Quite often, the problems begin in the foundations themselves.
In one digital transformation project, I worked with a company that had two brands, a paid CRM system, a newsletter tool, a task and document management tool, and email that wasn't connected to the CRM.
Nothing unusual for an initial setup. Just as it's not unusual for me to find chaos when I start examining an existing database and its data structure.
That was exactly the case here. The same customer appeared multiple times in the database, each time with slightly different information depending on which brand they had contacted.
A sale was considered successful as soon as an offer was accepted. That wouldn't necessarily have been a problem if there had been a process to track whether payment had actually been received.
As things stood, nobody really knew what had been completed and what hadn't.
And that's where any discussion about automation based on customer behaviour comes to an end. You simply cannot automate customer interactions when you don't have accurate, relevant customer data.
These situations aren't limited to micro and small businesses, or to Croatian companies.
Research suggests that as many as 55% of CRM projects drive customers away and reduce profitability.
Yes, drive customers away.
That's because CRM systems are often introduced before a customer-focused strategy and supporting processes are in place. As a result, customers are contacted too frequently, receive irrelevant offers or incorrect information, and instead of feeling valued, they feel bothered.
The underlying problem is almost always the same: CRM is treated as software that will manage customer relationships for you.
Without people who actually use it, even the best-designed system simply creates more expensive chaos.
Between Planning and Execution
A strategy on paper only produces results when someone puts it into practice, consistently, every single day.
And people often resist change because they don't understand why it's happening.
An older study involving 8,000 managers across 250 companies found that only 55% of middle managers could name at least one of their company's five strategic priorities.
My experience suggests we haven't made much progress since then.
That's why the second phase of my CRM Strategy service, CRM Strategy Adoption, begins where the blueprint ends.
By changing how a company works, we establish RevOps: a way for marketing, sales, and customer support to work together, use the same data, and pursue the same goal — predictable revenue.
Remember the example from my previous article, where marketing launches a cold outreach campaign targeting a customer who is already in discussions with sales?
Or customer enquiries that disappear without anyone knowing what happened to them?
These are precisely the problems this service addresses.
Once the system's structure is sound and the data is clean, what remains are habits and consistency. And those are developed through adoption.
Four Layers of One System
Consistent sales performance comes from a system that follows the entire customer journey, from the first interaction to the moment a customer returns and recommends you to others.
A well-designed transformation project that builds such a system has four layers. None can function properly without the others.
The first layer — customer experience as one continuous journey.
Marketing makes the promise, while sales and customer support deliver it.
When these teams aren't aligned, each develops its own processes. Instead of becoming a source of additional revenue, customer support turns into a complaints department.
This disconnect has been discussed for decades, and the conclusions consistently point to the same outcome: the entire organisation and its revenue suffer.
The second layer — technology and the team.
This is where the question of "how do we want customers to experience our business?" becomes a set of clear rules: who does what, and according to which standards.
CRM is the backbone of this layer, but its effectiveness depends on how well it connects with other tools and how consistently people use it.
The same applies to reports.
They're useful only if they help you decide where to invest more and what to stop doing.
This is where the old rule applies: measure twice, cut once.
The third layer — ownership of execution.
Someone needs to set the direction and standards and make sure every step happens when and how it should, while the team remains responsible for customer relationships.
This layer also reveals which customer relationships and pricing decisions actually generate profit and which eat into it.
And that's something most companies lack.
The fourth layer — transferring knowledge to people.
Everything is built with the goal of having someone inside the company who understands the system and can manage it independently.
That means training the team and explaining why things have been set up in a particular way.
It also means coordinating external partners, agencies, and freelancers so everyone is working towards the same goal.
A project structured this way requires someone who works from within the business, as part of the team.
That's why I usually lead these projects through a fractional engagement model.
The goal is always the same: by the end of the project, the company should have both the person and the system needed to operate independently, without me.
CRM Strategy Adoption makes sense for businesses that already have customers and at least a blueprint, whether they've completed a Sprint or already have a CRM system that nobody really uses.
It's particularly relevant for companies whose teams have grown beyond the point where the owner can remain the bottleneck for every decision.
If you don't yet have a blueprint, start with the Sprint.
The Weakest Link Is Always Human
As with any house, the people living in it are what matter most.
A system is only as strong as its weakest link, and that link is almost always a person: someone who doesn't understand the system or works around it because nobody has explained why it exists or how to use it.
That's why people on both sides must be at the centre of projects like these: the customer who pays and the employee without whom the entire system remains little more than words on paper.
Every process and every decision must make sense for both.
Business research has been examining this relationship since the 1990s, consistently finding that satisfied employees create value that customers can feel, and that this value leads to loyalty and profit.
If I remember correctly, one of those studies showed that customer satisfaction dropped from 75% to 55% after an employee left.
A system that people actually use also adapts over time.
For example, a report might reveal that customer enquiries consistently stall immediately after an offer has been sent.
The team changes how follow-ups are handled, the customer receives a timely response, and that improvement translates into revenue sooner.
And that is precisely the premium service I discussed in my first two articles.
It's what customers experience when you welcome them as someone you already know and provide an answer before they've even had to ask.
Three Articles, One House
At the end of the journey, from foundations and blueprints through adoption, stands RevOps.
This is the kind of business transformation I believe in, because I've yet to meet a business owner who wouldn't want their company to generate revenue independently of individual employees' goodwill, including their own.
Premium service then becomes the natural result of a well-coordinated system.
If your revenue still depends on who's working that day and what mood they're in, it's time to seek support.
If you'd like us to build that house together, get in touch for an informal conversation. We'll identify the weakest link in your system and explore what can be done about it.
And if you decide to work with someone else or manage the transformation yourself, it's useful to know which skills to look for.