Two numbers decide whether HVAC scheduling and dispatch software is worth buying, and no demo will show you either one.
The first is 4.2. That is the average number of jobs an HVAC technician completes per day, according to Fieldproxy benchmark data drawn from more than 2,000 field service businesses, with the top quartile at 5.5 or more.
The second is 10 to 12. That is what a technician runs per day during peak cooling season, according to operator research cited by Sameday.
Same shop. Same technicians. Same software. Roughly two and a half times the load. Every vendor on the first page of Google will demo you a board on a calm Tuesday and quote you a price against your headcount. Nobody will ask what that board does in the third week of July.
The short answer
HVAC scheduling and dispatch software assigns technicians to jobs and pushes the details to the truck. Nearly every platform in the category does that competently. The differences that matter to an HVAC company are not on the feature grid: how the board behaves at two to three times normal load, how it turns a signed maintenance agreement into scheduled visits in your slowest months, and what it costs to leave when it does not work.
Evaluate it against your own demand curve. If you cannot describe your July load and your October load in numbers before the demo, you are not ready to buy.
Your demand curve is the specification
Roofing dispatch is gated by weather and material delivery. Electrical dispatch is gated by license ratios and inspection windows. HVAC dispatch is gated by something more brutal and more predictable: a demand curve that swings several times over inside one calendar year.
Here is the shape, using a modeled $2M residential HVAC company from Steph's Books' seasonal cash flow guide:
| Month | Revenue | % of annual | Season |
|---|---|---|---|
| January | $175,000 | 8.8% | Heating peak |
| February | $185,000 | 9.3% | Heating peak |
| March | $120,000 | 6.0% | Spring dead zone |
| April | $100,000 | 5.0% | Spring dead zone |
| May | $130,000 | 6.5% | Pre-summer ramp |
| June | $210,000 | 10.5% | Cooling peak |
| July | $250,000 | 12.5% | Cooling peak |
| August | $230,000 | 11.5% | Cooling peak |
| September | $130,000 | 6.5% | Fall dead zone |
| October | $85,000 | 4.3% | Fall dead zone |
| November | $160,000 | 8.0% | Heating ramp |
| December | $175,000 | 8.8% | Heating peak |
By the numbers
The gap between the best month and the worst month is $165,000, roughly three months of payroll for a ten-person shop. The two shoulder seasons, March through April and September through October, span a third of the year and produce 15 to 20 percent of annual revenue.
That curve is your specification. It says your dispatch board has two entirely different jobs. In the peaks, its job is triage: absorb more demand than you have capacity for without losing the high-value calls or the technicians. In the dead zones, its job is the opposite: find enough billable work to keep six trucks moving when the phone is not ringing.
Almost every buying guide in this category evaluates the first job and ignores the second.
What actually breaks in July
The failure mode is not a software crash. It is the board quietly stopping being a plan and becoming a queue.
HVAC technicians describe this the same way across years of threads. A tech in r/HVAC put it plainly: "1 minute I look at my schedule for the day and see two calls remaining next thing you know after I finish a call I have three more calls remaining. Lot of the times they put them in at the same time frame or same time window then I have to call and find out who I'm supposed to go to first because they have both calls promised at the same time slot."
Another described the cost precisely: "At 2, you're on your way to your last job, but then 3 more jobs get added, and your plan is out the window."
The most telling detail comes from a separate thread where a technician reports that his company runs ServiceTitan and has configured it so he cannot see his own day, "under the guise of 'the schedule is constantly changing.'"
That is not a software defect. It is a company responding rationally to a board that has no reserved capacity. When every emergency call must be inserted on top of already-committed work, showing the technician a plan you intend to break creates more friction than hiding it. The configuration is a symptom of the capacity model, and no feature list will surface it.
Watch out
If your evaluation only covers whether the platform can add an emergency job, you have tested the easy half. Test what the platform does to the six jobs that were already on that technician's day, what the customers on those jobs are told, and whether the technician can still see a plan he can trust.
The maintenance book is a dispatch instrument
This is the part the category gets most wrong. Maintenance agreements are sold to HVAC contractors as a marketing program and a retention play. They are both of those. They are also the single most important input to your dispatch board, and they are the reason HVAC scheduling is a genuinely different problem from every adjacent trade.
Look at where the visits land. The standard residential agreement is two visits a year: a spring cooling tune-up and a fall heating tune-up. FieldPad's guide to recurring PM contracts puts those windows at March through May and September through November.
Now put that against the revenue table above. Those windows are April at $100,000 and October at $85,000. The maintenance book is a mechanism that manufactures billable, pre-sold, route-densifiable work in the exact two months your phone goes quiet.
The economics back it up. Citing ACCA industry benchmarks, Steph's Books reports that maintenance contracts account for roughly 55 percent of total HVAC service revenue in well-run companies. Gross margins on maintenance visits land at 40 to 60 percent against 25 to 35 percent on emergency repair calls, and 30 to 40 percent of tune-up visits produce a paid repair or an equipment recommendation.
The slot rule nobody writes down
Here is the operational insight that no vendor page in this category covers. An HVAC manager on r/hvacadvice described the actual dispatch rule:
"If your working on 4 calls a day, first two should be maintenances, which clears 2 service calls for same day call-ins. If your in your slow period 3 maintenance calls a day, 1 service call slot."
Read that again, because it is the whole thesis in two sentences. The maintenance book is not filler. It is a reservoir of movable work that lets you hold same-day capacity open. A maintenance visit is the only job on your board that a customer will let you reschedule without losing the customer. An emergency no-cool call is not. An install is not. A commercial PM under contract mostly is not.
So the maintenance book is what makes reserved capacity affordable. Without it, holding two slots open per tech per day means holding two empty slots. With it, those slots are booked with work you can push a week if a heat wave arrives, and the ratio flexes with the season: two of four in normal periods, three of four in the dead zone, and in peak season a technician in that thread argued for "a max of 1 preventative maintenance call per day or saved to the end of the day."
Another owner in the same thread summarized why every shop should carry the book: maintenance agreements "collect service work" and "fill in the shoulder season to balance out the hours/month issues."
This gives you a hard evaluation criterion. When you demo a platform, do not ask whether it "supports memberships." Ask it to show you:
- How a signed agreement generates its spring and fall visits automatically.
- Whether those visits enter a backlog with a target window rather than a fixed calendar date.
- How the dispatcher sees remaining unscheduled agreement visits against remaining shoulder-season capacity.
- How fast a booked maintenance slot converts to a same-day emergency slot, and what the maintenance customer is automatically told.
Point four is the one that fails. Plenty of platforms generate the visits. Far fewer treat them as a movable buffer, which is the only thing that makes them useful in July.
Most field service platforms model a maintenance agreement as a billing object with a recurring calendar event attached. Almost none model it as capacity you can spend. If your shoulder season is empty and your peak season is chaos, the gap is usually in that one relationship. Pavado builds custom CRMs around the way your shop actually schedules.
The implementation calendar nobody plans
This one costs real money and it is entirely avoidable.
Enterprise HVAC platforms are not same-day setups. Tooled Up Pro's pricing research puts ServiceTitan implementation at 3 to 6 months for a 5 to 15 tech shop and 6 to 9 months at 15 to 50 techs, covering data migration, pricebook setup, integrations and training. Jobber and Housecall Pro are same-day by comparison.
Now overlay the demand curve. Most HVAC owners start shopping for software when they have time to shop, which is the fall dead zone, when October is billing $85,000 and the dispatcher is not drowning. A project kicked off in October at a 6 to 9 month timeline goes live somewhere between April and July.
That means your team learns a new pricebook, a new dispatch board and a new mobile app during the single month that produces 12.5 percent of your annual revenue.
Tip
Count backwards from your peak. Pick a go-live date that sits in a shoulder season with at least eight weeks of runway before the ramp, then run one complete peak season on the new board before you decommission the old process. If the vendor's timeline cannot hit that window, start the project next cycle rather than compressing it.
There is a second timing trap in the same place. You will evaluate the board when it is calm, and a drag-and-drop calendar with nine jobs on it looks great in every product on the market. Bring a real July day to the demo instead: your actual worst Tuesday, with the emergency inserts, the two callbacks and the tech who went home sick at 11 a.m.
What it costs, including the cost of being wrong
Published and reported pricing spans roughly two orders of magnitude, which tells you the category is not really one category.
| Platform | Reported pricing | Contract | Setup |
|---|---|---|---|
| Jobber | ~$299/mo (Grow, annual, 10 users) | None | Same day |
| Housecall Pro | From ~$79/mo (1 user) | None | Same day |
| FieldEdge | ~$100/tech/mo | 12 months | 2 to 4 weeks |
| ServiceTitan | ~$245 to $500/tech/mo | 12 months minimum | 6 to 12 months |
At ten technicians, Tooled Up Pro models ServiceTitan at $55,600 to $86,000 in year one including implementation, and $45,600 to $66,000 ongoing, against roughly $3,588 a year on Jobber's Grow plan for a comparable seat count. Pro add-ons such as marketing and phone modules are reported to lift the bill a further 40 to 60 percent.
The number almost nobody prices is the exit. ServiceTitan requires a 12-month minimum with no free trial and demo-only pricing. Early termination fees documented in BBB filings and compiled by Tooled Up Pro include $15,000 for a ten-tech operation, $23,000 for a mid-size plumbing company, $39,000 for an HVAC company with 18 months remaining, and $46,000 for a large electrical contractor.
Put that next to the implementation calendar and the risk becomes concrete. If you go live in June and the board fails its first peak, you find out in July, and you are still 11 months from being able to leave without a five-figure charge. That is the actual downside scenario, and it is the reason the peak-day test matters more than any feature comparison.
Per-technician pricing has one more HVAC-specific wrinkle. Many shops add seasonal help for the cooling peak, and per-seat billing prices your peak headcount. It also creates a quiet incentive to leave the summer hires off the system, which is precisely the decision that makes your peak-season dispatch data useless. If you hire seasonally, ask how mid-contract seat changes are billed in both directions.
Five tests to run before you sign
Bring these to the demo. They are ordered by how often they fail.
1. The July day. Hand the vendor a real peak day and ask them to build it live: 11 calls across four techs, three of them same-day emergencies booked after 10 a.m., one tech out sick. Watch what happens to the jobs that were already committed and what the affected customers are told.
2. The agreement backlog. Ask them to show 300 active maintenance agreements producing 600 annual visits, and then ask how the dispatcher knows in early September whether the fall book will fit in the fall. If the answer is a report you export to Excel, that is your answer.
3. The slot reservation. Ask whether you can reserve same-day capacity per technician per day, by season, as a rule rather than as a manual block a dispatcher has to remember to place. Then ask who is allowed to override it.
4. The seasonal seat change. Ask what happens to billing when you go from 6 technicians to 9 in May and back to 6 in September. Get it in writing.
5. The exit. Ask for the termination terms, the notice period and what data you can export, in what format, on the way out. A vendor confident in the product answers this quickly.
What to measure once it is live
Write these down before go-live, because the before-and-after is the only honest ROI test and you cannot reconstruct the "before" later.
- Jobs per technician per day, measured separately for peak and shoulder. The blended average hides everything. The HVAC benchmark is 4.2 with a 5.5 top quartile.
- Technician utilization. Fieldproxy's HVAC benchmark is 62 percent with a top quartile at 78 percent or better. FieldEdge puts the broader field service average at 55 to 60 percent.
- First-time fix rate. HVAC benchmark 73 percent, top quartile 85 percent or better. This is where a board that reserves capacity shows up, because rushed diagnostics produce callbacks.
- Shoulder-season revenue as a share of annual. The modeled shop above sits at 15 to 20 percent across four months. Moving that number is what your maintenance book is for.
- Percentage of agreement visits completed inside their target window. If you are running fall tune-ups in January, the book is not doing its job.
For the money side of that curve, our guide to contractor cash flow management covers the reserve strategy that makes the October trough survivable. If you are still deciding whether a dispatch board is even the right purchase, CRM vs field service software for HVAC settles that with one number, and how to track HVAC jobs from lead to invoice covers what happens downstream of the board.
When a custom build actually earns it
Buy first. An off-the-shelf platform your dispatcher actually uses beats a bespoke one you have to maintain, and that is true for the large majority of HVAC shops.
A custom build earns its keep when a constraint of your operation cannot be modelled in any product on the market. In HVAC that is usually one of three: a maintenance agreement structure that membership modules cannot express, a dual residential and commercial schedule where the same technicians serve two different booking rhythms, or a capacity model where reserved same-day slots need to flex by season automatically rather than by a dispatcher remembering to place blocks every Monday.
Below that bar, pick the cheapest platform that survives the July test and spend the difference on technicians. If you have hit that bar and the constraint is genuinely unmodellable, a custom CRM built around your scheduling model is the alternative worth pricing.
The bottom line
The category sells you a calendar and prices you on headcount. Neither is the thing that decides whether the purchase works.
What decides it is that your business runs on a curve with a $165,000 gap between its best and worst month, that your technicians run 4.2 jobs on an average day and 10 to 12 on a peak one, and that the only lever you own for smoothing both ends of that curve is a maintenance book most software treats as a billing record.
Test the board on your worst day. Test the agreement backlog on your slowest month. Price the exit before you sign. Everything else on the feature grid is table stakes.
Sources
- Fieldproxy, HVAC Industry Benchmarks (jobs per day, utilization, first-time fix, revenue per tech)
- Steph's Books, Seasonal Cash Flow for HVAC Contractors (monthly revenue model, ACCA maintenance benchmarks)
- Tooled Up Pro, ServiceTitan Pricing 2026 (pricing tiers, implementation timelines, BBB termination fees)
- FieldPad, Recurring Maintenance Contracts for Solo HVAC Techs (agreement structure and visit windows)
- Sameday, How HVAC Companies Maximize Capacity During Summer Season (peak-season calls per technician)
- FieldEdge, Technician Utilization Benchmarks (field service utilization averages)
- r/HVAC, Overworking your techs and Dispatch can go fuck themselves
- r/hvacadvice, How do you balance installs, repairs, and maintenance agreements?
