HVAC Company Business BrokerBook a call
Menu
HedgeStone Business Advisors
Tool

What do your HVAC technicians produce per workday?

Use matched field headcount, workdays and service appointments to measure what each technician produces. Then test whether additional calls would create more earnings after their direct costs. Compare your figures with source-defined operating targets only after your period, trade, job type and use of technician time line up.

What do your numbers show?

Compare like-for-like service calls, hours and sales across field technicians and test a proposed operating change.

Jump to results
Inputs

Your results

Revenue per technician-day
$918
Billable share
68%
Call conversion
79.17%
Incremental annual EBITDA
$20,188
Value sensitivity
$100,938

Your average collected ticket is $425. ServiceTitan Contractor Playbook, residential HVAC service technician (2026-11-21) gives a residential service target of $375 and a 85% closed-call target. Define eligible calls consistently.

Annual revenue per technician is $201,875 for the activity entered. CT Acquisitions, 2026 Home Services M&A Multiples Report (2026-04-01) places its HVAC market band at $180,000–$220,000. Use a full year with comparable technician roles and revenue scope before drawing a comparison.

Scenario comparison

Your average collected ticket is $425.

Your annual revenue per techYour annual revenue per tech: $201,875Published market band lowPublished market band low: $180,000Published market band highPublished market band high: $220,000$0$220,000 (USD)Source: your current inputs and the calculation described below. Model reviewed November 21, 2026.
Chart data
Values shown in the scenario comparison
SeriesComponentValue
Your annual revenue per techYour annual revenue per tech$201,875
Published market band lowPublished market band low$180,000
Published market band highPublished market band high$220,000
Email me these results

Assumptions and formulas

Annual revenue = sold jobs × average collected ticket. Revenue per technician per day divides that amount by field FTEs and days worked. Added completed calls are sold at the observed close rate and ticket. Apply your incremental contribution percentage to estimate the earnings change, then apply your own valuation sensitivity.

The initial fields are an illustrative composite. Replace them with records for your own business and use consistent periods.

This is an estimate, not an appraisal or valuation opinion.

Which work belongs in your productivity calculation?

Select one period and one type of work. Residential service calls, maintenance visits, replacement installations and commercial projects require different crew sizes and generate different tickets. A business that enters only repair appointments but counts installation revenue in average ticket will overstate productivity. A company that puts installers in the headcount but enters only service revenue can make a productive workforce look weak.

Use full-time-equivalent field headcount for the period. Include owners only to the extent their field work and associated revenue are represented. A lead technician who spent half the year supervising can be a partially productive field role, depending on how you defined the scope. Keep a note of the choice beside the technician roster and productivity tracker.

How do you calculate revenue per technician-day?

Multiply paid jobs by average collected service ticket to get period revenue. Divide by the product of field FTEs and workdays per technician. The result spreads revenue across the available crew-days, so unfilled schedules and time spent driving remain visible. Billable share separately divides billable hours by payroll hours and helps explain why daily revenue changed.

What can the published targets tell you?

ServiceTitan’s Contractor Playbook gives separate targets for residential service technicians, maintenance technicians and comfort advisers. Its benchmark reporting documentation further explains how peers can be grouped by trade, business type, region and company size. Match those definitions to your input before treating a comparison as a performance issue. A service-call close rate and a replacement-estimate close rate measure different events.

CT Acquisitions’ 2026 Home Services report supplies a range for annual HVAC revenue per technician in its market analysis. It describes an advisor’s market zone; it cannot tell you what every field employee in your city should produce. If your shop outsources installation labor, carries a large apprentice class or handles long-duration commercial projects, your reported revenue per technician may reflect those choices more than the quality of individual performance.

How does a productivity change reach EBITDA?

Start with a number of extra completed appointments you believe dispatch can schedule. Apply the observed paid-job conversion and average ticket. Then apply the incremental contribution margin, including the cost of extra technician hours, parts, commissions and support required for those jobs. Only the remaining contribution enters the estimated change in earnings. A larger payroll step, new vehicle or dispatcher hire can eliminate part of the improvement.

Apply your own adjusted EBITDA multiple to that estimated earnings change as a sensitivity. The calculation assumes incremental work and steady service quality. If added calls pull your strongest technician away from profitable replacements or increase warranty callbacks, revise the scenario. A more aggressive schedule can raise gross revenue and reduce the earnings a buyer can actually repeat after closing.

How can you test a dispatch improvement?

Choose a route or service line with documented idle time and identify the specific constraint. Group nearby calls, stage parts before the morning departure or add a dispatcher review of unfilled afternoon slots. Track the same metrics before and after the change. An increase in average ticket following a price update should be separated from an improvement in conversion or crew utilization.

  1. Reconcile completed appointments to technician assignments and invoice collections.
  2. Check paid and billable hours against payroll and timecards.
  3. Compare callbacks, complaints and gross profit during the test.
  4. Document which changes still work when the owner takes a week away.

Use the owner-dependence scorecard when your productivity case assumes the seller will keep selling complex jobs. Buyers will ask whether the remaining crew has the authority, training and capacity to keep the same results once the transition ends.

How can you distinguish efficiency from rushed work?

Sample completed work orders and review return trips, credits, complaints and warranty costs after the original invoice date. A technician might squeeze another appointment into the day by postponing documentation or leaving an underlying problem unresolved. The extra visit improves the daily tally today while an unpaid callback consumes capacity next month. Match those later costs to the original work when you evaluate the change.

Check territory, traffic, parts availability and equipment age before comparing two field employees. A rural route can produce fewer tickets per day even when the technician performs well. A new subdivision may generate fewer replacements than a neighborhood full of aging equipment. For acquisition diligence, use the differences to identify specific training, routing or staffing needs. A ranking that ignores differences in job type and geography cannot tell a buyer which improvement will survive the handoff.

How do you measure a technician-day when several people share a job?

Start with the company’s unique completed jobs, then match each job to actual people and paid time. A lead and a helper can both appear on one invoice without doubling revenue. Your denominator should reflect the people and hours needed to earn that revenue, particularly when you compare a service department with installation crews.

Take a hypothetical $12,000 system replacement performed by two installers over two days. On those assumptions it consumes four installer-days. If the report credits the full sale to the lead, their individual sales dashboard can show $12,000 and the helper zero. The team still earned $3,000 of job revenue per combined installer-day before considering costs. A report based on credited sales and a report based on crew days describe different things.

Check how the shop handles partial days and shared assignments. A technician might spend the morning diagnosing a failed unit, transfer the replacement lead to a comfort advisor and return in the afternoon to support an installer. Record the actual time allocation rather than counting a full service day and a full installation day for the same person. An imperfect documented estimate is easier to evaluate than two apparently precise numbers that use the same hours.

Ask the field supervisor which people the report leaves out. An apprentice may be essential to safe handling and setup. An owner may cover emergency diagnosis without a scheduled technician record. A service manager may spend a significant part of a workweek in the field during extreme weather. Decide which costs and capacity you are measuring, then explain how you treated each role.

How do you distinguish higher output from a price or mix change?

Compare activity, time, collected price and margin separately. Revenue per day can rise even when technicians complete the same number of jobs in the same hours. A changed pricebook, one expensive replacement or a larger share of commercial work can explain the increase without a change in field efficiency.

Pick a small basket of comparable jobs, such as a particular routine repair across similar service territories. Compare travel, diagnostic time, repair time, return visits and final collections. If the shop raised its price by ten percent while actual hours and materials stayed constant, much of the revenue-per-day gain reflects pricing. Determine whether customer acceptance and repeat work stayed stable before treating the higher price as sustainable.

Now examine an operational improvement. Suppose a team saves fifteen minutes per eligible visit across twelve visits a week by stocking a frequently needed part. That releases three hours under the example assumptions. If the time comes in scattered intervals between fixed appointments, it may not create capacity for another call. If dispatch can combine it into a useful block, calculate the incremental contribution from work the shop can actually book.

Include failed work in the test. A crew that completes jobs faster but doubles its no-charge return visits has shifted hours from one line of the report to another. Follow each initial job through its warranty or callback window and count the associated labor and travel. A buyer needs to know whether an apparent speed improvement produces lasting cash or simply postpones work the customer already paid for.

How can you validate a productivity assumption in the first operating quarter?

Select one branch, job type or route where the operating team can explain the problem and measure the change. Preserve a comparable baseline and record who controls dispatch, pricing, training and van stock. Your pilot needs a practical decision rule for expanding, revising or stopping the change.

For example, a dispatcher might move planned maintenance appointments into a tighter geographic route. Measure how many slots were actually filled, whether promised arrival windows were met, how much paid drive time changed and whether emergency capacity improved or worsened. A route that eliminates mileage could still harm higher-value service if it places all experienced technicians in one corner of the territory.

Watch the experience of the employees whose roles change. A lead technician spending extra time training a new hire may show a temporary decline in individual revenue while increasing future team capacity. Document the training period, milestones and realistic date when the new employee can take independent assignments. A productive buyer can support that investment without interpreting the trainer’s temporary result as poor performance.

Before using a projected improvement to justify a higher offer, calculate the downside if the change takes longer or produces fewer paid calls. Include recruitment, overtime, software, training and any extra vehicle cost. Show the standalone historical earnings and the buyer’s improvement case separately. After the first quarter, compare the job-level evidence with the original assumptions and keep the changes your customers, technicians and financial records all support.

Where can you go next?

What else should you know?

Should installation crews be counted in service headcount?

Include installation crews only when the revenue and jobs you enter include their work under a consistent definition. A service benchmark based on single-technician calls will not match a multi-person replacement crew. Split the reports by activity and compare like periods before building a combined operating view.

Is a higher average ticket always better?

A higher ticket can reflect parts inflation, a change in job mix, larger installed equipment or stronger pricing. Check gross profit per sold job and callback rates before interpreting the increase as better performance. A crew that sells expensive low-margin jobs can produce more revenue with little additional earnings.

How should I treat a trainee who rides along?

Record the trainee’s paid hours and role using the same convention throughout the period. A ride-along might add labor cost before increasing completed calls. For diligence, show headcount, productive FTEs and apprentice hours separately so a buyer can understand near-term capacity and the training investment behind future coverage.

Can I use the benchmark for a three-month peak season?

The daily metric can describe that period when the inputs use the same dates. The annual benchmark comparison needs a full-year figure with comparable activity. Annualizing a hot summer can overstate ordinary demand. Rerun the model on a full year before making staffing or purchase-price decisions.

Which sources informed this page?

Explore the operations hub