91¶¶Òõ

The construction labor narrative is dominated by the shortage, with reporting difficulty hiring. Sit in a portfolio review with your CFO and director of operations, though, and a different problem surfaces. Some projects feel busy and look fully staffed but still deliver lower margins than expected. The team is working hard, but the numbers don’t quite add up. Revenue per person per month is the metric that makes that mismatch visible.

Divide a project’s total monthly revenue by the number of salaried team members assigned to it. The output connects two numbers most contractors already track in a way that makes staffing efficiency visible at the project level. Utilization rate and labor cost as a percentage of budget both have their place, but neither tells you whether a specific project is carrying more people than the work requires or fewer than the schedule can sustain.

Revenue per person in practice

A project generating $2 million in monthly revenue with eight assigned team members produces $250,000 in revenue per person per month. The same project with twelve people assigned produces $167,000. Both projects might show healthy utilization numbers because everyone is busy, but the second project is carrying four more salaries against the same revenue, and that difference compounds across a portfolio.

The metric gets more useful when you compare it across projects of similar type and size. A hypothetical portfolio:

The numbers don’t tell the whole story on their own. Healthcare B might need more people because the scope is genuinely more complex. Commercial D might be overstaffed because the team was sized for peak activity and nobody adjusted when the project settled into a steady phase. Without the metric, those conversations don’t happen. The project feels busy, and busy looks like it’s working until the margins come in lower than expected.

Overstaffing in construction

The overstaffing problem is quieter than the shortage, and it shows up in predictable patterns. A project gets staffed for peak activity during preconstruction or early site work. That sizing made sense when the team was running 15 submittals a week and coordinating daily with three design teams. Six months later, the project is in a steady construction phase, the submittal volume has dropped, and the same team size persists because nobody flagged the change. The people are busy, just not generating proportional revenue.

Growth compounds it. When a contractor wins more work than expected, the instinct is to hire and assign. The urgency of getting people on projects overrides the discipline of right-sizing teams. “Because of effective planning, we can probably get a few more projects than we typically would’ve because it’s a huge risk when resources are your biggest limitation,” says Johnathon Grammer, Director of Operational Excellence at Rogers-O’Brien. The flipside is that without that effective planning, adding people doesn’t always translate to adding capacity. Sometimes it just adds cost.

According to the , benefit costs add roughly 30 to 44% on top of base wages depending on industry and worker classification, with construction sitting near the higher end. Apply that to a salaried project manager making $95,000 and the true cost to the company runs closer to $130,000 to $137,000 once benefits, insurance, and employment taxes are included.

One unnecessary PM on one project for six months represents roughly $68,500 in cost that didn’t need to happen. Multiply that across a portfolio of 15 to 20 active projects and the aggregate drag on profit margins becomes real. AGC’s 2026 outlook confirms the labor-cost pressure isn’t easing. in 2026, but . When salaried headcount is hard to add and expensive to carry, every assigned salary needs to be earning its keep.

The cost of running too lean

Understaffing is the opposite problem, and it’s arguably more dangerous to long-term business health. It saves on labor cost in the short term while creating schedule delays, quality issues, and team burnout that cost more down the line. The superintendent covering two buildings instead of one catches fewer problems. The PM handling three projects simultaneously responds to RFIs slower. Submittals back up, schedules slide, and the overtime costs that follow can erase whatever labor savings the lean staffing was supposed to produce.

The retention effect matters here too. The industry’s per BLS data is among the shortest of any major industry, which means contractors are already fighting to keep experienced people. Chronic understaffing accelerates departures, and the cost of replacing a senior PM (recruiting, onboarding, ramp-up productivity loss) dwarfs the cost of adding a team member when the workload justified it.

Revenue per person per month helps identify both sides. If the number is consistently above the portfolio average, the team may be stretched too thin. If it’s well below average with no complexity justification, the project is probably carrying more people than the work demands. Either way, the metric only works if you know what normal looks like for your organization.

The treadmill effect on staffing efficiency

91¶¶Òõ’s puts median annual attrition across its dataset of 233 contractors at roughly 20%. A contractor wanting to grow headcount by 100 in a year doesn’t need 100 hires. It needs 125 to net 100, because 25 will leave during the year. At 35% attrition, the math gets worse: 154 hires for 100 net adds.

Revenue per person that doesn’t account for the treadmill understates the true labor cost of growth. A new PM replacing a departed PM carries recruitment costs, ramp-up productivity loss, and onboarding time on top of salary, and the new PM’s revenue contribution lags their seat for months. Calculated quarterly without context, that dip looks like a project-level inefficiency when it’s actually a portfolio-level retention symptom.

The in the dataset show similar attrition to the broader industry but grow at roughly three times the rate. The differentiator isn’t lower turnover, it’s proactive planning that staffs around expected attrition rather than reacting to it.

Setting a revenue per person baseline

An isolated revenue-per-person number for one project tells you very little. The value comes from establishing a baseline across project types and noticing outliers.

Start with historical data. Pull the last 12 months of project financials and team assignment records, divide monthly revenue by salaried staff assigned that month, and group by build type and project phase. A useful baseline looks something like this:

These numbers are illustrative. Every contractor’s baseline will differ based on market, geography, and how they scope project teams. The point is establishing what normal looks like so deviations trigger a conversation rather than going unnoticed.

Phase matters because team size should change as a project moves through its lifecycle. Preconstruction teams are smaller but so is the monthly revenue recognition, peak construction has higher revenue and larger teams, and closeout should see team sizes shrink as revenue winds down. A project where closeout RPP drops below the baseline suggests people stayed on longer than the work required.

Four staffing decisions this metric informs

Revenue per person per month becomes a planning tool when it informs the decisions teams are already making.

Team sizing on new projects. Compare projected monthly revenue against the portfolio baseline for that build type. If expected RPP falls below baseline with the proposed team size, the project may be overstaffed from day one. If it’s well above baseline, the team may be too lean. Connecting the pursuit pipeline to workforce data makes this comparison possible before the team is finalized.

Phase transitions. Most projects don’t adjust team size as they move from preconstruction to construction to closeout. Revenue per person makes the case for right-sizing at each transition. If the metric drops 30% from peak construction to closeout, that’s a signal to reassign people to projects where they’re needed more.

Portfolio rebalancing. When RPP is visible across all active projects, it becomes possible to spot where people are underutilized and where teams are stretched. A project running 40% above baseline RPP while another runs 20% below suggests a reallocation opportunity. That conversation belongs in a weekly planning meeting, not a quarterly financial review when it’s too late to act.

Pursuit strategy. A new-sector project staffed primarily with newer hires will tend to run below baseline RPP because those team members take longer to reach full productivity. That insight should inform pursuit go/no-go decisions and the speed at which the workforce ramps in a new sector. The Top 50 ENR 400 contractors plan an average of , and the longer horizon is what makes scenario-based RPP modeling possible at all.

Getting started with what you already track

Revenue per person per month doesn’t require new systems or data most contractors don’t already have. Monthly revenue by project comes from accounting, team assignments come from whatever system tracks who is on what, and the calculation itself is division. The challenge is operational, not mathematical. Getting those two data sets into the same place at the same cadence, so the metric updates in real time rather than becoming a quarterly hindsight exercise, is where most contractors stall.

Workforce planning platforms like 91¶¶Òõ bring team assignments, project data, and forecasting into one view, making revenue per person visible across the portfolio without the spreadsheet gymnastics. The metric won’t tell you what to do, but it will tell you where to look. In an industry where margins are tight and the difference between a profitable project and a break-even one comes down to having the right number of the right people at the right time, knowing where to look is worth the effort.