Custom hvac software development pays off when one workflow your generic tool handles badly is costing you money. That workflow is usually quoting, maintenance agreements or dispatch. Build that piece first and keep payments with a processor. For a focused first release, plan on 4 to 7 months and roughly $80K to $200K.
Most shops we talk to run 10 to 60 trucks on ServiceTitan, Housecall Pro or Jobber. The tool still works. The problem is the workarounds: spreadsheets for agreements, a second app for financing, and techs re-keying model numbers from the data plate.
Five features a home services app must get right
1. Good-better-best quoting on site
The quote is where revenue is made or lost. Techs need to build three options from a price book in under five minutes, attach photos and capture a signature on the tablet. Show a monthly financing amount next to each option, because it often changes which tier the customer picks.
Price book sync is the hard part. Supplier costs move often, so the app needs a markup rule per category, not hand-edited prices.
2. Dispatch built around skills and zones
A dispatch board must know who is qualified for what. A tech without the right EPA 608 certification should never land on a refrigerant job. Add drive-time estimates from Google Maps Platform and an automatic "on my way" text, and fewer customers call the office asking where the tech is.
3. An offline-first technician app
Basements, crawl spaces and rural routes kill signal. The mobile app must store the day's jobs, price book and forms on the device, then sync when it reconnects. We use a local database such as SQLite with a queued sync, and we agree conflict rules up front: the office wins on schedule changes, the tech wins on job notes.
4. Payments and financing at the door
Collecting before the truck leaves cuts receivables. The tech needs tap-to-pay on their phone, card-on-file for agreements, and a financing application the customer completes on their own phone. Commercial accounts need ACH and net-30 invoicing instead.
5. Service agreements with equipment history
Maintenance memberships are recurring revenue and the main reason shops outgrow generic tools. The app should auto-schedule spring and fall visits, bill monthly or yearly, and apply member pricing. Tie each agreement to the equipment at the address: make, model, serial, refrigerant type, install date and warranty status.
If you want to scope this with someone who already knows a tune-up from a call-back, you can talk to an engineer who has built in your industry.
Regulations that change the build
None of these rules are exotic, but each one shapes a data model or a screen. Put them in the backlog in week one, not week twelve.
EPA Section 608 refrigerant rules
Under EPA Section 608, technicians who service equipment that can release refrigerant must be certified. Larger appliances carry leak-rate and repair recordkeeping duties. So store certification type and number per tech, and log refrigerant added or recovered per job, by pound and type.
These rules are changing. EPA rules under the AIM Act are extending leak repair duties to more HFC equipment, and new residential systems are moving to lower-GWP refrigerants such as R-454B and R-32. Make refrigerant a lookup table, not a hard-coded list, and check current thresholds before you design the reports.
PCI DSS for card payments
Any system that stores, processes or transmits card numbers falls under PCI DSS. The cheapest way to comply is to never see the card number. Use a processor's hosted fields and readers, such as Stripe Terminal, so raw card data never reaches your servers.
TCPA for texts and calls
Appointment reminders and "on my way" texts generally need consent captured at booking. Marketing texts, such as tune-up promotions, need prior express written consent under the TCPA. Store consent per phone number with a timestamp and source, and honor STOP replies automatically.
Licensing, permits and backflow reports
Most states license HVAC and plumbing contractors, and many cities require permits for equipment changeouts. Plumbers who test backflow devices usually file test reports with the local water utility. Track license expiry per tech, and attach permit numbers and test results to the job record.
Consumer financing
If you offer financing through a lender, the lender usually handles the lending disclosures. Financing in-house turns you into a regulated lender, so talk to counsel before you go there. Most shops should integrate a lender rather than become one.
Integrations you will almost certainly need
- Accounting: QuickBooks Online or Xero, synced at invoice and payment level. Owners notice this one first when it breaks.
- Payments: Stripe, Adyen or your current processor, including card readers or tap-to-pay.
- Financing: a consumer lender such as Wisetack, Synchrony or GreenSky, through its partner program.
- Messaging: Twilio or similar for SMS and masked calls, plus call tracking for marketing attribution.
- Maps: Google Maps Platform for geocoding addresses and estimating drive times.
- Supplier catalogs: price files from your distributors, often CSV rather than a clean API.
- Your current field service tool: during migration, to pull customers, sites, equipment and agreement history.
Budget roughly 15 to 25 percent of build time for integrations. Supplier price files are usually the messiest, because each distributor formats them differently.
What hvac software development costs and how long it takes
These are typical ranges for projects of this shape. Your number depends on scope, the number of integrations, and how messy your existing data is.
Focused add-on: $40K to $90K, 2 to 4 months
One workflow that sits beside your current tool, such as a quoting app or an agreements portal. It syncs through the existing platform's API. It is the lowest-risk option, but you are limited to what that API exposes.
Core field app: $80K to $200K, 4 to 7 months
A technician app, dispatch board, quoting, payments and agreements, with accounting sync. This replaces the generic tool for most daily work. We typically ship iOS and Android from one codebase using Flutter or React Native.
Full platform: $250K to $600K, 9 to 15 months
Everything above, plus a customer portal, multi-branch reporting, truck inventory and commercial billing. This usually makes sense at 50 or more trucks or several locations. Plan another 15 to 20 percent of build cost per year for maintenance and updates.
Run the math against what you pay today. Add up per-tech fees, add-on modules and payment markup over three to five years before you decide.
Three mistakes first-time buyers make
Rebuilding everything the generic tool already does
Mature field service platforms have years of features behind them. Copying all of them is slow and expensive. Replace the part that costs you money, and keep the rest until the new system earns its place.
Designing for the office, not the truck
Screens get approved on a desktop monitor, then fail in a sunlit driveway with gloves on. Test on a mid-range Android phone, in full sun, with no signal. Use big tap targets, minimal typing, and photo capture instead of free text.
Treating data migration as a weekend task
Years of customers, addresses, equipment and agreement terms live in your current tool. Exports are often incomplete, and duplicate customers are common. Plan two to four weeks for migration, with a trial run and a short parallel period before cutover.
Two questions to ask any agency
How does your app handle a tech with no signal all day?
You want specifics: local storage, a sync queue and named conflict rules. If the answer is "it caches the screen", expect lost job notes and photos in the field.
Which parts would you not build?
A good agency pushes some work back to vendors: payments to a processor, financing to a lender, accounting to QuickBooks. An agency that wants to build everything is pricing for its revenue, not your outcome.
FAQ
How much does it cost to build custom HVAC software?
A focused add-on typically costs $40K to $90K. A field app that replaces your generic tool for daily work typically runs $80K to $200K, and a full multi-branch platform $250K to $600K. Add 15 to 20 percent a year for maintenance.
Should I build custom software or stay on ServiceTitan or Housecall Pro?
Stay if your workarounds are minor and the fees are manageable. Build when a specific workflow, such as agreements, quoting or commercial billing, costs you revenue every week. Many shops start with an add-on that connects to their current tool.
Does a field service app need to work offline?
Yes. Techs lose signal in basements, attics and rural areas every day. The app should save jobs, forms and photos on the device and sync later, and card payments need a reader or processor that supports offline mode.



