Productivity per Hour
How Productivity Is Calculated
Productivity per Employee = Total Output (or Revenue) ÷ Employees
Utilization (%) = ( Productive Hours ÷ Hours per Employee ) × 100
Achievement (%) = ( Productivity per Hour ÷ Target per Hour ) × 100
Worked Example: A 15-Person Support Team
A 15-person customer support team works 160 hours each per month — 2,400 total labor hours. Of those, timesheets show roughly 1,920 hours were spent on actual ticket work (the rest went to meetings, training, and admin). The team resolved 11,520 tickets in the month.
Utilization = ( 1,920 ÷ 2,400 ) × 100 = 80%
Per productive hour = 11,520 ÷ 1,920 = 6.0 tickets/hour
The distinction between the 4.8 and the 6.0 matters. If leadership wants more throughput, the two levers behave very differently: raising per-hour speed usually means training, better tooling, or macros — slow to move. Raising utilization from 80% to 85% (cutting two hours of meetings per person per week) adds ~120 productive hours a month, or roughly 720 extra tickets, with zero extra headcount. Most teams find utilization is the cheaper lever — up to the burnout ceiling.
Two cautions when using this metric. First, productivity numbers are only comparable within the same role and output definition — 4.8 tickets/hour cannot be compared to another team's 3.2 if their tickets are harder. Track your own trend line month over month instead. Second, watch for Goodhart's law: when a productivity number becomes a target, people optimise the number (closing tickets fast, splitting tasks) rather than the outcome. Pair any output metric with a quality signal — reopen rate, CSAT, error rate — before using it in performance conversations.
US 2026 Reference Benchmarks
Output-Based (per productive hour)
| Role / Team | Typical Output per Hour |
|---|---|
| Customer Support (tickets resolved) | 4 - 8 |
| Sales (outbound calls) | 25 - 40 |
| Warehouse (order picks) | 60 - 100 |
| Manufacturing (light assembly units) | 20 - 40 |
| Content (short posts / articles) | 1 - 2 |
Revenue-Based (annual, per employee)
| Industry | Median Revenue per Employee (USD) |
|---|---|
| General / All Industries | $250,000 |
| Technology / SaaS | $420,000 |
| Financial Services | $520,000 |
| Healthcare | $210,000 |
| Manufacturing | $310,000 |
| Retail & E-commerce | $260,000 |
| Hospitality | $95,000 |
How to Improve Workforce Productivity
- Automate Repetitive WorkUse workflow tools & AI to eliminate manual overhead and free up productive hours.
- Cut Meeting OverheadDefault to async updates; reserve live meetings for decisions only.
- Match Staffing to DemandRight-size teams based on weekly workload data, not annual forecasts.
- Invest in TrainingSkilled, confident workers produce more per hour with fewer errors and less rework.
- Measure & Share KPIsVisibility creates ownership. Share productivity metrics with the team weekly.
Frequently Asked Questions
What is workforce productivity?
It measures how much output - units, tasks, or revenue - your workforce generates per hour or per employee during a set period.
How do you calculate productivity per hour?
Divide total output (or revenue) by the total labor hours worked: Employees × Hours per Employee. This gives you units or revenue per hour of labor input.
What is a good utilization rate?
For knowledge and billable-hour teams, 70-85% is a healthy target. Above 90% risks burnout and quality degradation; below 60% indicates significant idle capacity or inefficiency.
Should I use Output or Revenue mode?
Use Output mode for operations, support, and production teams where physical or task counts are meaningful. Use Revenue mode for whole-company, sales, or service productivity KPIs.
How can I improve productivity?
Automate repetitive work, invest in upskilling, reduce unnecessary meetings, remove process blockers, and align headcount with real demand cycles.
Why did my productivity per hour drop after hiring?
This is normal and expected. New hires add full labor hours to the denominator immediately but take 3–6 months to reach full output. A dip after a hiring wave is a ramp-up artifact, not a performance problem — compare against the same period last year, or exclude employees in their first 90 days for a cleaner trend.
Should overtime hours be included?
Yes — include all hours actually worked, not just contracted hours. Excluding overtime overstates productivity and hides the fact that output is being sustained by extra labor input. If output only holds up because of recurring overtime, that is a staffing signal, not a productivity win.
Is this tool free?
Yes - 100% free, no login required, no data is stored or uploaded anywhere.