This guide covers the firm economics behind a single project: utilization, the multiplier chain, and the forecast that shows where a phase will land while there is still time to change it.
Finance Field Guide · companion to the Module 2 Overview & Quick ReferenceModule Home › Finance Field Guide
Optional depth. Read this for the firm economics and forecasting mechanics behind the module. Not required for the weekly 90 minutes.
Module 2 answered two questions: is my project healthy? and how do I deliberately create and protect margin? This field guide answers the two questions that come next from almost every PM: “Why does my hour cost so much?” and “Where is my phase going to land?” The first answer is the firm’s economics. The second is the forecast. Both rest on one discipline: every hour is a business decision.
Firm economics
The $70 of overhead on every hour is arithmetic. Utilization is that arithmetic.
Utilization is measured in dollars, not hours: direct labor ÷ total labor, the share of the firm’s payroll charged to projects under contract. At the enterprise level, Grace runs at 62.5%. Read it against two individual seats before drawing a conclusion:
The last two tiles carry the first rule: utilization is not one number with one passing grade. A junior architect runs above 90%. A principal splits between projects, pursuits, and reviews. The C-suite sits almost entirely in overhead, by design. Every seat has its own target, and every seat can be healthy at a very different number. Comparing one utilization figure to another, or to the enterprise 62.5%, carries almost no information.
The enterprise number does mark where the economic model stands: only 62.5¢ of every payroll dollar lands on project work. The other 37.5¢, covering the proposals the firm chased, the QA reviews that protect the stamp, and the mentoring that builds the next generation, plus rent, software, and insurance, all rides on the direct work. That is where the 1.75 overhead factor comes from, and why there are no forty-dollar hours.
Two levers, one master metric
The firm’s year is every project’s scorecard, added up. Firm finance and project finance are the same arithmetic at different scale.
Module 2 set out the chain: overhead factor 1.75 → cost multiplier 2.75 → target net multiplier 3.23 to 3.44 → target margin 15 to 20%. The chain is really two levers: how much of the payroll lands on projects (utilization), and how much revenue each direct dollar earns (the multiplier). Either lever read alone gives a false reading. A team can post a strong multiplier while half its people sit between assignments. Another can be fully loaded on work priced too thin to matter. Multiply the two levers together and both distortions cancel:
Every $1.00 Grace spends on payroll, billable or not, should return about $2.00 of net revenue. Both levers sit inside it, which makes Revenue Factor the master metric for a group of people. The rule that follows: use the right metric at the right altitude.
| Altitude | The metric | Why that one |
|---|---|---|
| A project | Profitability: the 15 to 20% margin. Variance ④ live, Profit ⑥ projected | Projects do not have utilization. People do. A project has a fee, a cost, and a margin. |
| A team | Multiplier + utilization + Revenue Factor | Small enough to see both levers separately, and who is pulling each one. |
| A studio / business unit | Revenue Factor | One number, both levers included. ~2.0 at plan. Drift below it means one lever has slipped. |
| The enterprise | Utilization 62.5% · net multiplier 3.23 · EBITDA 22.5% (FY26) | Utilization is measured here, across the mix of every seat, from >90% juniors to low-by-design leadership. |
Trace the multiplier lever on Oakhaven, at project altitude, where it becomes profitability. Grace’s $1.4M of net revenue should ride on roughly $420k of raw wage labor, an NLM of about 3.3, on plan. Now apply the Margin Gap snapshot: $700k spent to earn $600k. That $700k of loaded effort is about $255k of raw wages ($700k ÷ 2.75). $600k earned on $255k of labor is an NLM of roughly 2.35. No rate changed. No budget was exceeded. The multiplier collapsed because effort ran ahead of earned value.
From scorecard to forecast
The scorecard reports the current position. The forecast answers a second question: where will the phase land if nothing changes?
Two definitions carry the forecast: ETC (estimate to complete) is the cost of the work remaining. EAC (estimate at completion) is what the phase will have cost when it is done: EAC = spent to date + ETC. The Profit column ⑥ on the BST scorecard is exactly this: the fee minus the EAC, projected at today’s pace.
| Method | How | What it’s for |
|---|---|---|
| Pace-holds the fast check | EAC = spent ÷ % truly complete. Thirty seconds with the scorecard. | Shows that there is a problem, and how big. This is the number BST projects. |
| Bottom-up the plan | Re-estimate the remaining work task by task, the same buildup that created the fee. | Shows the real options: which tasks, which people, which scope. |
Run the pace-holds math on Oakhaven’s CD phase, the red row on the scorecard. CD carries $490k of the fee. Mid-flight it has earned $300k and spent $400k. If the pace holds: $400k ÷ ($300k/$490k) ≈ $653k at completion, a projected −$163k on a phase priced to make ~$90k. That figure sits in the Profit column while the project total still reports on target.
Earned value = $160k, so the phase is delivering at half speed. Pace-holds EAC = $200k ÷ 0.40 = $500k. That is $100k past the entire fee. Act the week the gap opens, not at 90%.
Same discipline, flexible invoice
Everything above assumes a fixed fee. Hourly and T&M work runs on the identical scorecard, with one input that someone has to enter.
Every project, lump sum or hourly, needs an Effort Projection, the planned value of the work, in dollars, before it starts. Variance, EAC, and percent complete all measure against it. On a fixed fee, the Effort Projection already exists: it is the fee. On hourly work, no one enters it unless a PM builds it, and Budget Effort reads zero and Variance reads meaningless. That is a missing input, not a limit of the tool.
| Lump sum | Hourly / T&M | |
|---|---|---|
| Effort Projection comes from | The proposal, built once and locked into the contract | The PM, built at intake, before the work starts, from the same estimating skill |
| Invoicing ceiling | Locked to the Effort Projection by contract. They are the same number | Flexible. The PM can move it as the work develops. The client is billed for hours actually spent |
| A negative Variance means | Margin is leaving the project. The firm absorbs the overage | The projection was off. A signal to understand, and possibly to flex the ceiling, not a margin loss |
Yes. The shape of the work is already known: roughly how many hours, roughly which people, roughly how long. Write that down as an Effort Projection before the first hour is charged. It can then be staffed, tracked, and forecast exactly like any other task. The one thing that cannot be done, and does not need to be, is locking the invoice to it.
Cohesion
Behavior, not knowledge
On your throughline project, this week: