The Invisible Gap in Agency Billing

Friday afternoon, just before month-end close. The project lead scrolls through four weeks of time entries. Something feels off — the total seems low, but she can't pinpoint what's missing. So the invoice goes out as-is.

What happens in that moment has a name: revenue leakage. Industry analyses put the share of earned revenue that service firms never invoice at 3 to 7 percent. For an agency doing two million in annual revenue, that's 60,000 to 140,000 — not lost to bad deals, but to friction in the firm's own process.

The insidious part: nobody notices. There's no moment when the money "disappears." It was never there — at least not on the invoice. And because it was never on the invoice, it's absent from no ledger. It's revenue that exists but never becomes visible.

42 Percent of Companies Have a Leak

The problem is neither fraud nor carelessness. It's system friction.

According to MGI Research, 42 percent of all companies experience systematic revenue loss through incomplete or faulty billing. For IT service providers and agencies, the gap is especially stubborn because the deliverable is harder to pin down than a physical product. Nobody forgets to bill for a pallet of screws. But the two hours a developer spent Thursday evening fixing a production bug? Those never make it into any system.

It's not that agencies are sloppy. Quite the opposite: most IT service firms run proper time tracking systems, maintain accurate hourly rates, and use professional invoice templates. What's missing is the bridge between them. Time entries live in Tool A, the project budget in Tool B, the invoice gets created in Tool C. And in the gaps between A, B, and C, revenue seeps away.

The root cause goes deeper than bad processes. It sits in the way agencies think about tracking: as an administrative afterthought. Something you deal with once the real work is done. But that separation — work first, document later — is where nearly every billing error begins. And no spreadsheet, however well-built, can fix it.

What Hospitals Get Right About Billing

In American hospitals, there's a role that doesn't exist in any agency: the Charge Capture Specialist. This person has a single job — making sure every service rendered hits the system before the patient is discharged. Every exam, every treatment, every bandage change.

Sounds like bureaucracy. It's the opposite.

Accounting firm Moss Adams examined five hospitals and found $18.2 million in services delivered but never billed. After implementing systematic charge capture processes, those hospitals recovered $5 to $6 million annually — not from new patients, but from correctly billing the ones they already had.

Scale that down to an agency. Not $18 million, obviously — but the principle is identical. An agency with 30 employees and $3 million in annual revenue that loses 5 percent to billing errors is giving away $150,000 a year. That's one full salary. Or the margin on a mid-sized project.

The real difference between a hospital and an IT agency isn't the industry. It's the assumption. Hospitals assume that unbilled revenue is the default unless you actively prevent it. Agencies assume their tracking is probably fine.

One assumption costs investment in infrastructure. The other costs revenue — every month, with no receipt. And here's the perverse part: the better an agency is doing, the more invisible the problem becomes. Growth masks the gap. It's only when margins start shrinking that anyone notices the growth was never as profitable as it looked. Revenue leakage prevention isn't something most firms consider until the damage is already significant.

Three Cracks Where Revenue Leakage Starts

Billing leakage in agencies is rarely one large hole. It's many small cracks that look harmless on their own.

The first: time tracking in the rearview mirror. When people fill in time entries on Friday evening for the entire week, they're reconstructing — and reconstruction is systematically inaccurate. Daniel Kahneman's research on cognitive bias shows that people consistently underestimate effort spent on past tasks. Not out of dishonesty, but because memory works that way. By Friday, you remember Tuesday's meetings and the big bug fix. But the half-hour code review in between? The twenty-minute client call? Gone. The result: billable hours that never get logged — one of the most expensive time tracking mistakes there is.

The second: scope creep without a price tag. "Can you just quickly..." is the most expensive half-sentence in agency life. Not because the work is bad — but because it stays invisible. When scope shifts but the invoice stays anchored to the original estimate, the agency funds the client's change requests from its own margin. Without noticing, because project budgets and actual effort live in different systems. The project lead sees green lights in the project tool. The controller sees red numbers in the quarterly close. In between: three months of unpriced scope creep.

The third: the invoice that goes out "next week." Deloitte documented 3 to 4 percent billing errors across 20,000 transactions at a financial services firm. The main cause wasn't broken software — it was delay. The more time passes between service delivery and invoicing, the more gets lost in details, context, and attribution. In agencies that invoice at month-end rather than billing in real time, that delay isn't an accident. It's system design. And it has a direct cost: every week of delay between delivery and billing increases the odds of line items being forgotten, misattributed, or quietly dropped — because it's easier than asking.

Real-Time Beats Month-End

The patterns from healthcare and financial services point to the same conclusion: capturing and reconciling services in real time prevents revenue leakage. Checking at month-end finds it at best — and often can't recover it because the context is gone.

In our experience — and in what we hear from other IT service firms — real-time monitoring recovers two to three times more revenue than retrospective audits. The reason is mundane. In real time, you can ask: "Are these three hours for the design review correct?" At month-end, you can only note: "Something's missing." The colleague who'd know is already on the next project. The context is gone. And with the context, the revenue.

For IT service providers, this means an uncomfortable realization: time tracking, project budgets, and billing belong in one continuous process — not in three separate tools stitched together with month-end exports. The split between "tracking hours" and "writing invoices" is itself a billing error. Every system break in between is an invitation to lose revenue.

In practice, that means: when a developer spends three hours on a feature on Tuesday, that information should hit the project budget in the same moment. Not on Friday, when they backfill time entries. Not at month-end, when the controller reconciles the numbers. Right then — because that's the only moment when it's clear whether those three hours are within budget, whether the rate is correct, and whether the work is billable.

Hospitals figured this out years ago. They call it charge capture and treat it as part of the value chain, not as administration. In IT services, there isn't even a term for it yet — maybe because most agencies haven't measured what slips through their fingers every month.

We built Leadtime because we spent years digging through time entries at month-end ourselves. Not because we're smarter — but because we finally wanted to stop searching for our own revenue.