Why silos cause revenue leakage

Silos cause revenue leakage because every department and every system sees only part of the revenue chain, and leaks arise precisely at the handover from one part to the next. Sales sees what was sold, operations what was delivered, finance what was invoiced. Each part can be correct on its own while nobody sees that a deal never became an invoice, or that a price agreement disappeared along the way. A leak between two silos has no owner, and that is why it persists.

What does a silo look like in practice?

A silo is rarely a department that refuses to cooperate. Usually it is a department that works well, with its own system, its own goals and its own figures. The problem is not the department but what it cannot see.

Take an ordinary chain in a B2B company:

1. Sales closes a deal in the CRM. Goal: new revenue. Figure: won deal value.
2. Operations or project management delivers or carries out the work, in the ERP or a planning system. Goal: on time and within budget. Figure: orders delivered, hours realised.
3. Finance invoices and collects, in the accounting system. Goal: correct records, paid on time. Figure: invoiced revenue, outstanding receivables.
4. Account management or support maintains the relationship. Goal: satisfied customers, renewals. Figure: churn, tickets.

Each of those four can have an excellent month while money leaks away. Sales hits its target. Operations delivers everything on time, including extra work that was not in the order. Finance invoices everything it is given, without error. Only the extra work was never passed on. Nobody made a mistake within their own silo.

Where does revenue leak between departments?

Revenue rarely leaks in the middle of a department. It leaks at the seams. These are the five that occur in almost every B2B company.

Seam 1: from sales to delivery

What the salesperson promised does not fully reach the people who have to deliver it. An extra service that is "included", a different price, delivery in phases. If it is not in a field, it does not exist for the next department. The reverse happens too: delivery provides more than was sold, because the customer asked for it and nobody knew it was not included in the price.

Seam 2: from delivery to invoicing

Delivered, but not invoiced. The delivery note does not come back, the hours are not marked as billable, the extra work sits in an email from the project manager. This is the seam with the most direct damage: the work has been done, the costs have been incurred, the revenue does not arrive. The article revenue leakage from manual administration describes how that happens in practice.

Seam 3: from contract to recurring billing

The contract says index annually, the invoice run does not know. The contract says move to the standard rate after twelve months, the discount carries on. The contract renews automatically, billing stops at the original end date. Contracts are signed by sales or management and read by nobody who does the invoicing.

Seam 4: from customer usage to commercial follow-up

A customer uses more than they pay for, or has outgrown their package. Support or operations sees it, account management does not. Or the other way round: a customer quietly buys less, finance sees revenue falling, but account management only hears about it at cancellation. See how to spot customers who are quietly buying less.

Seam 5: between reports

Sales reports won revenue, finance reports invoiced revenue, and management gets two figures that do not reconcile. Because the difference "has always been there", nobody investigates it. Precisely in that difference sit the leaks from the four seams above.

Why does nobody see it?

Three mechanisms keep silo leaks in place.

Everyone measures their own part. Every department is judged on figures from its own system. Nobody is judged on the difference between systems. What nobody measures does not exist as far as management is concerned.

Every figure is plausible on its own. Invoiced revenue is rising, the pipeline is healthy, the projects are running. A leak of a few percent disappears in normal fluctuations. You only see it when you compare at customer or contract level.

The leak has no owner. If sales enters a deal wrongly and finance prepares an invoice wrongly, the error belongs to someone. If an agreement between two departments disappears, the error belongs to nobody. Who is responsible for the handover? In many companies that question has never been answered explicitly. The article who is responsible for revenue leakage? addresses it.

What does not work?

A new system that does everything. The idea that one ERP or one all-in-one package removes the silos sounds logical. In practice, the problem moves. Within one package there are still modules, roles and screens that are not looked at by the same person. And a migration is itself a well-known source of leakage: contracts that were not transferred properly, price agreements that get lost.

A reorganisation. Merging departments changes who sits where, not what falls between the systems.

A weekly meeting between sales and finance. Useful for the relationship. But in a meeting you discuss what people know, and a leak is by definition something nobody knows.

What does work?

You do not close silo leaks by removing the silos, but by making the seams visible.

1. Draw the chain. From lead to paid invoice: which steps, which system, which department. Most companies have never put this on a single page. Do it. The overview in lead-to-cash explained helps as a starting point.
2. Mark every handover. Every place where information passes from one system or department to another. Write down how it happens: automatically, through a form, by email, in a conversation.
3. Give every seam an owner. One person responsible for the question: does everything that goes in on this side arrive on the other side?
4. Compare at the seam. Won deals against orders. Delivered orders against invoices. Contracts against recurring billing. Not on totals, but per customer, contract or order.
5. Measure the difference in euros. A difference expressed in euros gets attention in a management meeting. A difference in numbers of records does not.

The systems stay as they are. What changes is that someone guards the connection. How to set that up structurally is covered in the pillar how do you get a single source of truth for revenue?.

Worked example

Worked example: suppose an installation company with EUR 12 million in revenue carries out 600 projects a year. On some projects, extra work is agreed on site between the engineer and the customer. The extra work is noted on the job sheet, but the job sheet goes to planning, not to invoicing. If on 1 in 10 projects an average of EUR 800 in extra work is not invoiced, that is 60 times EUR 800, so EUR 48,000 a year.

Planning did everything right. Invoicing did everything right. The engineer helped the customer well. The money disappeared at the seam between job sheet and invoice. A comparison of job sheet lines with invoice lines per project finds it. A report per department never will.

Frequently asked questions

Are silos always bad?

No. Specialisation is useful: a finance team should not be managing the pipeline. The problem is not the silo itself but the unguarded handover between silos.

Which seam usually leaks the most?

That differs by business model. In project businesses it is often the seam between delivery and invoicing. In companies with recurring contracts it is often the seam between contract and invoice. In wholesale it is often price agreements between sales and the price list in the ERP.

Does an integration between systems solve the silo problem?

Partly. An integration moves data, but does not check whether everything arrived. Without comparison and an owner, a connected chain can leak just as well as an unconnected one, only faster.

How do I get sales and finance to look at this problem together?

Show the difference in euros, per customer, with names everyone knows. An abstract conversation about data quality wins nobody over. A list of ten customers where together EUR 60,000 a year sits between the systems does.

How do I know whether silos are costing us money?

Ask two questions at your next management meeting. Can someone say within a day which deals won last quarter still have no invoice? And can someone show, per contract, whether the agreed indexation has been applied? If the answer to either is "we would have to look into it", that seam is unguarded. Whether it leaks you only know once you compare, but an unguarded seam is where you start.