Field Service Software for HVAC: Build or Buy at 25 Trucks
The threshold is roughly 25 trucks, or the point where per seat fees cross $3,000 to $6,000 a month once office seats are counted. Below it, buy Jobber or Housecall Pro and go live in weeks.
On this page
The threshold is roughly 25 trucks, or the point where per seat fees cross $3,000 to $6,000 a month once office seats are counted. Below it, buy Jobber or Housecall Pro and go live in weeks. Above it the licence total still does not decide the question on its own, because a full build plus maintenance runs close to $260,000 over three years against $162,000 of subscription. What decides it is a specific misfit you can price: renewals lapsing in a spreadsheet, or a board that cannot see certifications. Most shops under 20 trucks should buy.
When is off the shelf genuinely the right call here?
Under 15 to 20 trucks, buy, and it is not close. Jobber and Housecall Pro will give you dispatch, work orders and invoicing in weeks for a monthly fee, and the workflow template fits most residential service shops closely enough that fighting it would be an odd use of money. ServiceTitan is the serious purchase as you get larger and want depth. FIELDBOSS is a credible option if you already run Microsoft Dynamics and want field service inside it rather than beside it.
These products exist because most shops have workflows close enough to the template, and custom field service management, usually shortened to FSM, is not a status symbol. It is a decision you make when the packaged tool's constraints are metered directly against your profit and loss.
Keep buying if your only complaint is a single missing feature. That is a workflow problem rather than a platform problem, and a build is an expensive way to solve it. Keep buying too if you cannot name the misfit in money. A shop that says the software is frustrating but cannot point to lapsed renewals, double entry hours or jobs routed to the wrong technician does not have a build case yet, it has a training and configuration case.
When does a custom build actually pay off?
When the misfit is metered against your numbers rather than felt in the office.
Build when per seat fees have crossed roughly $3,000 to $6,000 a month and keep climbing with every hire. Build when your dispatch or preventive maintenance logic is genuinely unusual and the packaged tool punishes it, for example commercial service agreements with equipment lists and per unit schedules sitting alongside residential no cool calls. Build when you are stitching together three or four subscriptions that do not talk to each other. Or build when the roadmap you depend on keeps postponing the one capability that would move your close rate.
The most common concrete trigger we see is preventive maintenance contracts living in a spreadsheet. A missed visit is a lost renewal, and renewals are the part of an heating, ventilation and air conditioning book that a buyer would actually pay for. If nine hundred agreements are being tracked by hand and a proportion of them quietly lapse each year, that is a number you can calculate, and it is usually larger than the licence you were arguing about.
The other honest trigger is a dispatcher rebuilding the board every morning because the tool cannot see which technician holds which certification, which unit is on the van, and how far the drive is. That is not a preference. It is jobs routed wrong every day.
How do they compare on the things that matter in this industry?
Test any product, and any developer, against these six.
- Skill and certification aware dispatch. Not a calendar with names on it. The board has to respect certifications, service area and what is actually on the van, so a residential technician does not get sent to a commercial variable refrigerant flow job.
- Equipment history per unit at each site. Every machine tracked by model, serial, install date and prior service, so a technician walks in knowing the unit rather than diagnosing it twice.
- Preventive maintenance as an engine, not a recurring calendar entry. Work orders generated per unit at each site on the right schedule, alerts before agreements lapse, and profitability reported per contract so you know which ones are worth renewing.
- Offline that reconciles, not offline that captures. Capturing data with no signal is straightforward. Deciding what happens when a technician who spent the afternoon in a mechanical room reconnects and the office has already edited the same work order is the expensive part, and it is where cheap builds and thin products both fall down.
- Two way accounting sync. One way export is easy. Getting costs to post back and invoices to reconcile without rekeying is where corruption hides. Ask for a specific integration already shipped, named, rather than a category.
- Data ownership and export. Your customer list, equipment history and agreement terms are the asset. Ask any vendor exactly what leaves with you and in what structure.
Run the demo on your own worst Tuesday rather than the sample data: an emergency no cool call at eleven, three technicians already committed, one of them the only person certified on that rooftop unit, and the part on a different van. If the board cannot show you that in one glance, no amount of reporting will make up for it.
What does total cost of ownership look like at your scale?
In Digital Heroes delivery experience, a focused module runs $45,000 to $80,000 and ships in 8 to 12 weeks: dispatch with skill and geography rules, work orders with equipment history, a technician application capturing readings, photos and signatures, and one accounting integration. A full custom platform runs $80,000 to $180,000 over 4 to 7 months, adding true offline synchronisation with conflict handling, the preventive maintenance contract engine, on site quoting and payment capture, van stock and a customer portal. Multi branch builds run $180,000 to $400,000 and upward.
Branch count is the largest driver by a distance, because branch is a dimension through the whole data model rather than a filter on a screen. Who can see what, which warehouse a part came from, which board a job appears on, how a technician shared between locations is scheduled: all of it changes. Shops that land in the top tier are usually there because they acquired somebody, not because they grew into it.
A 28 truck single branch contractor typically lands at $72,000 for a first release and $180,000 across both phases in about seven months. The individual lines worth knowing: the preventive maintenance engine is around $30,000, offline capture is around $12,000 with full conflict handling a further $22,000 in phase two, and discovery is around $11,000. That discovery line is the first thing a procurement conversation tries to remove and the one that decides the outcome.
Then the arithmetic people skip. At 28 trucks plus office seats, $4,500 a month is $54,000 a year and $162,000 over three years, rising with every hire. A $180,000 build plus maintenance at 15 to 20 per cent is roughly $260,000 over the same three years, flat with headcount. On raw cost the packaged product still wins at three years, and the crossover moves closer with every truck you add. Add device replacement, payment processing, mobile platform churn as phone operating systems update annually, and a support arrangement with real hours for the morning the accounting sync fails at six with trucks rolling.
What does the hybrid look like, and when is it the honest answer?
For a lot of shops between 20 and 40 trucks this is the best value option on the table, and it is the one nobody sells you.
Keep the commodity. Accounting stays in QuickBooks or Sage. Payments stay with your processor. Text messaging stays where it is. None of those wins you a job and all of them are fiddly to build.
Build the differentiator, which in HVAC is almost always one of two things. Either the dispatch board that understands certifications, van stock and geography, or the preventive maintenance contract engine that generates work orders per unit and tells you before an agreement lapses. Pick the one that hurts most and ship it in 8 to 12 weeks at $45,000 to $80,000, running alongside the packaged product rather than replacing it.
That shape has a second advantage. It gives you a real answer to the question of whether you can operate your own software before you commit to owning all of it. If the module is adopted and maintained for a year, extend. If it is quietly abandoned, you have learned something for $60,000 rather than $180,000.
The sequencing rule that goes with it: online first mobile in release one, capture offline and sync when back in signal, and defer full conflict handling to phase two once you know which fields technicians actually edit twice. Building that before you have watched real usage means guessing.
Which should you choose, by operator size and stage?
Under 15 trucks. Buy Jobber or Housecall Pro. Do not read further, and do not let anyone sell you a build.
15 to 25 trucks, one branch. Buy, and get serious about configuration. Most of the pain at this size is that nobody owns the setup. Name one person accountable for the pricebook, the agreement records and the dispatch rules before you conclude the tool is wrong.
25 to 40 trucks with a named, priceable misfit. Build the module, not the platform. Dispatch or preventive maintenance, one branch, keeping accounting and payments where they are. Pilot with one crew for two weeks and never cut over every truck on a Monday morning.
Above 40 trucks, or multi branch after an acquisition. The full platform, phased, proving it at your largest branch first and rolling out afterwards. Designing for all branches before any of them runs is how the top of the band gets reached. Say the word second branch during discovery even if it is three years away, because that one sentence changes the data model and retrofitting it later is close to a rebuild.
If you would rather someone argued with your brief than agreed with it, Digital Heroes writes a product requirements document before any code exists, so the scope is fixed and priced rather than discovered later at a day rate. Nothing about that commits you to the build.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- PTC identifies the leading causes of failed first visits as parts unavailability (the single most-cited complaint, named by 51% of field service executives), technicians lacking the required equipment or skills, and insufficient time allocated to the job - making parts logistics and skills-based dispatch the highest-leverage fixes. Source: PTC (2023) →
- Comparesoft reports the field-service industry-average first-time fix rate is about 80%, best-in-class providers reach roughly 90%, scores below 70% put the business at risk, and providers exceeding 70% FTFR saw customer retention around 86%. Source: Comparesoft (2024) →
- The average developer spends more than 17 hours a week dealing with maintenance issues such as debugging and refactoring, and about four of those hours on 'bad code' - waste that equates to nearly $85 billion annually worldwide in opportunity cost. Source: Stripe (2018) →
- The right combination of digital transformation actions can unlock as much as US$1.25 trillion in additional market capitalization across Fortune 500 companies, while the wrong combinations put more than US$1.5 trillion at risk; companies with all three core factors (strategy, aligned technology, and change capability) saw a 5% market-value lift relative to peers. Source: Deloitte (2023) →
Frequently asked questions
Is ServiceTitan or Jobber enough for our shop?
Under 15 to 20 trucks, almost certainly. Jobber and Housecall Pro cover dispatch, work orders and invoicing in weeks at a fraction of any build, and ServiceTitan offers real depth as you get larger.
The build case only appears when a specific constraint is costing money you can name, such as preventive maintenance renewals lapsing in a spreadsheet or a dispatch board that cannot see which technician holds which certification.
What does it actually cost to switch off a packaged product?
The visible cost is data migration, and it is smaller than people expect if you are disciplined: move what is live, archive the rest, and resist the urge to bring five years of closed work orders.
The real cost is parallel running and retraining during the changeover. Pilot one crew for two weeks with the old system still available, then move the rest. Cutting over every truck on the same morning is the failure mode, because eight technicians phone the office at once and the office has no fallback.
What happens if our vendor raises prices or changes the roadmap?
Per seat pricing is the exposure that scales against you, because it rises every time you hire, which is the thing you are trying to do. Model your fees at next year's headcount rather than this year's before signing anything.
Roadmap risk is harder to price. If your competitive position depends on features you have not thought of yet, renting is a reasonable answer. If it depends on a workflow you have been told is not on the roadmap, that is the clearer signal.
How long does an HVAC build take?
Eight to 12 weeks for a focused module, four to seven months for the full platform. Discovery takes three to five weeks and involves riding with a technician and shadowing the dispatcher, which is the phase most likely to be cut and most likely to decide the outcome.
Roll out by piloting one crew for two weeks. The acceptance test is that a dispatcher can run a full day on it, not a feature checklist.
At what point does building beat paying per seat?
The arithmetic turns when monthly fees cross roughly $3,000 to $6,000, which usually arrives past 25 trucks once office seats are counted. At 28 trucks and $4,500 a month you are spending $162,000 over three years and rising, against roughly $260,000 for a $180,000 build plus maintenance that stays flat.
Raw licence cost alone rarely decides it. Price the specific misfit as well, because that is where the difference actually sits.
Can we keep QuickBooks and build only part of the system?
Yes, and between 20 and 40 trucks it is usually the best value option available. Keep accounting, payments and text messaging where they are, and build the dispatch board or the preventive maintenance engine that the packaged product gets wrong for your shop.
It also tests whether you can operate your own software before you commit to owning all of it. A module adopted and maintained for a year earns the right to be extended.
Why does the preventive maintenance engine cost around $30,000?
Because it is not a recurring calendar entry. It generates work orders per unit of equipment at each site on the right schedule, alerts before agreements lapse, and reports profitability per contract so you know which agreements are worth renewing.
A missed visit is a lost renewal, and renewals are the part of an HVAC book that has real value. That is why it is usually the first item in phase two and often the whole reason the build gets funded.
How much does adding a second branch cost later?
More than people expect, because branch is a dimension through the whole model rather than a filter: visibility, warehouse stock, dispatch boards and technicians shared between locations all change.
That is why multi branch builds start at $180,000 rather than extending a single branch system for a small increment. The efficient path is proving the system at your largest branch first, and telling the developer during discovery that a second branch exists in your plans even if it is years away.
What security and compliance does custom field service software need?
The baseline is encryption in transit and at rest, role-based access so a technician sees only their own jobs, remote wipe for lost phones, and audit logs on anything that touches money. Run payments through a processor like Stripe or Square so card data never touches your servers and the heaviest PCI burden stays with them. If your crews serve regulated sites such as healthcare or government facilities, say so in scoping, because access and documentation requirements shape the data model.
How much would it cost to build something like ServiceTitan just for my company?
A true ServiceTitan clone would cost millions and you do not need one, because companies that bring this request to Digital Heroes typically use 20 to 30 percent of its features. Building that slice, shaped to your exact dispatch board and technician day, runs $80,000 to $200,000 depending on offline requirements and integrations. The field service builds that succeed copy a workflow, not a product.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
Is Housecall Pro enough for a growing HVAC or plumbing company, or do we need custom software?
Housecall Pro holds up well to roughly 10 to 20 technicians on standard residential jobs, with its Essentials plan listing around $129 per month for up to five users. The ceiling appears with commercial work: multi-visit projects, progress billing, equipment service history, and inventory are thin, which is when owners start managing the business in exported spreadsheets. Use the spreadsheet count as your signal: three or more recurring workarounds mean the tool no longer fits.
Why do agencies charge for a discovery phase instead of quoting for free?
Because an accurate quote requires real work: mapping your workflows, finding the edge cases, and writing a specification, which typically takes 1 to 3 weeks and costs $2,000 to $10,000 at Digital Heroes depending on system complexity. You leave discovery owning a written spec and a fixed price you can take to any vendor, so the money is not locked into one agency. Free estimates are guesses, and the guess usually becomes your budget overrun six months later.
What does it cost per year to maintain custom field service software?
Budget 15 to 20 percent of the original build cost per year, so $15,000 to $20,000 on a $100,000 platform. That covers hosting, security patches, integration API changes, a monthly block of small improvements, and the iOS and Android updates Apple and Google ship on their own schedule. Skipping it is not a savings; the technician app needs attention every OS cycle or it eventually stops opening on new phones.
Can I get my customer and job history out of ServiceTitan or Jobber if we switch to custom software?
Yes. Jobber and Housecall Pro both provide CSV exports of clients, jobs, and invoices, and ServiceTitan data comes out through its API and report exports, though attachments and full audit history take extra work. Budget 2 to 4 weeks of migration effort inside the project for cleaning, mapping, and verifying records, and run both systems in parallel for at least two billing cycles before cutting over.
Who can build a custom field service management software system?
Digital Heroes builds custom field service management software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other field service management software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Dhruv.
Director of DevOps & Infrastructure · Delhi · 5 posts on the site
Published · Last updated .
