Your team is 90% utilised. Timesheets are full. Projects are closing. So why does the margin keep coming in short?
Because utilisation is the wrong number to watch.
High utilisation only proves your team is busy. It doesn’t prove they’re making you money. The hours your team logs and the hours that reach an invoice are two different figures. The gap between them is where project profitability bleeds out.
| According to the SPI Research 2024 Professional Services Maturity Benchmark, average billable utilisation across professional services firms fell to 69.3% in 2023, sitting well below the 75% optimal threshold. That figure counts hours logged on billable work. It says nothing about how many of those hours actually reached an invoice. That second number is lower. Significantly lower. For a 10-person team billing at $150/hour, every percentage point below the 75% threshold costs roughly $15,000 in annual revenue. Most teams have no idea which side of that line they are on. |
Stop blaming your pricing model. You have a blind spot. Fixing it starts with understanding exactly where the leak is and why the tools most teams rely on are structurally incapable of catching it in time.
The Metric Confusion Costing You More Than You Think
Utilisation and realization sound like the same thing. They’re not, and conflating them is one of the most expensive habits a project business can develop.
Utilisation: the percentage of a team member’s time spent on billable work. An 87% utilisation rate looks healthy on paper.
Realization: the percentage of billable hours that actually reach an invoice and get paid. If 10% of those billable hours get absorbed by out-of-scope revisions, written off to keep a client relationship intact, or logged against the wrong code, your realization rate drops to 77%. No one registers it until the reconciliation.
Most teams obsess over utilisation because it’s easy to pull from a time-tracking tool. Realization requires connecting three separate data points: scope agreed, hours logged, and amounts invoiced. Most teams don’t have that connection built into their day-to-day workflow.
The industry benchmark for realization in professional services sits between 85% and 95%. Below 80% on a consistent basis, the problem isn’t a lazy team or difficult clients. Your operational systems are letting revenue walk out the door before you’ve had a chance to bill it.
Four Places Your Margin Is Leaking Right Now
Scope creep gets blamed for everything. The biggest margin leaks are internal, and they’re happening on projects that look completely under control.
Unbilled revisions: The client requests a change. The team absorbs it because the relationship matters. No change order is raised because it feels like a small ask. Across eight projects a month, that pattern produces a material write-off with no paper trail.
Senior staff doing junior work: A senior consultant drafts an update an analyst could write. In the moment, it feels efficient. At billing, it destroys your margin. You’re burning senior-rate costs against mid-level outputs, and your margin model was never built for that.
Scope agreed in the wrong place: Projects with ambiguous deliverables generate more revision cycles, more internal debate, and more write-downs than projects with tight scope. The damage doesn’t show up at kickoff. It surfaces six weeks in when three stakeholders have three different definitions of done.
Write-downs that nobody tracks: Most billing teams carry an informal habit of sneaking reductions into an invoice when a project runs long. It keeps the client relationship intact. Write-downs that aren’t tracked systematically become invisible losses that compound month over month. They never get fixed because nobody can see them.
| Spreadsheets are autopsy tools. By the time a monthly finance report lands, the projects are closed, the team has moved on, and the loss is permanent. Any business still relying on end-of-month reconciliation to manage profitability isn’t managing it. It’s documenting failure after the fact. |
Why Your Current Tools Are Built for the Wrong Moment
The tools most project teams use, time trackers, billing spreadsheets, monthly finance reports, share one design flaw: they record what happened, not what’s happening.
A time tracker tells you hours were logged. It doesn’t tell you whether those hours are billable, whether they’re within scope, or whether the project is tracking toward a profitable close. A monthly finance report arrives three weeks after the month ends, reporting on projects already closed and margins you can no longer recover.
By the time a spreadsheet shows you a problem, you have two options: absorb the loss, or have an uncomfortable client conversation. Neither is a good operational outcome.
Teams running consistent margins aren’t better at post-mortems. They’ve moved visibility from after closeout to during delivery. At any point in an active project, they know whether budget burn is tracking against the original forecast and they act on that information while there’s still time to change the outcome.
| 💡 Pro Tip: Before changing any process, run a realization audit on your last five closed projects. Pull hours logged, hours billed, and hours written off. The pattern will immediately tell you whether you have a scope definition problem, a billing process problem, or a resource allocation problem. That distinction determines which fix you actually need. |
How Kobi and the Skarya CFO Dashboard Stop the Bleed In-Flight
The operational shift that separates teams running 30%+ margins from those perpetually puzzled by the gap: profitability visibility has to live inside the delivery workflow, not in a separate finance tool someone checks at month end.
Skarya’s CFO Dashboard gives project leaders a live read on budget burn, realization rate, and resource cost, updated as hours are logged, not after the project closes. No manual reconciliation. No waiting for a finance report. The numbers move in real time, which means decisions that affect margin get made while there’s still margin left to protect.
| Kobi flags realization leaks before they reach billing. When a team member logs hours against a project tracking above scope, Kobi surfaces the discrepancy immediately. Project leads see the alert inside their workflow, raise a scope conversation with the client, or adjust resource allocation before the write-down becomes inevitable. The intervention happens at the moment it’s still possible to act on it. |
| The CFO Dashboard maps cost to task before you staff the project. One of the most expensive decisions in a project business happens at staffing: who gets assigned to what. Skarya’s resource view shows the cost rate of each team member against the value of each task phase, so you can match seniority to complexity before work begins, not after you’ve already burnt two weeks of partner time on tasks that should have gone to a mid-level. |
The CFO Dashboard also tracks write-downs as a project metric, not as an accounting footnote. Every hour written off is captured, categorised, and visible to the project lead and finance team simultaneously. Patterns that were previously invisible become actionable: if one project type consistently generates write-downs, that’s a pricing or scoping problem you can fix before the next engagement.
Resource Allocation Is Where Margin Is Won or Lost
Every time you assign a senior consultant to a task a mid-level could own, you’re making a margin decision. Most teams don’t recognise it that way, which is precisely why it keeps happening.
Effective resource allocation for profitability follows one principle: senior capacity is your scarcest, most expensive resource. Reserve it for work that genuinely requires senior judgment: complex problem-framing, high-stakes client decisions, quality control on critical deliverables. Everything else flows to the level it matches.
This requires two things most teams skip. First, explicit task classification at scoping: which phases require senior input, and which require mid-level execution? Second, a staffing view that shows cost against task complexity before assignments are made, not just availability.
Teams that build this discipline into their resourcing process consistently find that margin improves without changing their rates. The cost basis per project drops because the work is being done by the right person, not just the available one.
Making Margin a Live Metric, Not a Monthly Verdict
The final piece isn’t a tool or a process. It’s a decision about who owns the numbers.
In most project businesses, profitability is a finance team concern. The people making the daily decisions that destroy margin, scope accommodations, resource assignments, revision cycles absorbed without a change order, are completely disconnected from the financial data.
When project leads can see budget burn, realization rate, and write-down history in real time, inside the same platform where work is happening, the feedback loop closes. Scope drift gets flagged by the person managing the project, not discovered by the finance team three weeks later.
Make project-level profitability visible to the people leading the project before the project closes. Not in a separate dashboard they have to log into. Not in a report they have to request. In the same workflow view they’re already using.
That’s when profitability stops being a verdict and becomes a variable you can actually manage.
The Only Number That Actually Tells You If a Project Made Money
Utilisation fills timesheets. Realization fills bank accounts. If you’re only tracking one of them, you’re managing a feeling, not a margin.
The path to consistently profitable projects isn’t a pricing overhaul or a new client onboarding checklist. It’s closing the gap between hours worked and hours billed, matching resource cost to task complexity, and shifting profitability visibility from month-end reconciliation to active delivery management.
Find your realization rate right now. If it takes more than five minutes to locate that number, your system is already costing you money.
If you want to see how Skarya handles this in practice, Kobi flagging realization leaks before they reach billing, the CFO Dashboard mapping cost to task complexity, all of it live inside the delivery workflow, the platform was built for teams who are done managing margin in hindsight. See how it works →
Frequently Asked Questions
What is the difference between utilisation and realization rate in project management?
Utilisation measures how much of a team member’s time is spent on billable work. Realization measures how much of that billable time is actually invoiced and collected. A team can be fully utilised and still have poor realization if hours are being written off, absorbed into unbilled revisions, or logged against non-billable codes. Realization is the metric that determines whether a project actually made money.
What is a healthy project profitability margin for service businesses?
Most professional services firms target 20 to 35% net project margin. Firms consistently running below 15% typically have a realization problem, a resource cost alignment problem, or both. The benchmark varies by service type. Strategy and advisory work often targets higher margins than implementation or managed services, but the underlying drivers are the same.
Why do projects lose profitability even when they deliver on time?
On-time delivery and profitable delivery are not the same thing. Projects lose margin to unbilled revisions, senior staff performing low-complexity work, scope that was ambiguous at kickoff, and write-downs that never get reviewed. None of these show up in a delivery timeline. They appear in the gap between hours logged and hours invoiced at billing time.
How do I track project profitability in real time without a dedicated finance team?
You need a direct connection between scope, time logged, and billing status, visible to the project lead, not just the finance function. Tools like Skarya’s CFO Dashboard surface budget burn and realization rate in real time, inside the delivery workflow, so project leads can catch margin drift before the project closes rather than discovering it at reconciliation.
What is a project write-down and how does it affect profitability?
A write-down occurs when billable hours are reduced or removed from an invoice, usually to manage a client relationship when a project runs over scope. Occasional write-downs are a normal part of professional services. Systematic write-downs that are never tracked become invisible losses that compound over time. Treating write-downs as a project metric, not just an accounting entry, is one of the fastest ways to identify structural profitability problems across your portfolio.
Leave a Reply