What is Revenue Intelligence? The complete guide for B2B

Revenue Intelligence is the continuous connecting and checking of all the data that describes your revenue: deals in the CRM, terms in contracts, lines on invoices and payments in the accounts. The aim is not a better-looking dashboard but an answer to one question: is the revenue you sold also the revenue you invoice and receive? Where the two drift apart, there is revenue leakage, and Revenue Intelligence makes that gap visible in euros, with an owner and a next step.

That sounds obvious. Yet in most B2B companies nobody can answer the question in one go. Sales looks in the CRM, finance in Exact, Xero or NetSuite, operations in a planning tool and the board in a spreadsheet that someone rebuilds every month. Each system is correct on its own terms. The gap sits between them.

This guide covers the whole subject: what Revenue Intelligence is and is not, how it works technically, which data and systems you need, why it is becoming more important and how to judge whether it will pay off for your business.

Revenue Intelligence explained for business owners

Picture the route a euro of revenue travels. A salesperson marks a deal as won in HubSpot. A contract is signed with an annual price, an indexation clause and a volume tier for additional licences. Someone sets the customer up in billing. Every month an invoice goes out. The customer pays, or does not pay in full, or pays late. Halfway through the year additional work is agreed by email.

Something can get lost at each of those handovers. The deal is never invoiced because nobody set the customer up in billing. The indexation is forgotten. The additional work lives in an email and nowhere else. The volume tier is not applied because the extra licences were delivered but never passed on.

Revenue Intelligence is the discipline, and the software, that follows this route from start to finish. It puts the systems side by side, compares what should have happened with what did happen and reports the difference. For a business owner it comes down to three questions:

1. Am I invoicing everything I sold? At the right price, at the right time, with the right increases.
2. Am I receiving everything I invoiced? And can I see in time which customers are about to buy less or leave?
3. Is the picture I base my decisions on correct? Is the forecast built on data that matches reality?

The difference from ordinary reporting is that Revenue Intelligence does not stop at a number. A report says revenue this month is 3 percent below budget. Revenue Intelligence says four customers are still being invoiced at last year's rate, what that costs per year and who needs to fix it.

What is Revenue Intelligence software?

The term is used in the market for different things, which makes it confusing. Broadly, you will find three kinds of software under this name:

• Conversation and deal analysis. Tools such as Gong started by analysing sales calls, tools such as Clari with pipeline and forecasting. They mainly answer which deals will close and how salespeople are performing. That is valuable for large sales teams, but it barely looks at what happens after the signature.
• Forecasting and pipeline tools. These focus on prediction: how much revenue will come in this quarter. They use CRM data and sometimes historical revenue.
• Revenue monitoring across the whole chain. Software that connects CRM, contracts, billing and accounting and checks whether they agree with each other. The emphasis here is on revenue leakage: money you have already earned but do not receive.

What a Revenue Intelligence platform must be able to do is set out in what a Revenue Intelligence platform does. In short: it reads your systems, connects records that belong together, compares them against rules and expectations, and turns deviations into tasks with a euro amount attached.

Some vendors go a step further and call their product an operating system for revenue. What that means, and how it differs from a standalone tool, is explained in what a Revenue Intelligence OS is.

What it is not

Revenue Intelligence is not a CRM. It does not replace your CRM and it is not where salespeople keep track of their deals. It reads the CRM.

Nor is it accounting. The general ledger stays in Exact, AFAS, Xero, NetSuite or SAP. Revenue Intelligence checks whether what is recorded there matches what was sold and agreed.

And it is not a BI tool such as Power BI. A BI tool shows you whatever you build yourself. You have to know which question to ask, which tables to join and which outcome is suspicious. Revenue Intelligence comes with those questions built in: it knows that a won deal without an invoice is a problem, and that a contract with an indexation clause should produce a higher invoice in January.

How does Revenue Intelligence work?

Under the bonnet, every serious Revenue Intelligence solution does roughly the same thing, in four layers. The full version is in how Revenue Intelligence works, from CRM to invoice.

1. Read

The software pulls data from the systems you already use. Usually through an API connection with read access: deals and products from Salesforce or Pipedrive, invoices and receivables from Exact, Xero or Dynamics, subscriptions from a billing tool, contracts from a document system. This happens continuously, not once. A check that runs once a year only finds a leak after it has been running for twelve months.

2. Connect

This is the hardest layer, and the point where most spreadsheet attempts fail. A customer is called "Baker Installation Services Ltd" in the CRM, "Baker Install. Ltd" in the accounts and "Baker Holdings" in the contract. The deal has three product lines; the invoice has five because finance splits them differently. To compare anything, the software has to know which records belong together: which customer, which deal, which contract, which invoice lines.

That connecting is done on keys such as the company registration number, customer account number, order number or contract number, and where those are missing on names, amounts and dates. The better your own data, the less guesswork is needed.

3. Compare

Once the records are connected, you can apply rules. A few examples:

• Every deal marked as won has a first invoice within thirty days.
• A contract with an indexation clause shows a higher rate on the invoice after the indexation date.
• The number of licences invoiced equals the number of licences delivered.
• The invoiced price does not deviate from the price list by more than the agreed discount.
• A customer who ordered every month and then orders nothing for two months is a signal.

Alongside fixed rules you can look for patterns: deviations from the same customer's past behaviour, or from similar customers. This is where AI comes in, but the foundation is rules you could explain yourself.

4. Act

A deviation is only worth something if someone acts on it. Good Revenue Intelligence turns every finding into something concrete: this is the difference, this is how certain we are, this is what it costs per year, this person resolves it. Sometimes the fix can be automated, for example a draft invoice for the missing additional work or a task in the CRM. Sometimes a person has to decide, for example whether you still charge a customer the indexation.

What data do you need?

Revenue Intelligence works with the data you already have. Nothing new has to be collected, but some things do have to be brought together. The main sources:

Not every company has all of these sources, and you do not need them all to start. A project business mainly has hours, additional work and milestone invoices. A SaaS company mainly has subscriptions and usage. A wholesaler has orders, price agreements and rebates. What data Revenue Intelligence uses sets out, source by source, which fields really matter and what you need at a minimum.

One point deserves attention now: contracts. In many companies the most important terms on price, indexation and volume tiers exist only in a PDF. No system knows about them. That is exactly where leaks arise that keep running for years.

Which systems do you connect?

The minimum connection for meaningful Revenue Intelligence is the CRM plus billing. With those two you can already find the most common and often the largest leaks: won deals without an invoice, price differences between deal and invoice, and customers who exist in one system but not in the other.

After that you add whatever is relevant to your business model: the accounting system for payments, an ERP for orders and delivery, time tracking for project businesses, a billing tool for subscriptions. Which combination suits which type of company, and how to set it up securely, is covered in which systems to connect for Revenue Intelligence.

Two principles always apply:

• Read access wherever possible. Revenue Intelligence does not need to change your systems to find leaks. Writing back, for example a task in the CRM or a draft invoice, should only happen after explicit approval.
• Your own systems remain the source. The accounting system remains the source for what was invoiced. The CRM remains the source for what was sold. Revenue Intelligence is the layer that compares them, not a new place where the truth lives.

Where Revenue Intelligence finds leaks

The value of Revenue Intelligence is clearest from the leaks it finds. Most are not spectacular. Nobody committed fraud and no system is broken. They are handovers that did not quite work.

Won but not invoiced. The deal is marked as won in the CRM, but the customer was never set up in billing, or the first invoice was never sent. This is the classic leak between sales and finance.

Forgotten indexation. The contract says the price rises every 1 January in line with a published price index. Nobody put that into billing. In the first year you miss a few percent, in the second year it compounds, and after three years you are structurally undercharging a customer.

Prices that are wrong. A salesperson gave a 15 percent discount for the first year. The discount was set up in billing as a permanent discount, so it simply carries on. Or a customer gets a price from an old price list because the item was once created by hand.

Additional work that is recorded nowhere. In projects, additional work is agreed on site or by email. If it never comes back as an order or as hours, it is never invoiced.

Licences and quantities. A customer has grown from 40 to 55 users. The contract says you invoice per user. Billing is still set to 40.

Quietly drifting away. A customer orders a little less each month without cancelling. Nobody notices, because there is no moment when anyone looks.

These are not rare exceptions. They are the standard patterns that occur, to varying degrees, in almost every B2B company running several systems.

Worked example: what is at stake?

A commonly cited estimate is that revenue leakage in B2B lies between 1 and 5 percent of revenue. That is a range, not a research finding that applies to your company. The real figure depends on how much manual work sits between your systems, how complex your pricing agreements are and how long leaks can go unnoticed.

Worked example: suppose your company has revenue of EUR 8 million. You have 300 contract customers with an indexation clause, averaging EUR 12,000 a year. For 40 of those customers, last year's 3 percent indexation was not applied.

• Missed revenue per customer per year: EUR 12,000 x 3% = EUR 360.
• For 40 customers: EUR 14,400 per year.
• If it is left for two years and a second indexation is added on top, the shortfall per customer grows and in the second year you are already missing more than double.

Add five won deals without a first invoice at an average of EUR 8,000, and a handful of customers with more users than they pay for, and you quickly reach tens of thousands of euros a year. That is not a dramatic percentage of EUR 8 million. But it is money you have already earned, with no additional cost against it, and it comes back every year until someone notices.

Why Revenue Intelligence is becoming more important

Revenue Intelligence is not a new idea. Controllers have sampled invoices for decades. What is changing is that doing it by hand works less and less well. The full argument is in why Revenue Intelligence matters more and more for B2B; in brief:

• More systems. A EUR 5 million company now runs on a CRM, an accounting package, a planning tool, a support tool, an e-signature platform and a handful of spreadsheets. Every extra handover is another place for a leak.
• More complex pricing models. Subscriptions, volume tiers, usage-based prices, bundles, indexation. The more variables in a price, the greater the chance that one of them is not applied correctly.
• Recurring revenue. With a one-off sale, an error happens once. With a subscription or framework agreement, an error repeats every month until someone finds it.
• Pressure on margins. When costs rise, money you have already earned is the cheapest money there is. Recovering a leak costs no marketing and no sales effort.
• Better technology. API connections have become standard, and AI makes it feasible to connect messy data and read contracts at a scale that used to be reserved for large enterprises.

The role of AI

AI is often presented as the core of Revenue Intelligence. In practice it is an amplifier, not a foundation. The foundation is that your systems are connected and that records are reliably matched. Without that, AI has nothing to work with.

Where AI genuinely helps:

• Reading contracts. A language model can extract from a PDF the term, the indexation that applies and the volume tiers. That makes contracts checkable that previously sat only in a folder.
• Matching records. Recognising that "Baker Install. Ltd" and "Baker Installation Services Ltd" are the same customer works better with AI than with exact rules.
• Finding anomalies. Recognising patterns that no fixed rule captures, such as a customer who orders differently from comparable customers.
• Explaining. Turning a finding into a readable explanation with the evidence attached.

What AI should not be used for is deciding without a person looking on. A model that sends credit notes or charges customers indexation on its own is a risk out of proportion to the time saved. The right set-up is: AI proposes, shows the evidence, a person approves.

Who is Revenue Intelligence for?

Not every company needs it. A company with twenty customers, one product and an owner who sees every invoice personally gets little out of it. The value grows with three things:

1. Number of customers and invoice lines. From a few hundred customers or a few thousand invoice lines a year, manual checking is no longer a realistic option.
2. Complexity of agreements. Custom prices, indexation, volume tiers, additional work, usage-based billing.
3. Number of systems and handovers. Every time information has to pass from one system or department to another, something can be left behind.

Companies from roughly EUR 2 million in revenue with recurring revenue, projects with additional work or contracts with pricing agreements usually get the most out of it. Think of managed service providers, SaaS companies, installation companies, consultancies, wholesalers with framework agreements and business services.

How do you get started?

You do not have to start with software. The most important thing is knowing where you leak and how much. A practical order:

1. Map the chain. Draw for yourself the route from deal to payment. Which systems, which handovers, who does what. Mark every point where something is retyped by hand.
2. Do one comparison by hand. Export all won deals from the past year from the CRM and all invoices from the accounting system. Find the first invoice for each deal. Every deal without an invoice is a finding.
3. Take out the contracts with indexation. List every customer with an indexation clause and check whether the rate on the latest invoice is higher than a year earlier.
4. Add it up. Put an annual amount against each finding. Only then do you know whether you are talking about hundreds, thousands or tens of thousands of euros.
5. Decide whether it needs to be structural. If a one-off check turns up a lot, those same leaks will open again tomorrow. Then continuous monitoring is the logical step.

If you would rather not do this yourself, you can have a one-off revenue audit carried out, independent of any software. If you want the checks to run continuously, you look at a platform. What AutoMaat's platform looks like is shown on the system page. They are two different choices, and neither is a precondition for the other.

Checklist: do you need Revenue Intelligence?

Answer these questions honestly. The more often the answer is no, the greater the chance that revenue is leaking away without anyone seeing it.

• Can you produce, within an hour, a list of all deals won last quarter with the matching first invoice?
• Do you know, for every customer with an indexation clause, whether the latest indexation was applied?
• Do the revenue figures from sales and finance match in the same meeting?
• Is additional work always recorded as an order or as hours before it is carried out?
• Would you see within a month that a regular customer is starting to buy less?
• Is someone responsible for making sure CRM and billing agree?
• Are discounts with an end date actually ended?

Frequently asked questions

What is the difference between Revenue Intelligence and Business Intelligence?

Business Intelligence is a set of tools for analysing and visualising data. You define the question and build the report yourself. Revenue Intelligence is aimed at one question: is your revenue correct from sale to payment? It comes with the checks built in and ends in an action rather than a chart.

Do I need Revenue Intelligence if I already have a good CRM?

A CRM knows what was sold, not what was invoiced and paid. Most leaks arise precisely after the moment the deal is marked as won in the CRM. A good CRM is a precondition for Revenue Intelligence, not a substitute for it.

How much revenue leaks away on average?

A commonly cited estimate is 1 to 5 percent of revenue. There is no reliable average for your sector or size. The real figure depends on how much manual work, how many systems and how much price variation your company has. The only way to know is to measure it.

Do I have to connect all my systems to start?

No. CRM plus billing is enough to find the first and often the largest leaks. You add other sources when they are relevant to your business model.

Does Revenue Intelligence replace my controller?

No. It takes over the searching that a controller can never do completely: comparing every deal, every invoice, every month. The controller decides what happens with a finding and makes sure the agreements are right.