Revenue per person per month divides a project’s total revenue by the number of salaried team members assigned to it. It connects two numbers most contractors already have, revenue and headcount, in a way that makes staffing efficiency visible at the project level. The industry tracks utilization rate and labor cost as a percentage of budget, but neither tells you whether a specific project is carrying more people than the work requires or fewer than the schedule can sustain.
Table of Contents
“We spent too much time simply trying to display our data correctly and it detracted from the problem-solving and thoughtfulness that workforce planning and scheduling deserve,” says Keyan Zandy, CEO of Skiles Group.
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. Here’s what a hypothetical portfolio might look like:
| Project | Monthly revenue | Team size | Revenue per person | Notes |
|---|---|---|---|---|
| Healthcare A | $1.8M | 6 | $300K | Experienced team, repeat client |
| Healthcare B | $2.1M | 10 | $210K | Three newer PMs, first-time build type |
| Commercial C | $1.2M | 5 | $240K | Lean team, strong superintendent |
| Commercial D | $1.4M | 8 | $175K | Overstaffed during ramp-up, never adjusted |
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. But without the metric, those conversations don’t happen. The project just feels busy, and busy looks like it’s working until the margins come in lower than expected.
Overstaffing in construction
The construction industry has an understaffing narrative and the data supports it. 92% of construction firms report having a hard time finding workers to hire. The labor shortage dominates every industry conference and trade publication.
Overstaffing is the quieter problem, and it happens in predictable patterns. A project gets staffed for peak activity during preconstruction or early site work. The team size made sense when there were 15 submittals a week and daily coordination 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.
The financial impact is concrete. Labor burden in construction averages approximately 44% of base wages, according to Construction Coverage’s analysis of Bureau of Labor Statistics data. Apply that to a salaried project manager making $95,000 and the true cost to the company is closer to $137,000 once you include benefits, insurance, and employment taxes.
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.
The cost of running too lean
The opposite problem is just as real and arguably more dangerous to long-term business health. Understaffing saves on labor cost in the short term while creating schedule delays, quality issues, and team burnout that cost more down the line.
An understaffed project pushes experienced people past sustainable workloads. 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.
“Company morale goes down, employees are burnt out because they’re going to do whatever it takes to get the job done. It affects your employee retention and increases safety incidents on a project,” says Shawn Gallant, COO of Columbia Construction. “With any safety incident, there’s a cost, but more importantly, somebody’s personal life could be impacted.”
The retention effect matters here too. The industry’s average employee tenure of 3.9 years means contractors are already fighting to keep experienced people. Chronic understaffing accelerates departures. The cost of replacing a senior PM, including recruiting, onboarding, and the productivity gap while the replacement gets up to speed, 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 for a project, 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.
Setting a revenue per person baseline
The metric is only useful as a comparison tool. An isolated revenue-per-person number for one project tells you very little. The value comes from establishing a baseline across project types and then noticing outliers.
Start with historical data. Pull the last 12 months of project financials and team assignment records. For each project, divide monthly revenue by the number of salaried staff assigned that month. Group the results by build type and project phase:
| Build type | Avg RPP (preconstruction) | Avg RPP (peak construction) | Avg RPP (closeout) |
|---|---|---|---|
| Healthcare | $185K | $255K | $320K |
| Commercial | $205K | $280K | $345K |
| Industrial | $215K | $305K | $375K |
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 that deviations trigger a conversation rather than going unnoticed.
Phase matters because team size should change as a project moves through its lifecycle, and your utilization rate should reflect those transitions. Preconstruction teams are smaller but so is the monthly revenue recognition. Peak construction has higher revenue and larger teams. Closeout should see team sizes shrink as revenue winds down. A project where closeout RPP drops below the baseline suggests people stayed on the project longer than the work required.
“We have total transparency in our metrics now. Fast-forward from last year to this year, our utilization has exceeded our targets. The increased utilization rate contributes directly to higher than forecasted profits,” says Ed McCauley, VP of Corporate Services at Wohlsen Construction. Revenue per person per month makes that utilization-to-profit connection visible at the project level, where staffing decisions actually get made.
Four staffing decisions this metric informs
Revenue per person per month becomes a planning tool when it informs the decisions you’re already making.
For team sizing on new projects, compare the projected monthly revenue against your portfolio baseline for that build type. If the 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 for the scope. The Forecasting Dashboard that connects your pursuit pipeline to workforce data makes this comparison possible before you finalize a team.
For phase transitions, most projects don’t adjust team size as they move from preconstruction to construction to closeout. The preconstruction team stays on through construction, and the construction team stays on through closeout. Revenue per person per month 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.
For portfolio rebalancing, when you can see RPP across all active projects, you can 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.
For pursuit strategy, scenario planning becomes more grounded when you can model the RPP impact of winning a new project. Gilbane Building Company faced this when expanding into data centers and advanced manufacturing, sectors that required specialized expertise their existing teams hadn’t built before. With workforce data centralized across regions, they could evaluate pursuits with confidence that the right teams could be assembled. Without that kind of visibility, the projected RPP for a new-sector project staffed primarily with newer hires will tend to be lower than baseline, because those team members take longer to reach full productivity.
“Bridgit saves me personally at least 4-6 hours a week. And then if you multiply that across the company, we’re saving hundreds of hours a week,” says Chris Martin, VP of Technology Services at MYCON. Those reclaimed hours shift what operations leaders spend their time on. Instead of data entry and spreadsheet maintenance, they can look at metrics like revenue per person and ask whether the staffing configuration is producing the returns the business needs.
Getting started with what you already track
Revenue per person per month doesn’t require new systems or data that most contractors don’t already have. Monthly revenue by project comes from accounting. Team assignments come from whatever system tracks who is on what. The calculation is division.
The math is simple. Getting those two data sets into the same place, at the same cadence, so the metric updates in real time instead of being a quarterly exercise in hindsight, is the actual challenge. The contractors who connect workforce data to financial outcomes in real time are the ones who catch overstaffing before it erodes margins and understaffing before it burns people out. Workforce planning platforms like Bridgit 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. It tells you where to look. In an industry where margins are tight, labor costs are rising, 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.
