Revenue per technician: definition, formula, and dashboard example
Revenue per technician tells you how much income each field tech generates in a given period. Here is how to calculate it cleanly, what the number really signals, and how to watch it in real time so field performance stops being a monthly surprise.
Formula
Revenue per technician = total revenue generated ÷ number of active technicians (in the period)
Divide total revenue attributed to field technicians by the number of techs who ran calls in the same period. Run it monthly for trend comparison, weekly for coaching. For meaningful numbers, strip out jobs without a technician assignment and revenue lines not tied to field work (install-only P&L centers, for example).
Some operators calculate revenue per tech per day or per job count instead of per period. All three are valid; just label clearly and stay consistent so you can compare month over month.
What is revenue per technician?
Revenue per technician is the average revenue each active field tech produces over a set time window, usually a month. It is a productivity and capacity metric: how much of your field labor investment is turning into top-line revenue. For home-service companies with technician teams across HVAC, plumbing, electrical, or other trades, it is one of the clearest signals of whether your field operation is scaling or stalling.
Most operators know their total monthly revenue. Fewer know how that revenue is spread across techs. The average can hide a situation where two top performers are carrying the team while three others are running low-ticket calls, creating a hidden labor efficiency problem that does not show up until payroll analysis at month-end.
How the math works
To calculate it, divide the revenue generated in a period by the number of active technicians in that period. The average on its own can mislead, because a strong number can sit on top of a wide spread between your best and weakest tech, and that gap is the coaching and pricing opportunity, so read it per technician rather than as a single figure. On a datacube board per-technician revenue comes from the Completed Revenue column on ServiceTitan's Technician Performance Report or the Profit-by-date report in Housecall Pro.
Who owns it and how often to review it
Service managers and GMs own revenue per technician at the team level. Individual techs own their own number. Review it weekly on a leaderboard for live accountability, and monthly in a full technician scorecard alongside average ticket, close rate, and job count to diagnose whether a revenue dip is a pricing problem, a volume problem, or a mix problem.
How to improve it
Revenue per technician rises when techs run more jobs, close more options, or sell higher-value work. The levers are: optimizing dispatch to send the right tech to the right job type (reducing drive time and mismatched skill sets), coaching presentation and options selling in the field, running goal-based contests with visible leaderboards, and reviewing low-revenue call outcomes weekly to find patterns in declined work or incomplete installs. Visibility is the prerequisite: techs who can see their own number in real time consistently outperform those who only hear about it at a month-end meeting.
What good, watch, and poor revenue-per-technician movement signals
Targets vary by trade, service type, geographic market, and season. Use these as directional reads and set your own baseline from your last 90 days of data.
- Revenue per tech trending up month over month while job count holds steadyTechs are presenting and closing higher-value options; pricing or membership upsell is workingGood
- Current
- Target
- Revenue per tech flat while headcount growsNew techs may be diluting the average; split the view between tenured and new hires to diagnoseWatch
- Current
- Target
- More than a 2x spread between your highest and lowest techThe gap is usually a coaching and dispatch problem, not a headcount problemWatch
- Current
- Target
- Revenue per tech dropping in peak seasonDemand is there but techs may be rushing, skipping options, or running too many small ticketsPoor
- Current
- Target
- High revenue per tech but low job count and falling gross marginCould indicate parts-heavy work skewing revenue without margin; review job profitability alongsidePoor
- Current
- Target
| Metric | Current | Target | Status |
|---|---|---|---|
| Revenue per tech trending up month over month while job count holds steadyTechs are presenting and closing higher-value options; pricing or membership upsell is working | Good | ||
| Revenue per tech flat while headcount growsNew techs may be diluting the average; split the view between tenured and new hires to diagnose | Watch | ||
| More than a 2x spread between your highest and lowest techThe gap is usually a coaching and dispatch problem, not a headcount problem | Watch | ||
| Revenue per tech dropping in peak seasonDemand is there but techs may be rushing, skipping options, or running too many small tickets | Poor | ||
| High revenue per tech but low job count and falling gross marginCould indicate parts-heavy work skewing revenue without margin; review job profitability alongside | Poor |
Info
Coaching moment: what to do the day a tech's revenue dips
A sudden drop in one tech's revenue per day is a same-day conversation, not a month-end review. Possible causes: dispatch sent them to a low-opportunity call type, they are rushing through options on back-to-back jobs, or a parts shortage is killing completion rates. Pull their job list for that day, look at average ticket and close rate together, and coach on the specific pattern. A live board makes this a 10-minute manager check-in instead of a post-mortem.
Five ways revenue per technician gets distorted (and how to fix each)
| Distortion | What it does to the number | Fix |
|---|---|---|
| Including techs on vacation or leave in the denominator | Deflates the average; makes productive techs look weaker | Count only techs who ran at least one job in the period |
| Counting install-crew revenue alongside service-tech revenue | Mix of high-ticket installs inflates or deflates the service baseline | Segment service techs and install techs into separate views |
| Revenue credited to the wrong tech in the CRM | One tech's number looks exceptional; another looks weak artificially | Audit job assignments weekly; enforce dispatch attribution rules |
| Using invoiced revenue instead of collected revenue | Inflates the number if AR is slow; masks collection issues | Decide on a consistent revenue recognition rule and apply it to all techs equally |
| Not adjusting for seasonality | A December plumbing tech looks weak vs a July HVAC tech even if both are performing well | Compare year-over-year for the same period, or set seasonal targets per department |
Warning
Data visibility gap: why CRM reports lag on this number
Most CRM report screens show revenue per technician as a monthly export, which means you are reading last month's performance today. By the time a service manager opens that report, the low-revenue tech has already run two more weeks of underperforming calls. A live dashboard that surfaces individual tech revenue daily, with trend direction and a comparison to goal, turns this from a retrospective report into an in-the-moment coaching trigger. The goal is to catch a performance dip in week one, not week five.
Revenue per technician on a live field performance board
How revenue per technician appears on a datacube Techs board, updated throughout the day as jobs close in the CRM, displayed on a wall-mounted TV or a manager's mobile device.
Figures are illustrative. Your datacube board reflects your own connected CRM, QuickBooks, and field operations data.
KPIs to read alongside revenue per technician
| KPI | Why it pairs here |
|---|---|
| Average ticket | If revenue per tech is flat but job count is up, average ticket is falling; find the pricing or options-selling gap |
| Job profitability | High revenue per tech can coexist with low margin if parts costs are unchecked; always read these together |
| Gross margin | Confirms that higher revenue per tech is actually flowing to the bottom line |
| Callback rate | A tech generating high revenue but also high callbacks may be cutting corners; flag for quality review |
| Technician scorecard | The full multi-KPI view of a tech's performance: revenue, ticket, close rate, review score, and callbacks in one place |
Owner takeaway
- The team average is a starting point, not a conclusion. The spread between your best and weakest tech is where the real coaching work lives.
- Revenue per tech is most useful at the individual level, in real time. A monthly export tells you what happened. A live board lets you act on it today.
- Segment before comparing: service techs vs install techs, tenured vs new hires, and seasonal peaks vs slow periods all warrant separate baselines.
- Pair revenue per tech with job profitability and callback rate so a high number does not hide a quality or margin problem underneath it.
Revenue per technician FAQs
Build your technician performance board
See revenue per technician, average ticket, job count, and close rate for every tech on a live dashboard, updated throughout the day from your CRM so you can coach on what is happening now, not what happened last month.
Keep exploring
Related
Go deeper