Why Technology Cannot Save You From Skipping the Thinking

There is a quote Fiona Ngaruro heard in her first year of university that she still comes back to. Her lecturer said it once, almost in passing: technology is an enabler. It is not a solution. At the time she had no idea what it meant. Twenty years and a dozen markets later, she says it is the clearest lens she has for diagnosing why digital transformation fails.

The $1000 email platform that sent two emails

Fiona tells a story about a client she was brought into recently. A medium-sized business, exporting products globally through e-commerce. They had invested in a high-end platform setup: sophisticated e-commerce tooling, an email marketing solution integrated on top. Real budget. Real intent.

When she arrived, she asked a simple question: why did you choose this tool? Nobody could answer it clearly.

She looked at the email platform. In twelve months of having it, the company had sent two emails.

The lesson she draws is not about vendor selection. It is about the sequence that most organizations skip entirely: define the actual problem, assess which solutions genuinely fit, look at the people and processes in place, then introduce the technology. Most companies reverse the order. They buy first and think second.

What transformation actually looks like

When Fiona describes an organization that has been genuinely transformed by its CRM, she talks about traceability. You should be able to follow a logical line from every action the marketing or CRM team takes back to a strategic goal.

Data capture connects to segmentation. Segments connect to lifecycle journeys. Journeys connect to revenue outcomes. Everyone in the business understands why the tool is there, not just the team that bought it.

That last part is the real tell. In most companies, the tool is hanging on the side. A few people know how to use it. The rest of the organization treats it as someone else's responsibility.

"Transformation has been embedded in the organization. Everybody understands why this tool is there."

From campaigns to infrastructure

Most CRM teams run campaigns. A product launch. A seasonal promotion. Mother's Day. Send, report, repeat. It feels productive because there is always something going out.

What Fiona is describing is different. CRM as infrastructure means building the underlying systems that run whether or not anyone is actively sending something this week: lifecycle journeys triggered by behavior, segments that respond to data, automations that upsell and re-engage based on what a customer actually did.

She built this at Jumia across 12 African markets simultaneously, governing through standardized calendars, frequency guardrails, weekly check-ins across every country team, and testing in multiple languages including Pidgin English in Nigeria, French and Darija in Morocco, and Swahili in Kenya. The result was CRM growing from 18% to 30% of overall revenue.

The operational difference she describes between campaigns and lifecycle is essentially this: campaigns are one-offs that branch customers out of their journey temporarily. Lifecycle is the engine running underneath everything else, all the time.

"In the same amount of hours that you normally spend on sending these few campaigns out, you can do a lot, lot more."

The constraint advantage

The part of this conversation I keep thinking about is when Fiona talks about her work in constrained environments: SMEs in Kenya, women-owned coffee farms whose global buyers stopped traveling during COVID, fintech users who cannot pay by card because card penetration in the market is below 2%.

Her point is that in these environments, you cannot buy your way out of a poor understanding of your users. You have to start from where people actually are.

The practical example she gives is the coffee farmers. She went in assuming everyone knew how to build a content presence on Instagram. She quickly discovered that some of her students had never opened a Zoom call. She had to start from: click this link, now what do you see?

Budget does not protect you from misunderstanding your users. If anything, it sometimes insulates you from the feedback that would have caught the problem earlier.

The bottom line

The through-line in this conversation is about sequencing. Thinking before buying. Infrastructure before campaigns. Retention alongside acquisition. Understanding before building.

Fiona's single piece of advice for someone who has already bought a platform and is quietly worried it will not stick: pause. Go back to the original problem. Get clear on what you were actually trying to solve, and whether this tool genuinely maps to that. Then figure out what capabilities exist in the product that connect to that problem.

"Take a pause back and ask: what were we trying to solve initially?"

If that question makes you uncomfortable, that might be the most useful signal you have right now.

Connect with Fiona Ngaruro on LinkedIn and find her MarTech Unravelled Podcast on Apple, Spotify, and YouTube.