Contents
Three concepts to keep apart
A measure is objective and numerical (a time, a volume). A metric (or indicator) quantifies something more subjective, such as satisfaction or perceived effort, often by combining several measures. ROI is a financial metric that expresses the expected gain or loss relative to the cost of an investment. Confusing these three concepts is the leading cause of a poorly built ROI case that the finance function then rejects.
Customer lifetime value (CLV): the cornerstone of the calculation
Customer lifetime value adds up the future revenue expected from a customer, adjusted for the retention rate and discounted over time, minus the cost of acquisition. It answers very practical questions: how much to invest in acquisition, what future revenue can be expected, and how much it is justified to invest in retention rather than in acquiring new customers alone.
Leading and lagging indicators
Leading indicators (long waiting times, processing backlogs, service outages) predict a coming deterioration in customer experience, so you can act before the problem reaches the customer. Lagging indicators (actual churn, final satisfaction score) confirm an outcome that has already happened. A robust ROI case relies on both: leading indicators to manage, lagging indicators to prove.
The link between employee experience and financial results
The link between employee experience and a company's financial performance, documented as early as the 1990s under the name "service-profit chain", remains one of the strongest arguments for justifying an investment in customer experience: an organisation cannot sustainably deliver a good experience to its customers with disengaged teams.
Building a convincing ROI case
A customer experience ROI case is always stronger when it is built with the finance function, not against it or without it. This ensures that the calculation methods are consistent with the way the company already evaluates its other investments, and it gives the case a credibility that no stand-alone presentation can achieve.
Worked example (illustrative)
Take a services company with 2,000 customers under contract, an average annual margin of 3,000 MAD per customer and annual churn of 15%. If it brings churn down to 12%, it keeps 60 more customers each year. That represents 180,000 MAD of margin preserved per year, before counting referrals or additional sales.
These figures are hypothetical and serve only to show how the calculation works.
Building a first ROI case in Morocco
- Establish a baseline. Many companies do not have a reliable history of customer data. Three to six months of measurement before any initiative gives you a credible point of comparison.
- Think in dirhams. Express every gain in MAD: the cost of a call or ticket avoided, the margin on a retained customer, an increase in average basket size.
- Stay cautious. Use low assumptions. A conservative case that proves out is worth more than an ambitious projection that undermines the programme's credibility.
- Involve the finance function from the start so that the calculation method is the company's own.
Practical checklist
- Choose two or three financial levers at most.
- Measure the current situation before launching the initiative.
- Document every calculation assumption.
- Separate proven gains from estimated gains.
- Present the results together with the finance function.
Further reading
- 3 min read
- 4 min read
- 4 min read
Frequently asked questions
Can the ROI of customer experience always be measured in money?
Most of the benefits can be expressed in financial terms (retention, lower support costs, additional revenue), but a qualitative share (reputation, brand preference) is harder to quantify. It should be presented as such, without forcing an artificial conversion.
Do you need specialist software to calculate this ROI?
No. The data usually already sits in the company's CRM, support and finance systems. The difficulty is generally not collecting the data but linking it together coherently.
General information, not legal advice.
Report an error