Home services software development: build vs. buy for HVAC, plumbing, and electrical operators

You run a 45-technician plumbing company. You pay ServiceTitan $2,400 a month - $28,800 a year. You also pay extra for the marketing module, the payroll add-on, and the financing integration. Your two franchise locations cannot share a single reporting view. Your commercial clients want invoices tied to their purchase order numbers, and ServiceTitan gives you one billing template. Three technicians lost job records last month working in commercial buildings with no signal. You have been asking ServiceTitan support about the franchise reporting gap for six months and each call ends with "we're working on it."

This is the moment most HVAC, plumbing, and electrical operators call us about custom home services software development. Not because the off-the-shelf platform is broken. Because they have grown past what it was designed to handle.

Custom home services software development costs $85,000-$150,000 to build once. You own it. No per-seat increases every year. No module upsells. No billing logic you have to work around every week.

According to IBISWorld's 2024 HVAC Services industry report, the US HVAC services market generates $115 billion in annual revenue across approximately 117,000 businesses. Nearly all of them run on the same four platforms. When your workflows outgrow those platforms, you pay for software that fights you every week.

This guide covers who actually builds custom home services software, what each phase includes, where off-the-shelf tools hit hard walls, and where these projects fail.

Clone scripts vs. custom build

Before you plan a build, it is worth knowing what already exists.

Workiz is a white-label field service platform aimed at small residential contractors. You can run it under your own domain with limited brand customization. Monthly costs start around $225 for 5 users and scale with seats. At 30+ technicians, you are paying $1,000-$2,000 a month for a platform you cannot fully configure, cannot sell access to, and cannot extend with custom billing logic. Franchise-level reporting does not exist. The moment a second location goes live, you are back to consolidating spreadsheets.

ServiceFusion offers a white-label reseller program for software companies that want to bundle field service tools under their own brand. It is not designed for operators - it is designed for ISVs. If you are a plumbing franchise trying to give franchisees access to your branded platform, ServiceFusion's reseller terms are restrictive, the UI stays recognizable to anyone who has used it before, and you cannot modify the core billing model.

Off-the-shelf SaaS clone scripts (PHP/React field service templates sold on Codecanyon and similar marketplaces) exist at the $300-$1,500 price point. They cover basic job creation and technician assignment. They fall apart at offline sync, real-time dispatch, multi-location billing, and anything involving commercial PO-based invoicing. You will spend 6-12 months patching a codebase that was never designed for production at your scale.

The common failure point across all three options is the same: they were built for a broad market, not your trade and not your franchise structure. At 30+ technicians with multi-location operations, you are spending staff time every week working around limitations they cannot remove.

Who actually builds an app like ServiceTitan

Not every contractor needs custom home services software. The operators who build share one of four clear characteristics. If none of these describe your situation, the off-the-shelf options are probably the right answer today.

HVAC franchise operators with 3+ locations. A regional HVAC franchisor running three to eight locations needs consolidated job revenue, technician utilization, and customer retention across all locations in one view. ServiceTitan charges per location and lacks a native multi-location hierarchy with consolidated P&L. The only path to a unified franchise view is building it - or spending $40,000+ a year on enterprise licensing for something that still does not match your reporting needs. Operators who build also charge franchisees a platform fee, often $150-$400 a month per location. That fee recovers the build cost in 3-4 years.

Electrical contractors with commercial clients. Commercial electrical clients - property management companies, hospitals, general contractors - require invoices in their format, purchase orders tied to their ERP, and compliance documentation attached to each job record. ServiceTitan and FieldEdge were built for residential billing. Adapting them to commercial PO-based billing with attached safety certifications means exporting data and processing it by hand. A custom platform builds the exact billing logic your contracts require.

Plumbing companies with specialty billing. Pool service companies billing chemical treatments as recurring consumable line items. Restoration contractors billing against insurance claim numbers with photo evidence packages per job. Backflow testing companies filing compliance certificates per device per address. These are not edge cases - they are standard practice in specialty trades. Generic platforms treat them as workarounds. Custom software treats them as the primary data model.

Operators building a managed services offering. Some contractors have moved up the value chain. They provide a tech-managed service layer to commercial facilities managers who want one platform for all vendors - HVAC, plumbing, electrical, cleaning - under the operator's brand. These businesses cannot white-label ServiceTitan. They need their own platform to present a coherent product to clients. The software becomes part of what they sell.

V1, V2, and V3 features - with cost per phase

V1 - launch (16-18 weeks, $85,000-$105,000)

V1 is the minimum you need to run daily operations without a spreadsheet or a platform fighting your workflow.

Dispatch board. A visual board showing all open jobs, all technicians, and the day's schedule. Dispatchers drag jobs between time slots and technician rows. Each job card shows customer name, address, job type, estimated duration, and current status. Cross-platform mobile (one codebase for iOS and Android) saves $30,000-$50,000 compared to native builds. For a dispatch tool without heavy graphics rendering, the tradeoff is worth it.

Job management. Create a job from an inbound call, a web form, or a service-due trigger. Assign a job type. Add notes. Attach photos from a previous visit. View the full equipment history for the customer's address before the technician arrives.

Technician mobile app with offline mode. Show the day's assigned jobs. Navigate to the address. Run through a job checklist. Take before-and-after photos. Collect a digital signature. Generate and send an invoice. The app must complete every one of these steps with no signal. This is the hardest engineering problem in the build - covered in the failure section below.

Customer history. Full service history per address: what equipment is installed, warranty dates, past invoices, which technicians have been there, and what was recommended but not completed. Technicians who see this before a visit sell more. Average ticket size goes up when the tech knows the water heater is seven years old before walking in the door.

Invoicing and payment. Generate an invoice on-site. Accept a card payment. Email the receipt. Sync the transaction to QuickBooks. This loop - job closed, invoice sent, payment collected, accounts updated - is the financial heartbeat of the business.

Pricing book. Pre-set prices for every service, part, and labor rate. Technicians select from the book instead of quoting from memory. Pricing stays consistent across 45 technicians. Margin holds.

Automated reminders. Appointment confirmation when a job is booked. A reminder 24 hours before. A service-due notice for customers on maintenance plans. A review request once the job closes. All triggered automatically from job status changes, with no dispatcher action required.

Reports. Revenue by technician, job type, and customer source. Average ticket size, conversion rate, job completion rate, and call-to-close time. This is where owners and operations managers spend an hour every morning.

V2 - growth (+5-7 weeks, $110,000-$130,000 total)

V2 adds features that matter once the core operation runs on the custom platform and you want to grow recurring revenue.

Customer self-booking through a web portal cuts inbound call volume by 20-30% for companies with established customers. Maintenance agreement billing with automatic renewal management converts one-time customers to recurring contracts. Technician performance dashboards with commission calculations give field managers real numbers to manage against rather than gut feel.

V3 - scale (+5-6 weeks, $130,000-$150,000 total)

V3 is for operators growing into multi-location operations or building a platform product for franchisees.

Separate job boards, technician rosters, and P&L reporting per location. Consolidated franchise-level reporting across all locations with per-location drill-down. White-label configuration: custom domain, brand colors, logo, and login screen per franchisee. API access for commercial clients who need to pull job data into their own facilities management systems.

Where projects fail

Two problems kill home services software builds at a rate far higher than any other technical risk. Both are predictable. Both are expensive to fix after launch.

Offline mode skipped in V1. Technicians work in basements, attics, commercial plant rooms, and rural properties with no signal. The app must complete a job without a connection: run through the checklist, capture photos, record the signature, generate the invoice, and accept a card payment. When the phone regains signal, every offline action must sync back to the server without creating duplicate records or overwriting updates made from the dispatch board while the tech was offline.

This sync logic is genuinely complex. Every offline action needs a timestamp, a device identifier, and a conflict resolution rule. Building it correctly takes 3-4 extra weeks in V1. Retrofitting it after launch - after you have live data, live technicians, and a dispatch board in production - takes 6-8 weeks and breaks active operations during the migration. Every team that skips offline mode to hit a launch date pays for it within 60 days of going live. The failure is always the same: the first technician loses signal in a basement on day three and cannot close the job record.

"Field service operations lose an average of 1.5 hours per technician per day to scheduling inefficiencies and poor software fit - roughly $18,000-$25,000 per technician per year in lost revenue capacity." - ServiceMax Field Service Index (Salesforce, 2022)

Real-time dispatch sync without a recovery strategy. When a dispatcher reassigns a job on the web app, the technician's mobile app must show the update within seconds. At 45 active technicians, you have 45 simultaneous live connections to the server. This is manageable with the right architecture - persistent server connections, a message queue, and a reconnect strategy that replays missed updates after a dropped connection.

The failure is not the sync itself. It is the missing recovery strategy. When a technician's phone drops the connection and reconnects, what does the app show? If the answer is "whatever was last synced before disconnect," you have technicians driving to addresses that were reassigned while they were offline. Teams that budget 2-3 extra weeks for reconnect logic and event replay in the backend avoid a painful fix six months into production.

According to the Technology Services Industry Association's 2023 Field Service Management Benchmark Report, companies with 50+ technicians using purpose-built or custom platforms report 23% higher first-time fix rates than those on generic software. That gap comes from software that matches your workflow - not software you adapt your workflow to fit.

How RaftLabs builds home services software

RaftLabs has built dispatch systems, technician mobile apps, and multi-location job management platforms for HVAC, plumbing, and electrical businesses. We have solved the offline sync problem in production - not in theory. We have built the WebSocket architecture for real-time dispatch at 50+ concurrent connections. We have built QuickBooks and Stripe integrations that handle the edge cases that surface in live operations: partial payments, refunded jobs, split invoices, and duplicate sync prevention.

We start with a 30-minute scoping call. We will ask which ServiceTitan, Housecall Pro, Jobber, or FieldEdge features you actually use, what your monthly platform cost is, and the three workflow problems that generate the most manual work each week. We will give you a realistic cost range and timeline before you commit to anything. If the off-the-shelf option is still the right answer at your current scale, we will tell you that too.

If you are paying $20,000+ a year for a platform that cannot handle your franchise billing, cannot white-label your brand, or forces technicians to work around an offline limitation - a 30-minute scoping call is worth the time.

Book the scoping call