What does Revenue Intelligence deliver?

Revenue Intelligence delivers three main things: revenue you already earned but did not invoice, leaks you prevent before they compound, and figures you can steer on because CRM, billing and the accounts finally say the same thing. The largest and most measurable return is the first: revenue leakage found and stopped, commonly estimated at 1 to 5 percent of revenue. Whether it pays off for your business depends on how much is leaking, what the solution costs and how much of the amount found you actually recover.

Why is this question harder than it looks?

With most software, the return is a saving: fewer hours, fewer licences, fewer errors. You can estimate those reasonably well in advance. With Revenue Intelligence, the largest return is something you do not know in advance: how much revenue is currently disappearing unnoticed. If you knew, you would already have fixed it.

That means every business case contains an unknown. Vendors like to fill it in with an attractive percentage. That is exactly where you need to be careful. An honest calculation starts with a range, not a point estimate, and only becomes precise once you have looked at your own data.

This article goes through the returns one by one, sets the costs against them and shows how to weigh them up. Where a subject has its own in-depth article, the link is included.

Return 1: revenue found

The most direct return is revenue you should already have invoiced. Think of:

• Won deals in the CRM that never led to an invoice.
• Extra work on projects that was carried out but not invoiced.
• Contracts with an indexation clause that was not applied.
• Customers using more licences, seats or volume than they pay for.
• Discounts that stayed in place after the agreed period.
• Unpaid invoices at customers who keep receiving deliveries as normal.

What each of these items is worth depends entirely on your business. The commonly cited estimate for revenue leakage is 1 to 5 percent of revenue, with smaller companies tending towards the higher end. Treat that as an order of magnitude, not a promise. What it means concretely in euros, and why the amount is usually larger than the first number you find, is worked out in what does revenue leakage cost.

Two caveats missing from many business cases:

Not everything you find, you recover. A discount that has run for three years you will probably not claw back retrospectively. Extra work from eighteen months ago is commercially difficult to invoice now. The ongoing part you do stop. So in your business case, count the part you will invoice from now on, and treat recovery of the past as a bonus.

Revenue found is one-off, leakage stopped is recurring. A forgotten invoice you send after all pays off once. A subscription you correct pays off every year. The second is worth far more to your valuation and your margin.

Return 2: leakage prevented

The first round finds the old leaks. The value of continuous monitoring lies in the leaks that no longer arise afterwards, or that are found within days instead of after a year.

That difference is bigger than it looks. An error in a recurring contract that you find after a month costs you one month. The same error found at year-end close costs you twelve months. At a company that processes new contracts, changes and price adjustments every year, new discrepancies arise all the time. The question is not whether they arise, but how long they remain.

This is also the return that is hardest to prove, because you are measuring something that did not happen. A practical approach: track how many discrepancies are found each month and how old they are on average when they are found. If that average falls from months to days, you are seeing the return.

Return 3: a forecast you can steer on

A forecast from the CRM describes what sales expects. A forecast that also takes billing, contracts and usage into account describes what is likely to come in. At many companies the gap between the two is big enough to base the wrong decisions on: hiring someone you cannot pay, or postponing an investment you could have made.

The return on a better forecast is hard to express in euros. It is not revenue you recover, but a decision you make better. So be careful about including it in a business case. Mention it as a benefit, do not count on it.

Return 4: time

At many companies a structural amount of time goes into reconciling figures by hand every month. Finance exports from the CRM, sales exports from billing, someone builds an overview in Excel, and at the monthly meeting it turns out the figures do not match. Then the investigating starts.

That time is measurable. Ask the people doing it how many hours a month they spend on:

• Reconciling CRM and billing.
• Working out why figures in reports differ.
• Checking invoices against contracts or orders by hand.
• Preparing the monthly report.

Convert those hours into costs. It is not a large item next to the revenue found, but it is the one you know for certain.

Return 5: retention and expansion

Revenue Intelligence that puts usage, support and payment behaviour side by side spots customers who are drifting away earlier than an account manager who calls only a few times a year. And it spots customers who use more than they pay for, which is an expansion opportunity.

Here too: be careful with the numbers. Seeing a signal does not mean you keep the customer. It means you get the chance. What that chance is worth depends on what your team does with it.

What does it cost?

Against the returns there are costs, and they involve more than the licence.

What a platform costs in practice, and where price differences between vendors come from, is covered in what does a Revenue Intelligence platform cost. The rule of thumb: the licence is rarely the largest item in the first year. Internal time often is.

How do you weigh it up?

The business case has a simple shape. Return in year one, adjusted for what you realistically recover, minus total costs in year one. Then the same for years two and three, in which the implementation costs fall away and the stopped leakage continues to pay off.

How to calculate that step by step, including the payback period, is explained in how do you calculate the ROI of Revenue Intelligence.

Worked example: a company with EUR 8M revenue

Suppose your company has EUR 8M in revenue. This is an example to show the calculation, not a prediction for your business.

• Leakage at a cautious 1.5 percent: EUR 120,000 a year.
• Of that, you realistically recover 60 percent in year one, because part of the past can no longer be invoiced and some fixes take time: EUR 72,000.
• Time saved: 16 hours a month of reconciliation, at EUR 60 an hour: EUR 11,520 a year.
• Return in year one: around EUR 83,500.

Set your total year-one costs against that: software, implementation and internal time. If they stay well below the return, the case is positive. In year two the implementation costs fall away, while the stopped leakage continues.

Do the same calculation with 0.5 percent leakage. If the case still holds, it is a robust decision. If it only holds at 4 percent, you know you first need to establish how much is really leaking.

How much leakage is enough?

There is a floor below which software does not pay for itself. That floor depends on your revenue, your complexity and what the solution costs. A company with EUR 3M in revenue and a simple billing model has a different threshold from a company with EUR 25M in revenue, four systems and hundreds of recurring contracts. How to set that threshold for your own situation is covered in how much revenue leakage justifies software.

The reverse also applies. A company with many manual handovers between systems almost always leaks more than a company where everything happens in one package. Complexity is a better predictor than revenue alone.

When is it worth it?

Revenue Intelligence delivers most at companies where revenue passes through several systems before it reaches the bank. The signs that you are in that position are set out in when does a business need Revenue Intelligence. In short:

• Sales and finance quote different revenue figures in the same meeting.
• You have recurring contracts with indexation, tiered pricing or usage-based prices.
• There are manual steps between deal, order and invoice.
• Nobody can say within a day which won deals have not yet been invoiced.

A question that often follows: is this also something for a smaller company? The answer is yes, but the form differs. Where it does and does not work for SMEs is covered in can an SME use Revenue Intelligence.

"We already have a CRM" and "we already have Power BI"

The two most common objections concern overlap with what is already there.

A CRM is built to manage sales. It knows what was sold, not what was invoiced or paid. It does not check itself against billing. Why that difference matters is covered in do I need Revenue Intelligence if I already have a CRM.

Power BI, or another BI package, can show data from several systems. But it shows what you build into it. It does not look for discrepancies by itself, it does not price them and it does not assign them to an owner. Whether your existing dashboards are already enough is covered in do I need Revenue Intelligence if I already have Power BI.

In both cases: the existing systems stay. Revenue Intelligence sits on top of them, it does not replace them.

Who picks it up?

A finding only delivers something if someone acts on it. That sounds obvious, but it is the most common reason revenue leakage analyses end up in a drawer. Sales sees it as a finance problem, finance sees it as a sales problem, and operations has no time.

Who is responsible depends on where the leak is. A deal without an invoice sits at the handover from sales to finance. A missed indexation sits with whoever manages the contracts. How to divide that responsibility is covered in who is responsible for revenue leakage. Without that agreement, every investment in detection is money thrown away.

One-off review or continuous monitoring?

There are two ways to get to the return, and they are not interchangeable.

A one-off review, a revenue audit, maps where revenue is leaking right now and what it costs. It produces a list of findings and an order in which to tackle them. It suits you if you first want to know whether enough is leaking to invest further, or if you want to fix it yourself afterwards. When that is the right choice is covered in when does a revenue audit make sense.

Continuous monitoring connects the systems and compares them all the time. It finds new leaks as soon as they arise, instead of once a year. It suits you if your business has enough moving parts to produce new discrepancies every month.

At AutoMaat these are also two separate products: the Revenue Audit, a one-off review carried out personally across eight areas in which every finding is given an amount in euros, and RiOS, a platform in beta that connects to existing systems and monitors revenue leakage continuously. You can take one without the other.

Can you fully automate it?

Partly. Comparing systems, finding discrepancies and pricing them can largely be automated. Deciding what to do about a discrepancy cannot always. Calling a customer about a missed indexation, reversing a discount at a strategic account, sending an invoice retrospectively: those are commercial choices a person should make. Where the line lies between what you can and cannot automate is covered in can revenue leakage be fully automated.

What does it not deliver?

An honest business case also names what you should not expect.

It does not make bad data good by itself. If customers appear three times in the CRM under slightly different names, or if contracts are not held digitally anywhere, Revenue Intelligence will show you that. It will not fix it for you. The first months often go partly into clean-up, and someone has to do that work.

It does not replace commercial choices. Whether you correct a customer with a price that is too low, and how, remains a trade-off between revenue and relationship. Software can supply the amount and the evidence. The decision is yours.

It does not bring in new customers. Revenue Intelligence is about the revenue you already have or should already have had. It can surface expansion opportunities at existing customers, but it is not a means of opening new markets. Anyone who expects that is comparing it with the wrong investment.

It does not work without access. A platform that only sees the CRM cannot say anything about billing. The return scales with the number of systems you connect and the quality of the key that links them, usually a customer or contract number that is the same in every system.

If you know this in advance, you set expectations correctly and judge the return after six months by the right measure.

A checklist for your own business case

1. Estimate your leakage as a range. Calculate with a low and a high estimate, not with a single number.
2. Split one-off from recurring. What do you recover once, and what do you stop for the future?
3. Count what you realistically recover. Not what you find.
4. Include all costs. Software, implementation, data clean-up and the internal time to follow up signals.
5. Appoint an owner in advance. Who picks up the findings, and does that person have the time?
6. Run the numbers at the low estimate too. If the case still holds, it is a robust decision.
7. Measure after six months. How many discrepancies found, how many resolved, what amount recovered? Compare with the business case.

Frequently asked questions

How quickly does Revenue Intelligence deliver results?

The first findings usually come from the first comparison of systems, so within weeks of connecting them. Whether those findings turn into revenue depends on how quickly your team acts on them. The ongoing return, leaks that no longer compound, builds up over months.

Is 1 to 5 percent leakage a reliable figure?

It is a commonly cited estimate, not a measured average that applies to every company. It indicates the order of magnitude. For a decision you need your own number, and you only find that in your own data.

What if almost nothing leaks at our company?

Then that is a good outcome, and you know your processes work. For a company with little leakage and little complexity, continuous software is then probably unnecessary. A periodic check may be enough.

Does it only deliver something for finance?

No. Sales gets a forecast that matches what actually comes in, customer success sees earlier which customers are drifting away, and the leadership team gets one figure instead of three. But the most measurable return does sit with finance: revenue that is invoiced instead of forgotten.

What is the biggest risk of the investment?

That nobody picks up the findings. A system that reports twenty discrepancies a week that stay on a list delivers nothing. Settle ownership before you choose the software.