Roland Wabersich

← All case studies

Case study

Case study: Recurring revenue

From project business to 95% recurring revenue

value chain solutions GmbH · SaaS data platform · 2008–2025

How paid development and consulting became a predictable subscription business – and what was difficult along the way.

  • 40% → 95%recurring revenue, 2008 to 2025
  • 8.5 yearsaverage customer lifetime
  • 88%retention rate
  • 100%equity-financed

Starting point

value chain solutions started in 2003 with consulting on retailer data and automatic replenishment. The first customer projects were dominated by development: customers paid for part of the initial development of the platform, and recurring fees were low. Recurring, predictable revenue was nevertheless at the centre of the business model from the start. In 2008 its share was 40%.

Not a switch, but a path

There was no single trigger for the change. As the solution matured and grew, the share of paid additional development fell and the recurring share rose. At the same time, onboarding became more automated and therefore cheaper with every new customer. We did not pass this saving on as a discount but shifted it proportionally into the recurring fees.

What became product

We standardised everything that could be standardised functionally and technically. That took two to three cycles, mainly to find out which requirements several customers share.

The pricing model

Contracts usually ran for at least one year and could then be terminated quarterly. The price depended on the number of data sources and countries and on the data processes per week, plus customer-specific variables such as lines of business, product-retailer combinations or order lines. Customer complexity determined the base price, because the larger and more complex a customer is, the more effort it takes to support them.

The number of users on the customer side was limited. For customers this limit was practically irrelevant; for us it was a way to adjust if usage developed unexpectedly. Users on the retailer side were always unlimited, because the solution lives from collaboration with retail.

What was difficult

Justifying recurring fees was never the problem: daily data processing, cloud infrastructure and support were part of the service. Something else was difficult. The operating effort is almost the same for small and large customers, but small customers have far smaller budgets. We therefore adjusted the model several times, for example via the number of order lines transmitted or via a support model with a limited number of contacts and requests. Some of this worked very well, some of it remained a challenge.

A uniform price per data source was just as hard to convey: for a large customer it stood for 1,000 records, for a small one perhaps 10.

There were always special requests. In most cases we managed to have them paid for and then included them in the standard. Over the years, almost everything relevant ended up in the system. Or we convinced the customer to adapt their process to our standard as best practice.

Steering

We steered monthly with a few simple KPIs: total revenue, revenue by country and product area, share of recurring revenue, ratio of new to lost customers, revenue per salesperson, order lines generated and imports completed. In addition there were targets per customer.

Result

The share of recurring revenue rose from 40% (2008) via 80% (2015) to 95% (2025). Average customer lifetime is 8.5 years, the retention rate 88%, measured by number of customers over 16 years. The growth from EUR 0.8m (2009) to EUR 3.3m in revenue (2013) was financed entirely from own funds.

What I would do differently today

I would analyse the cost drivers earlier and clarify which customer groups place which demands on the system and on support. And I would communicate that to customers more clearly from the start.

What I bring

I support software companies on the way from project and licence business to recurring revenue as fractional COO or interim managing director: pricing model, standardisation, onboarding and KPIs – from the perspective of someone who did it with his own money.