Labor cost as a percent of revenue, by month and team

A company labor ratio can conceal teams with very different delivery economics. Define employer costs, match them to revenue periods, and calculate team ratios using documented allocation rules. Build an internal baseline rather than borrowing an unsupported benchmark, then use the comparison to review pricing, service mix, and staffing capacity.

By SIGNLD Editorial · · 8 min read · Core Concepts
Payroll, time and accounting records compared to examine labor cost percentage of revenue.

What is covered?

What does the percentage measure?

Labor cost percentage of revenue measures how much of a defined revenue amount is absorbed by a defined set of labor costs. The calculation is labor cost divided by revenue, multiplied by 100. Its usefulness depends less on the arithmetic than on consistent definitions of cost, revenue, period, and reporting group.

For illustration only, a team with $60,000 of included labor cost and $100,000 of matched revenue has a labor ratio of 60%. That leaves 40% before any excluded expenses, not necessarily profit. Supplier costs, facilities, software, and other overhead may still need to be paid. These numbers are invented examples, not benchmarks.

A ratio can move because costs rise, revenue falls, or both. It can also move because an accounting adjustment changes the denominator. Always show the underlying cost and revenue totals beside the percentage. If revenue is zero or negative, flag the ratio for review rather than presenting an ordinary percentage that invites a misleading comparison.

For a broader view of paid hours and commercial results, see what each employee's time actually earns. The monthly ratio here supports pricing and staffing discussions at team level. It is not an individual productivity score or a reason to rank employees.

Which payroll costs should you include?

Begin with gross wages and salaries, then identify employer payroll taxes, employer benefit contributions, and other employer costs included in your policy. Decide how bonuses, commissions, overtime premiums, and paid leave will be treated. Finance should approve the definition so monthly movements do not reflect changing inclusion rules.

Do not add employee deductions as though each were a separate employer expense. Likewise, avoid counting paid leave twice if it is already included in gross pay. Employer contributions and employee withholdings can appear near each other in payroll files while representing different things. Field selection needs review, not a blanket sum of every column.

State whether contractor costs belong in the metric. A narrow payroll ratio may exclude them, while a broader delivery labor ratio may include supplier labor. Either can be useful if labeled accurately and applied consistently. If staffing shifts from employees to contractors, an unchanged narrow payroll ratio can conceal an increase in total delivery cost.

Keep direct labor and shared labor distinguishable. A delivery team, central administration, and company leadership have different relationships to revenue. You can show direct team ratios alongside a company ratio that includes shared labor. If shared costs are allocated to teams, publish the basis and avoid counting the same costs again in consolidation.

How do you match months and teams?

Use the revenue period and cost period that finance approves for the question. A payroll payment date may cover work performed partly in the previous month. An invoice can cover future work or arrive after delivery. Matching calendar payment dates alone can manufacture a swing that says little about actual operating performance.

Where accrual reporting applies, use the relevant adjustments and record how payroll crossing month end is assigned. Treat bonuses and irregular employer costs consistently, with a note when they materially affect a month. Do not quietly remove an unfavorable item simply to make the ratio resemble the previous period.

Team mapping needs dates too. If someone moves between teams midmonth, use the approved assignment or recorded allocation for that period. For people serving several teams, apply a documented method based on supported hours or another agreed driver. Leave unresolved amounts visible instead of assigning them to whichever team has room in its budget.

Revenue allocation also needs a rule. Shared clients and bundled services may not map neatly to one team. Agree how those amounts are attributed before comparing ratios. Otherwise, one team can appear expensive simply because another team receives the revenue credit for work they delivered together.

Why can the company total hide a problem?

A stable company percentage can conceal opposing team movements. One group may improve its pricing while another absorbs extra revisions without corresponding revenue. Their effects can cancel at company level. Looking only at the overall ratio can delay a useful discussion about scope, service mix, and capacity.

Compare teams only after checking that their responsibilities and revenue treatment are comparable. A support function without directly attributed revenue should not be judged by the same ratio as a delivery team. Treat it through an explicit shared cost view or another appropriate planning measure, not an artificially unfavorable team ranking.

Investigate a change through its components. Did overtime increase? Did discounts reduce revenue? Did hiring precede a planned launch? Did a large credit fall into the month? The ratio identifies a question; it does not identify fault. Pricing, scheduling, and customer terms may explain more than employee effort does.

How should you set an internal baseline?

Start with several comparable closed periods using the same definitions. Separate service types or seasons when their economics differ, and note material changes in team composition or accounting policy. Use the resulting pattern as an internal baseline, not a claim about what every company in the sector should achieve.

Agree a review range with finance and delivery leaders based on your own margins, commitments, and capacity plans. No unsupported industry benchmark is needed. A movement outside that range should prompt investigation, not an automatic staffing cut. Document the cause, action, owner, and review date so the next month tests an actual hypothesis.

How can SIGNLD support a monthly review?

The connector directory lists QuickBooks, Harvest, Xero, HubSpot, Salesforce, and Stripe. Gusto and ADP are not listed, so use payroll files rather than assuming direct connections. Confirm accounting fields and available team references before deciding which monthly comparisons the evidence can support.

SIGNLD's Knowledge Graph builds automatically from connected sources, with no data engineering required. Review entity matches, date boundaries, and allocation rules before accepting a team result. Use a Decision Topic for the recurring review and a Decision Brief to explain the ratio, exceptions, and proposed pricing or staffing action.

Restrict payroll inputs to approved identifiers, periods, and necessary employer cost components. Keep unrelated personal fields out and share aggregates with managers. Avoid surveillance, employee rankings, and small reporting groups that reveal individual pay. Risk Alerts can support ongoing review of configured changes once the baseline and ownership are clear.

Your data stays yours: read-only connections, a private LLM powered by AWS Bedrock on a single-tenant instance, and we never train on it.

Key takeaways

  • Calculate the ratio using a documented employer cost definition and revenue from the same period.
  • Review team ratios because a company total can conceal changes in service mix and delivery cost.
  • Set internal baselines from comparable periods rather than relying on unsupported industry percentages.
  • Use restricted payroll inputs and aggregate reporting to support pricing and staffing, not employee rankings.

FAQ

Is a lower labor percentage always better?

No. A lower percentage can reflect higher prices or efficient delivery, but it can also reflect understaffing, deferred hiring, or a temporary revenue spike. Check service quality, commitments, and capacity alongside the ratio. The useful question is whether the cost structure supports the work and financial plan, not whether the percentage can be reduced indefinitely.

Should contractor payments be included?

Include them if you are measuring total delivery labor, and label that broader definition clearly. Exclude them if the stated measure is specifically payroll cost, but show a separate contractor view when material. Keep the definition stable across months so a shift in staffing arrangement does not masquerade as an improvement in underlying delivery economics.

What should happen when revenue is unusually low?

Show the underlying totals and investigate the reason before comparing the percentage with ordinary months. Revenue timing, credits, seasonality, or delayed delivery can produce a large ratio without a matching increase in labor cost. If revenue is zero or negative, mark the ratio as not meaningful for ordinary comparison and explain the exception.

How many months are needed for a useful baseline?

There is no universal minimum that fits every business. Use enough comparable closed periods to understand your own seasonal patterns, billing cycles, and staffing changes. If history is limited, label the baseline provisional and review it as new periods close. Avoid presenting a short or structurally different history as a dependable target for every team.

Related reading

Try SIGNLD free

Explore the core concepts, then register for SIGNLD. Choose the Free Forever plan or a 14-day Growth trial, no credit card. Start with one closed month, approved payroll fields, and a team allocation policy.