The Margin Leak Map: Where Revenue Disappears Between Quote and Cash

Your firm quoted $120,000. You delivered the work. You invoiced. Six months later, you netted $97,000. The $23,000 that disappeared didn't show up in any single line item on your P&L — it leaked out across four boundaries that nobody was watching.

This is the pattern Cendia sees in nearly every services firm between 30 and 100 people. Revenue enters at the top looking healthy. Profit exits at the bottom looking thin. The space in between — the operational middle — is where the leakage happens, and most firms don’t have a map for it.

The Margin Leak Map is a diagnostic exercise that identifies exactly where margin disappears between a quoted project and a delivered outcome. It has four boundaries, each with its own failure modes, and each measurable in dollars.

The four boundaries where margin leaks

Every services project passes through four boundaries on its way from a signed contract to collected cash. Leakage happens at each, but for different reasons.

A typical 60-person services firm leaks 8-15% of contracted revenue across these four boundaries. Most of it is recoverable through process changes, not pricing changes.

Boundary 1: Quote-to-Kickoff — the leak that starts before work begins

The most common pre-work leak is scope creep that happens between the signed contract and the project kickoff. A $120,000 project becomes a $135,000 project in scope before the first deliverable is started — but the contract still says $120,000.

This happens in three ways:

Verbal additions during onboarding. The client asks “can we also include…” during the kickoff call. The project lead says yes because the relationship is new and saying no feels adversarial. No change order is filed. The additions become part of the understood scope without becoming part of the paid scope.

Contract ambiguity. The SOW says “website redesign” without defining how many pages, how many revision rounds, or what “redesign” includes versus excludes. Six weeks in, the client’s definition of “redesign” turns out to be 40% larger than the team’s.

Onboarding friction. The client takes 3 weeks to provide assets, logins, or brand guidelines that the team needs to start. The project timeline doesn’t shift, but the compressed delivery window increases rework and overtime.

Cendia’s finding across 20+ engagements: Quote-to-Kickoff leakage averages $4,800-$7,200 per project in a firm billing $150-200/hour. On a 40-project annual portfolio, that’s $192,000-$288,000 in margin that was sold but never collected.

Boundary 2: Kickoff-to-Delivery — where most of the dollars disappear

Kickoff-to-Delivery is the largest leak boundary in most services firms because it’s where the handoff count is highest. A typical project passes through 8-14 handoffs between kickoff and final deliverable, and every handoff carries cost.

The three biggest Kickoff-to-Delivery leak sources:

Rework from context loss. A project moves from strategy to design to development. At each boundary, context is re-created from scratch. The designer interprets the strategy deck differently than the strategist intended. The developer interprets the design differently than the designer intended. Each misinterpretation produces a rework cycle that costs 4-12 hours.

Unclear ownership during transitions. A project sits in a queue for 2-3 days between phases because the receiving team wasn’t notified, doesn’t know the priority level, or is waiting for a briefing that nobody scheduled. This doesn’t feel like a leak because nobody is working on it — but the delay compresses downstream timelines and increases overtime later.

Scope discovery during execution. The team starts building and realizes the requirements were incomplete. The missing requirements are real work that needs doing, but they weren’t in the original estimate. The project absorbs them silently because re-scoping feels harder than just doing the work.

The Cost-Per-Workflow framework helps here. Most teams measure direct labor cost only. But coordination cost — the time spent on handoffs, status updates, and re-explaining context — runs 30-50% of total project cost in a services firm. The Kickoff-to-Delivery boundary is where coordination cost concentrates.

Boundary 3: Delivery-to-Invoice — the quiet leak

Delivery-to-Invoice leakage is smaller in percentage terms but insidious because it’s entirely self-inflicted. The work is done. The client is satisfied. The margin loss happens because the firm’s own billing process is slow, incomplete, or both.

Three patterns Cendia sees consistently:

Delayed invoicing. The project completes but the invoice goes out 2-4 weeks later because the project lead hasn’t submitted final hours, or the billing team is waiting for a completion sign-off that nobody sends. Every week of delay increases the probability of a disputed line item by roughly 8%, because client memory of what was agreed to fades.

Underbilled hours. Team members don’t log all their time. This is universal. In Cendia’s experience, services firms with manual time tracking underbill by 6-12% of actual hours worked. At a $175/hour rate and 20,000 annual billable hours, that’s $210,000-$420,000 in work performed but never invoiced.

Line item disputes. The invoice includes items the client doesn’t recognize or doesn’t agree to. Each disputed line item costs 2-4 hours of project manager time to resolve, regardless of whether the firm ultimately collects.

Boundary 4: Invoice-to-Cash — the back-end drain

Invoice-to-Cash is the final boundary and the one most firms understand best because it shows up in accounts receivable aging reports. But understanding it doesn’t mean fixing it.

The average days sales outstanding (DSO) for a 50-75 person services firm is 45-65 days. Every day past 30 carries a financing cost (the firm is paying salaries with cash it hasn’t collected yet) and an increasing probability of partial write-off.

Cendia’s data across 15 client engagements: firms that fix Boundaries 1-3 see their DSO drop by 12-18 days without changing payment terms. The reason is upstream — when the work was scoped cleanly, delivered without disputes, and invoiced promptly, clients pay faster because there’s nothing to contest.

How to build your own Margin Leak Map

You can run a first-pass Margin Leak Map in a single afternoon. The exercise works best with your head of operations and your finance lead in the same room.

Step 1: Pick 5 recent projects. Choose completed projects from the last 6 months — a mix of sizes and clients. Pull the original quote, the final invoice, and the actual hours logged.

Step 2: Calculate the gap. For each project, compare quoted revenue to collected revenue. The difference is your total leak. Most firms find it runs 8-15%.

Step 3: Allocate the gap across the four boundaries. For each project, estimate how much of the gap came from each boundary. You won’t have perfect data. That’s fine — even rough allocations reveal which boundary is your biggest problem.

Step 4: Identify the top 3 leak sources. Across all 5 projects, which specific failure modes appeared most often? Name them concretely: “verbal scope additions during onboarding,” not “scope creep.”

Step 5: Size the annual impact. Multiply the per-project leak by your annual project count. This is your recoverable margin — the revenue you already sold but didn’t collect.

The margin was already sold. The clients already paid for it in the quote. It leaked out through four boundaries that nobody was measuring — and most of it is recoverable through process changes, not pricing changes.

What this isn’t

A few scope notes:

• This isn’t a pricing strategy. The Margin Leak Map assumes your pricing is correct. If your pricing is wrong, fixing operational leakage won’t save you. But most firms in the 30-100 person range are priced reasonably — they’re just not collecting what they quoted.
• This isn’t about working harder. The leakage is caused by structural gaps — missing handoff rules, unclear ownership at transitions, billing processes that require human memory instead of documented triggers. The teams aren’t lazy; the structure is broken.
• This isn’t unique to any industry. Digital agencies, law firms, IT consultancies, accounting firms, architecture firms — the four boundaries are the same. The leak rates vary by industry but the map is universal.

Where to start this week

Two actions, both completable before Friday:

1. Pull 3 recent projects. Compare quoted revenue to collected revenue. Calculate the gap as a percentage. If it’s above 5%, you have a leak worth investigating.

2. Ask your ops lead one question. “Of our last 10 completed projects, how many had scope additions after the contract was signed that we didn’t bill for?” The answer tells you how much of your leak is in Boundary 1.

If the numbers surprise you and you want a structured diagnostic — measured costs, identified root causes, and a 30-day intervention plan — that’s what a Cendia engagement produces. The 30/90/365 Sizing model applies: we scope every recommendation against 30-day, 90-day, and 365-day impact so you know what to expect and when.

This article is part of Cendia’s Hidden Costs series. Companion pieces cover the Handoff Cost Model, Coordination Cost, and the Cost-Per-Workflow framework applied to services firms.