What does each employee's time actually earn?

Revenue per paid hour connects payroll capacity, delivery time and earned revenue for the same period. Compare team, client and service economics before drawing conclusions about people. Use the result to review pricing and staffing, with clear allocation rules, restricted payroll detail and separate views of invoiced amounts and collected cash.

By SIGNLD Editorial · · 9 min read · Decision Intelligence
Payroll, time and accounting records compared to examine revenue per employee hour.

What is covered?

What does revenue per employee hour actually measure?

Revenue per employee hour compares revenue associated with work to the paid hours supporting it. Payroll knows the cost and paid time, time or project records describe where the work went, and accounting establishes what was earned, invoiced and collected. Those amounts are related, but they are not interchangeable. A meaningful comparison names the numerator and denominator before discussing performance.

This is primarily a pricing and staffing question. Are service prices covering the capacity required to deliver them? Does a team have enough time for the commitments already sold? Which client arrangements require more delivery effort than expected? It is not a reason to monitor individual activity continuously or infer someone's value from a single ratio.

The Cluster A guide to which deals actually made money follows deals into accounting. Here, the next step is the delivery effort behind those deals. A profitable sale can depend on an unrealistic assumption about available hours, while a currently low ratio can reflect onboarding or work whose revenue belongs to a later period.

Which records should you bring together?

Start with approved payroll costs and paid-hour records, approved time entries, project and client identifiers, invoice lines, payment allocations and the accounting revenue schedule where relevant. Add service agreements and budget assumptions so the result can distinguish included work from approved extra scope.

Keep employee identifiers separate from public names when possible. The analysis may need a stable internal reference, but it rarely needs bank details, tax identifiers or personal addresses. Limit the exported columns to the question, restrict access to sensitive amounts, and follow the organization's approval process before including payroll information.

The SIGNLD directory lists QuickBooks, Xero and Harvest, alongside HubSpot, Salesforce and Stripe. Gusto and ADP are not listed as direct connectors. Their payroll evidence must therefore be described as exports or files, not as an available direct connection. The integrations hub is the starting point for checking named combinations rather than assuming every source is supported.

Confirm the available fields and dates before building the comparison. A listed connector does not establish that every customer reference, ownership history or payroll component is present. Unmatched projects and uncertain allocations should remain visible, with an owner responsible for checking them.

How do paid hours differ from delivery hours?

Paid hours include the time for which the business compensates employees under its policies and records. Delivery hours describe time assigned to customer work. Depending on the business, paid time can also include leave, training, administration, sales support and internal improvements. Those activities are not automatically waste simply because they do not create an invoice line.

Define two measures when both are useful. Earned revenue divided by paid hours asks how the whole paid capacity supports the revenue base. Earned revenue divided by delivery hours asks how the work assigned to customers converts into revenue. Label them separately. Do not switch denominators between teams to make their results appear comparable.

For salaried roles, use a documented paid-capacity convention rather than pretending every payroll amount contains a literal hourly record. Have finance and the relevant manager approve that convention. If time entries are incomplete, identify the missing coverage rather than treating unrecorded hours as available capacity or absent work.

How should you assign labor cost and revenue?

Define loaded labor cost with finance. Include wages or salary and the employer costs relevant to the question, such as payroll taxes and benefits, without adding components already included in the payroll total. Keep shared overhead separate unless a documented allocation method assigns it. An invoice from a contractor belongs to a different source path but may support the same project.

Match time to projects using stable identifiers and service periods, then assign costs using a consistent rule. For fixed-fee work, the contract and accounting treatment govern earned revenue; an hour logged does not automatically create revenue. Invoice value shows what was requested, and collected cash shows what has actually been received.

Where several employees support one project, do not attribute the full project revenue to each of them and then sum the results. Allocate revenue once using an explained method, or retain it at team or project level. A precise person-level result can be less honest than an aggregate when the work is shared and the records do not establish individual attribution.

Document exclusions, partial payments, credits and currency handling. Keep forecast revenue separate from earned revenue. These distinctions allow the review to ask whether pricing covers delivery without presenting an expected collection as money already available.

What can an illustrative comparison reveal?

Consider a team with illustrative earned revenue of 30,000 currency units, 600 paid hours and 400 approved delivery hours in the same period. The illustrative earned revenue per paid hour is 50, while earned revenue per delivery hour is 75. These figures are illustrative, not a benchmark or an expected result.

Suppose illustrative loaded labor cost is 24,000 currency units for those 600 paid hours. That is an illustrative cost of 40 per paid hour. The difference between revenue and labor cost is not full project profit: supplier bills, software, facilities and other relevant costs still need their accounting treatment and allocation.

Now ask what changed when the next period's ratio moved. Did service prices change, did a project take more hours, or did paid onboarding capacity increase before billing began? The ratio points to a question. It does not answer it by itself, and comparing two employees with different responsibilities would not explain the commercial cause.

Why should the review focus on pricing and staffing?

A team's commercial result depends on commitments made outside the team as well as delivery itself. Sales can promise scope that was not priced, a client can delay approvals, and an account can receive an authorized concession. Individual hour counts do not establish control over those decisions.

Set the purpose before collecting data. Explain who will see the analysis and what decisions it is intended to inform. Restrict detailed payroll access, review aggregate results first and offer a way to correct inaccurate records. Do not use the ratio as an automatic ranking, dismissal trigger or compensation decision.

Look for repeatable service patterns rather than isolated personal comparisons. If a job type regularly requires extra supervision or overtime, review scope, scheduling and rates. If a team has unused capacity, check pipeline timing and required skills before assuming more work can simply be reassigned.

What should you do with the answer?

Assign a commercial question to each material difference. A service may need clearer scope, a project may need a revised staffing plan, or the invoice process may need an approval handoff. Name the evidence, proposed change and person authorized to decide. Do not rewrite historic hours to make the comparison fit the original budget.

Review proposals with delivery and finance together. Pricing changes should account for customer value and contractual commitments, not just a cost floor. Staffing changes should account for skills, lead times, leave and delivery uncertainty. A ratio can support those discussions while leaving room for the judgement the records cannot supply.

Which questions should you investigate next?

Use the companion guides to narrow the next review:

  1. Gusto and QuickBooks labor cost by client describes payroll exports alongside listed accounting records.
  2. ADP payroll and project margin follows payroll files into accounting and project evidence.
  3. Overtime cost by customer or job examines whether extra delivery effort is priced.
  4. Pricing services from actual delivery cost separates the cost floor from the pricing decision.
  5. Over-budget projects before they finish compares current burn with remaining work.
  6. Headcount planning from the pipeline combines probable demand with usable capacity.
  7. Freelancer versus employee cost compares project economics without giving classification advice.
  8. Harvest and Xero project profitability relates time evidence to accounting.
  9. Labor cost as a percentage of revenue defines a consistent team and monthly comparison.

How can SIGNLD support a careful review?

The Knowledge Graph builds automatically from connected sources, with no data engineering required. SIGNLD uses a private LLM powered by AWS Bedrock to investigate relationships in the available records. Keep a Decision Topic focused on a defined pricing or capacity question and a Decision Brief clear about evidence, allocation rules and uncertainties.

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.

Risk Alerts can prompt review of relevant changes, but they should not become automatic judgements about people. Missing hours, incomplete payroll files and uncertain project mappings still require correction or explicit limits before a finding informs a commercial decision.

Key takeaways

  • Paid hours and delivery hours answer different commercial questions and need separate labels.
  • Earned revenue, invoice value and collected cash should not be treated as interchangeable.
  • Shared project revenue should be allocated once or kept at an aggregate level.
  • Use labor economics to review pricing and staffing, not to rank or monitor employees.

FAQ

Is revenue per paid hour a measure of individual productivity?

Not by itself. The result depends on pricing, scope, staffing mix, accounting timing and the allocation method as well as delivery work. Shared projects may not support reliable person-level revenue attribution. Use the metric primarily for pricing and staffing reviews, present aggregates by default, and investigate the business cause before drawing conclusions about an individual.

Should leave and training be removed from paid hours?

Only if the chosen measure explicitly excludes them and is labelled accordingly. Paid-capacity economics often needs those hours because the business still bears the cost. Delivery-hour economics answers a different question. Keep both definitions visible, apply them consistently and explain material changes in leave or training rather than silently adjusting the denominator.

Can invoice totals stand in for earned revenue?

Not automatically. An invoice can request payment before the service is earned or after it was delivered. Use the accounting revenue treatment appropriate to the question, and show invoiced and collected amounts separately where useful. Match periods and credits so the comparison does not confuse a billing event with the revenue attributable to that period.

Does this require a direct payroll connector?

No. Approved payroll exports can provide relevant evidence when no listed direct connector exists. Gusto and ADP are not listed in the current SIGNLD connector directory. Use carefully scoped files, preserve their reporting dates and restrict sensitive fields. Confirm the evidence available before assuming that a file supports every cost or paid-hour allocation needed.

Related reading

Try SIGNLD free

See how SIGNLD works, then create your workspace with the Free Forever plan or a 14-day Growth trial, no credit card.