How professional services firms close the revenue-margin gap

Diagram of the connected operating model — FP&A for projects: C-Suite, Finance, and Project Management plus Resource Management, Customer Service, and Delivery all feeding one operational picture across the quote-to-cash lifecycle.

Most professional services firms I sit down with already know which lever is leaking. They have a shape of the answer. What they don’t have is the visibility to act on it before the quarter closes and the margin miss has to get explained.

The most recent industry benchmark puts the pattern in plain numbers: 90% of professional services firms hit their revenue target, 17% hit margin (SPI / Rocketlane, 2026). That gap isn’t a sales problem. It’s an operations problem hiding inside the financials.

Across close to a hundred professional services firm implementations over an 11-year span, the same handful of operational truths shows up over and over. Forecasts that don’t quite land. Billing that runs two or three weeks behind delivery. Resources allocated on who’s visible at the moment, not where the work is. A monthly P&L that lives in a spreadsheet three people maintain and nobody fully trusts. Each one is tolerable on its own. Together they’re the difference between the margin a firm is capable of and the margin it actually books.

Most of the revenue-margin gap reduces to four levers. None of them are glamorous. All of them are fixable. Frankly, the firms that close the gap don’t pick one and hammer on it for a year. They work all four together, because the levers depend on each other.

The four levers that actually move performance

Most improvement budgets get spent on things that look like they should move margin: a new tool, a reorg, a pricing exercise, a delivery methodology refresh. Sometimes those help. More often they don’t, because they don’t touch the operational truths that created the gap in the first place.

The four that do:

  1. Forecasting that lands within the quarter you’re in.
  2. Knowing where the bench is, weekly.
  3. Closing the gap between work delivered and cash collected.
  4. Getting paid for what you actually did.

Each is a separate discipline. All four share one underlying requirement: visibility into what’s happening while there’s still time to do something about it.

Forecasting that lands within the quarter you’re in

A forecast isn’t a prediction. It’s the input that shapes hiring, capacity, and investment decisions for the next quarter. When the forecast is wrong, the consequences land three months later as scrambled staffing and deals that didn’t close on the date sales said they would.

The best PS firms forecast within a 5% margin of error. The median firm isn’t close. Around 30% cite inaccurate forecasting as the primary driver of their missed revenue targets.

What I see, almost without exception, is what I’d call the quote-to-scope disconnect: the opportunity is stand-alone, the scoping of the actual engagement is stand-alone, and the gap between them is where the forecast quietly breaks. SOWs get built with numbers that came from history, or from products bolted into the system, or from a quote put together outside the system entirely. None of that reflects the real delivery shape, the resources, the hours, the utilization. The forecast is built on inputs that were never connected to the work that’s about to get done.

It happens in two places at once. Resourcing forecasts (who’s available, who’s over-committed, who’s about to roll off) and cost-and-revenue forecasts (what comes in, what goes out, when). Both of them are downstream of the same disconnect. Fix one without the other and the picture stays half-wrong.

The fix isn’t more rigor on the forecast itself. It’s getting into the system sooner. Before the opportunity closes, while it’s still open in some stage of sales, build the project out, even with generic placeholders and generic numbers. You don’t need it spot-on accurate. You need it visible. From there, finance, resource management, delivery, and project management can all see the shape of what’s coming, and you update as the deal firms up.

The firms that forecast well don’t have better forecasters. They have current data. Pipeline shape, delivery capacity, and project velocity all sit in the same operational picture. When a deal moves in the pipeline, the capacity plan knows. When a project slips, the forecast knows. Nobody reconciles anything at the end of the quarter, because nothing was out of sync in the middle of it.

Knowing where the bench is, weekly

Industry billable utilization fell to 66.4% in 2025, an all-time low (SPI / Rocketlane, 2026). Firms operating at maturity Level 5 run 75 to 80%. The gap between those two numbers is roughly the entire EBITDA margin of a typical PS firm.

Most firms can’t close that gap not because their people aren’t working hard enough, but because leadership can’t see the problem in time to act. Monthly utilization reports tell you what happened last month. By then the bench time has already been paid for.

The questions worth asking weekly, not monthly:

  • Where is the demand coming from next quarter?
  • Which roles are already over-committed?
  • Which consultants are coming off engagements with nothing to move into?
  • Which practice areas are chronically under-utilized?

A healthy overall margin can hide three engagements running at a loss. A solid utilization rate can mask two chronically underused consultants. Before any of that conversation is useful, you have to define what utilization means in your firm. There’s actual utilization (the 40-hour week, all activity logged) and there’s billable utilization (the percentage of that time on billable work). If you’re tracking just one of those, you’re flying half-blind.

What I call the role-anchored utilization read is the way out. The number has to be split billable versus non-billable, and the target has to be set by role.

For junior consultants, healthy billable utilization sits in the 70 to 80% range. The other 20 to 30% isn’t dead time. It’s training, internal meetings, ramp, the things a junior should be doing to get to senior. If your juniors are at 95% billable, they aren’t learning anything that isn’t on the engagement they’re staffed to.

For senior consultants, principals, partners, owners, the number is lower. 50 to 60% billable, max. These are the people shaping the way the business runs and grows. If they’re heads-down on deliverable work at high utilization, the finances look great this quarter and the firm starves long-term. Mentoring junior staff, working pipeline, building the practice, that’s not idle time. That’s the work that keeps the firm in business in three years. It should be logged as a percentage of utilization, even though it isn’t direct billable.

One number doesn’t fit every role. A weekly view, split by billable and non-billable and anchored to role, is what makes it possible to tell which utilization is healthy and which is hiding a problem.

Closing the gap between work delivered and cash collected

Most PS firms accept a 2-3 week lag between month-end and invoice as normal. It isn’t ideal. It also isn’t the whole picture.

The most recently published industry-average DSO is 46.8 days, up from 43.5 the year prior (SPI Research). That’s a full month and a half of revenue parked in WIP and AR — and the trend is moving the wrong way.

The draft response in most operator playbooks is “move to weekly billing.” Honestly, in 11 years of doing this work, I have never seen a firm successfully adopt a same-week billing cadence. The reason isn’t laziness or politics in any narrow sense. It’s structural. Almost every PS firm we work with has a mixed deliverable environment: services alongside software licenses, hardware, subscriptions. Client contracts on the license side were negotiated end-of-month and aren’t getting re-papered. Running multiple billing cycles across the same organization is genuinely overwhelming, and most leadership teams rationally decide the cash-flow trade-off is the lesser problem.

That doesn’t mean the lag is fine. It means the conversation has to shift from “eliminate the gap” to “manage the gap.” The places where firms actually have room to move are the ones inside their control: late time entry, manual billing runs, and approval processes that require someone to compile the data before they can review it. Those are fixable without re-papering a single client contract. Firms that get this right don’t get to same-week. They get from three-week billing cycles to inside-of-two-weeks, consistently. The work is the same. The cash conversion is meaningfully different.

The harder discipline is WIP management during the project, not at month-end. Unbilled work-in-progress that sits for weeks is a margin signal. Scope is drifting, billing rules aren’t being enforced, or the project isn’t structured cleanly. The firms with the cleanest cash conversion treat WIP as a delivery-leadership conversation, not a finance exercise. They catch the issue in week two, not month three.

What I’d call this in practice is the weekly WIP review. The conversation has to converge two groups who usually read the same data in different languages. PMO reads schedule. Finance reads budget. Neither one is connecting either of those to the revenue-billing lifecycle. It’s a tea-leaves problem, and the weekly review is what forces the readings to line up.

The three questions worth running through every week:

  • Can we bill what we’ve delivered?
  • Will we deliver what we’ve committed to bill?
  • Are we going to finish within a margin we sold?

The standing agenda covers revenue recognition risk, budget versus actuals, project health, resource utilization signals, timesheet and approval lag, forecast accuracy, billing readiness. Pull the data with a real dashboard and a real report writer. The point isn’t the meeting; the point is that the data converges before the surprise does.

Getting paid for what you actually did

Revenue leakage is the quietest margin killer in professional services. The industry average is 4.5%, a five-year low but still real (SPI / Rocketlane, 2026). Firms with weak time capture and scope discipline routinely lose 5 to 8% of revenue they should have captured.

Leakage comes from four sources, but in operator practice they aren’t equally weighted. Across the firms I’ve worked with, the order is consistent:

  1. Scope drift. By far the most common. Almost every engagement we examine has at least some of this happening.
  2. Dropped expenses. Occasional. Real, but episodic.
  3. Logged-but-unbilled time. Rare. A clean PSA solution catches this almost automatically.
  4. Informal discounts. Rare. Sales organizations manage this pretty heavily; it’s the one leakage source that has natural friction against it.

Scope drift is the one that hides longest because each individual instance is small. The good news is that the diagnostic is already in your hands if the systems are in place. You compare against the baseline you set when the project started. When margin starts compressing, when timeline starts slipping, when costs start running over plan, that’s the tell.

The recommendation I make to almost every client is snapshot-and-compare against actuals. Take a snapshot of the forecast at a set cadence (weekly, monthly, whatever the project rhythm supports) and compare each subsequent snapshot against actuals as they land. None of the major PSA solutions does this out of the box, which is the part that surprises people. But the granularity it gives you, and the speed at which you can pivot when the snapshot starts diverging from the actuals, is what separates the firms that catch scope drift early from the ones that find it at quarter-close.

A healthy realization rate isn’t about policing. It’s about closing the loop between what was sold, what was delivered, and what was billed, while the memory of each engagement is still fresh.

Why these aren’t four separate projects

The four levers look like four separate projects. They aren’t. All four depend on the same underlying conditions:

  • Data that lives in one operational picture across sales, delivery, and finance.
  • The discipline to act on it weekly, not at quarter-end.
  • Processes that close the loop while the engagement is still fresh.

This shows up in the field as a recurring anti-pattern. Larger firms have DNA etched with the way they’ve always done things. Even when their systems are antiquated, they’ll force the old ways back into the new solution. Smaller firms are more nimble. Industry doesn’t matter much. Size does.

One engagement that comes to mind: a manufacturing firm with field services teams who go out to support deployed equipment as well as deliver new work. Their resource management office was short-staffed, so they wanted to assign groups of resources to activities rather than individuals. We told them, strongly, not to go down that road. They picked it anyway, because it was the easy path. Eighteen months to two years later, they’re starting to come around. The cost of the shortcut wasn’t operational; it was visibility. Without individual resource assignments, there’s no individual utilization data, no view into who’s overloaded, no early signal on the bench. The lever they picked, resource mechanics, broke the lever they didn’t think about, which was visibility into the workforce.

When any of those underlying conditions is missing, margin slips through the cracks. When all three are in place, the levers reinforce each other. Forecast accuracy improves because capacity is visible. Billing accelerates because the process runs at frequency, not against a deadline. Realization tightens because every handoff is on the same record.

The pattern across the firms I’ve worked with: the ones that exceed in this aren’t running more efficient projects. They’re running more connected ones.

What I’d call this, on first use, is the connected operating model. It’s the easiest way to say what it actually is: FP&A for projects. All the moving pieces necessary to deliver the quote-to-cash scenario end to end, connected and visible across the C-suite, finance, project management, resource management, customer service, and delivery. Not a process. Not a tool. The operating model that ties the four levers into a single discipline.

Patching one lever at a time (a new billing system this year, a capacity tool next year, a forecast overhaul the year after) leaves a firm stuck. Each project delivers on its own. The underlying picture stays fragmented. The firms that close the gap treat the four as a single discipline, with visibility being the primary goal.

What it looks like when the model is in place

A firm I worked with, healthcare consulting in the Northeast, serving hospitals and nursing organizations, was running entirely on spreadsheets. They were tracking time. They were producing statements of work. None of it was connected.

When we built out a few of their existing projects inside a real PSA solution and dropped in their actual time, revenue, and cost data, the margins came back negative in the hundreds of percent. One project at -2,000%. We thought we’d been handed bad data. We re-checked. The data was right. Their finance lead had had a feeling, in the way operators always have a feeling, that the margins were worse than what was reported, but nobody had been able to see it in numbers until that moment. The firm wasn’t going under; they were making money elsewhere. They just had no idea how much they were losing on the work they thought was profitable.

The after wasn’t a process change. It was a visibility change. Proposal through invoice, end-to-end, in real time. They could write more accurate SOWs because they could see what the last ten engagements actually cost. They could see margin compression in week three, not at quarter-close. They could see utilization sliding the same week it slid. Sales had visibility. The PMO had visibility. The CFO had visibility. It changed the way they ran the business. Not because they were working harder, but because the surprise had been engineered out of the operating rhythm.

Where this is going

Two shifts are happening at the same time, and both of them are going to reshape the operating model again over the next few years.

The first is the move from time-and-materials to outcome-based delivery. Firms that price and bill against outcomes, rather than hours, are reshaping how revenue gets recognized, how engagements get scoped, how clients are managed. It’s a different deal entirely, and the firms that don’t adopt it will have a hard time. The ones with a clean PSA foundation and the discipline to run the numbers will find the transition manageable. The ones still running on spreadsheets and goodwill will find it brutal.

The second is AI. I want to be careful here, because there’s a particular flavor of marketing right now that treats AI as the answer to all of this. It isn’t. If you don’t have a foundational system today and your plan is to build a custom AI to handle PS operations from scratch, you are signing up for something that is hard to scale, hard to maintain, and expensive to run. AI is a tool that gets inserted into specific delivery areas, where it does a particular job well. It’s a game-changer in those places. It is not a replacement for the operating model.

Where AI does earn its keep is exactly the place the four levers point: full-picture visibility under a single pane of glass. Scoping, delivery, customer success, outcomes, the whole picture of an engagement, including what I’d call the CV for the project: the resume of what got delivered, against what was sold, with what margin, by whom. That’s the kind of layered insight a connected operating model makes possible and a custom AI built without that foundation can’t deliver.

A rhythm, not a project

Closing the revenue-margin gap isn’t something a PS firm does once. It’s a rhythm: weekly forecasts, role-anchored utilization reads, snapshot-and-compare against actuals, and a clean close on every engagement. The firms that build the rhythm don’t experience it as extra work. They experience it as the absence of the surprise margin meetings that used to happen every quarter.

Frequently asked questions

What is the difference between revenue target and margin target performance in professional services?

Most PS firms hit their revenue target (around 90% do, per SPI / Rocketlane 2026). Far fewer hit their margin target (around 17%). The gap is operational, not commercial. Revenue is what sales books; margin is what delivery, billing, and realization actually preserve. The four levers (forecasting accuracy, weekly bench visibility, work-to-cash conversion, and revenue leakage) are where the margin gets lost between booking and collection.

How do I read utilization correctly across roles?

First, define utilization in two parts: actual utilization (all 40 hours accounted for) and billable utilization (the percentage of that time on billable work). Then anchor the target to role. Junior consultants run healthy at 70 to 80% billable, with the remainder going to training and ramp. Senior consultants, principals, partners, and owners run at 50 to 60% billable, max. The rest is mentoring, pipeline, and the work of running the firm. A single firm-wide utilization number hides more than it shows.

Why is same-week billing so hard to actually adopt?

In eleven years of professional services implementation work, I haven’t seen a firm successfully move to same-week billing. The reasons are structural rather than political. Most firms operate in mixed deliverable environments where services run alongside software licenses or subscriptions, and license contracts are typically negotiated on end-of-month terms. Running multiple billing cycles inside one organization is operationally overwhelming. The realistic goal isn’t elimination of the gap. It’s compression: moving from three-week billing cycles to inside-of-two-weeks, consistently.

Is AI going to replace professional services automation?

No. Custom AI built on top of nothing, as a substitute for foundational PSA systems, is hard to scale, hard to maintain, and expensive to run. AI is a tool that gets inserted into specific areas of delivery where it does a particular job well. It’s not a replacement for the operating model. It’s a layer on top of one that already works. Firms looking to add AI capability are best served by getting the connected operating model in place first.


About The Author