Realization rate math every agency founder should be able to do on a whiteboard
How to calculate billable, effective and fixed-fee realization, why utilization hides the real problem, and which levers move realization without burning out the team.
Key takeaways
- Realization is billed value divided by the value of the hours you actually worked. Utilization tells you how busy people were, not whether you were paid.
- On fixed-fee work, realization is set at the moment you agree scope and decided every day after by what you let in.
- Unbilled scope is the realization lever with the least downside: it needs no price rise and no extra sales.
On this page (6 sections)
Three numbers that get confused
Agency finance conversations tend to mix up three numbers. They are related, but they answer different questions, and the confusion is why so many founders are surprised at year end.
| Metric | Formula | Question it answers |
|---|---|---|
| Utilization | Billable hours ÷ available hours | Were people busy on client work? |
| Realization | Revenue billed ÷ (hours worked × standard rate) | Were we paid for the work we did? |
| Gross margin | (Revenue − delivery cost) ÷ revenue | Did the work make money? |
A team can be 85% utilized and still lose money if realization is poor. That is the trap of fixed-fee delivery: everyone is busy, timesheets look healthy, and a growing share of those hours are being spent on work no one agreed to pay for.
A worked example on one fixed-fee project
Take a $96,000 fixed-fee web platform. The agency's standard blended rate is $150 per hour, so the fee implies 640 hours of work. Delivery cost runs at $60 per hour.
- Planned: 640 hours, $38,400 delivery cost, $57,600 gross profit, 60% margin, 100% realization.
- Actual: the team logs 820 hours because of rework, extra review cycles and roughly 120 hours of client requests that were outside the SOW.
- Realization: $96,000 ÷ (820 × $150) = $96,000 ÷ $123,000 = 78%.
- Delivery cost: 820 × $60 = $49,200. Gross margin: ($96,000 − $49,200) ÷ $96,000 = 48.75%.
Twelve points of margin disappeared without a single failed milestone. Now split the 180 extra hours by cause. About 60 were genuine estimation error, the kind you fix by estimating better next time. About 120 were scope that a client asked for and the team delivered. Those 120 hours, at $150, are $18,000 of work that could have been a change order.
If even two thirds of that had been raised and approved, the project would have billed $108,000 for 820 hours: realization of 88% and a margin of about 54%. Same team, same client, same hours. The difference is whether the extra work was priced.
Where realization leaks on fixed-fee work
On time-and-materials work, realization leaks through write-downs: hours that were logged and then cut from the invoice. On fixed-fee work, there is no invoice line to cut, so the leak happens upstream. The main sources, in rough order of size in our onboarding cohort:
- Unpriced scope additions, mostly small requests made in chat and delivered without a change order.
- Revision loops beyond the agreed rounds, especially in design and content-heavy projects.
- Estimation error on the original scope, often on integrations and data migration.
- Internal rework caused by unclear requirements, which is partly an estimation problem and partly a scope problem.
- Non-billable project management overhead that grows with the number of stakeholders.
Only the first two are fully fixable inside a live project. Estimation error is a lesson for the next SOW. Rework and overhead can be reduced but not invoiced. That is why unbilled scope is the lever founders should look at first: it is already worked, it is already valuable to the client, and it simply has not been priced.
Measuring realization without a finance team
You do not need an ERP to track this. You need three inputs per project: the fee, the hours logged and a standard rate. Most agencies already have all three in Harvest, Toggl or Clockify and their accounting system.
- Pick one standard blended rate per role or per agency and stop changing it mid-year.
- Every month, compute realization per project as revenue recognized divided by hours logged times standard rate.
- Tag hours that went to work outside the SOW. This is the step most teams skip, because nobody knows in the moment which work was outside the SOW.
- Report three numbers to leadership: realization, unbilled scope hours, and change orders raised versus approved.
Levers that move realization, ranked by side effects
Founders usually reach for the levers that have the worst side effects first. Here is the same list ordered by how much collateral damage each one tends to cause.
| Lever | Typical effect | Side effects |
|---|---|---|
| Price unbilled scope as change orders | High on current projects | Low when evidence is clear and timely |
| Tighter SOW exclusions and revision caps | High on future projects | Low, clients prefer clarity |
| Better estimation on integrations | Medium on future projects | Low, slower proposals |
| Raise rates | Medium | Can slow sales |
| Push team to log fewer hours | Looks high, is zero | Hides the problem and erodes trust |
| Ask for unpaid overtime | Short-term only | Burnout and attrition |
The last two are worth naming because they are common. Telling people to log fewer hours improves the realization number without changing reality. Asking for weekend work to protect a fixed fee transfers the cost of unpriced scope onto your team's evenings. Both make the next project worse.
What good looks like
Agencies with healthy fixed-fee economics do not have clients who never ask for more. They have a system where every ask is noticed, compared to the contract, estimated and either absorbed on purpose or priced. In TWINJAM's onboarding audit, agencies reclaimed an average of 18.4% of project margin once that system was in place, mostly by billing work they were already doing.
The whiteboard version is simple. Know your rate, know your hours, know which hours were inside the contract. The rest is having the conversation, which we cover in the change order guide.
Arjun Bhatia
Finance & Revenue Operations Lead, TWINJAM
Arjun builds the margin telemetry models and previously ran finance for a 90-person product studio. He thinks in realization rates.
Newsletter
The Profitable Agency
Weekly teardowns of agency contract terms, margin protection and delivery operations. One email every Thursday, no fluff.
Read by delivery leads and agency founders. Unsubscribe in one click.