How to build an app like ServiceTitan: field service software breakdown

Most field service companies that come to us about building custom software are not trying to out-engineer ServiceTitan. They are running 30 to 80 technicians, paying $15,000 to $25,000 per year in platform fees, and dealing with two or three workflow problems ServiceTitan cannot solve cleanly -- franchise reporting, niche trade-specific billing, or a white-label requirement for a client who does not want to see a third-party tool in their operations. ServiceTitan's generic model creates real friction at that level.

A custom field service platform costs $80,000-$140,000 to build once. You own it. No per-user fees. No module upsells. No pricing increases each year.

According to IBISWorld's 2024 HVAC Services industry report, the US HVAC industry generates $115 billion in annual revenue across approximately 117,000 businesses. Most run on generic software. Those that invest in custom dispatch and scheduling tools typically see 15-20% improvement in technician utilization.

This guide covers what the build involves: the modules by phase, the business model decisions, the two engineering problems that trip up most first-time builds, and the specific company types where custom makes financial sense.

How ServiceTitan makes money (and what that means when you build your own)

ServiceTitan is a SaaS platform on a per-user, per-module subscription model. Starter runs $398/month for up to 10 users. Essentials is $598/month. The Works plan starts at $1,000+ per month. Enterprise pricing goes to $2,000-$5,000 per month for large operations. Add-on modules -- marketing automation, payroll, financing -- push a 30-technician company to $12,000-$20,000 per year.

ServiceTitan also earns a processing margin on payments through its embedded financing and payment products. Their business model is designed to grow with you: every technician you add, every module you turn on, every payment processed through their system generates more revenue for them.

When you build your own platform, your cost structure inverts. You pay once to build, then carry annual maintenance costs -- typically 15-20% of the build cost per year for bug fixes, security updates, and incremental features. At $120,000 to build and $20,000/year to maintain, a company paying $18,000/year on ServiceTitan reaches break-even at roughly six years. Companies paying $25,000/year break even in under five.

Your monetization options when building your own depend on your business model. If you run a franchise operation, you can charge franchisees a white-label SaaS fee -- $150-$400/month per location is a typical range -- and recover the build cost while giving franchisees a better-integrated tool than any off-the-shelf option. If you build for your own operations, the return is efficiency: fewer dispatch errors, higher technician utilization, and a pricing book that prevents technicians from quoting off-menu.

"Field service operations lose an average of 1.5 hours per technician per day to scheduling inefficiencies and poor software. That is roughly $18,000-$25,000 per technician per year in lost revenue capacity."

-- ServiceMax Field Service Index (Salesforce, 2022)

Who builds this instead of buying ServiceTitan

Four specific types of companies build custom field service platforms. The deciding factor is almost always one of the following: scale, franchise structure, workflow specificity, or a white-label requirement.

HVAC and plumbing companies with 30+ technicians paying over $15,000/year. At this scale, the annual subscription cost funds a meaningful portion of a custom build. The companies we talk to at this level have also accumulated enough operational history to know exactly which ServiceTitan features they use and which ones they are paying for but ignore. That clarity makes scoping a custom build straightforward.

Franchise operators who need consolidated reporting across locations. ServiceTitan does not offer a white-label option. A franchisor who wants their franchisees on a single platform under the franchisor's brand has no off-the-shelf path. Building gives them a platform they can charge for, one that reflects their own operational standards rather than a generic field service workflow.

Niche trade contractors with unusual billing requirements. Pool service companies that bill chemical treatments as recurring line items. Elevator maintenance companies with compliance reporting requirements. Restoration contractors who bill insurance companies under specific claim categories. These workflows require workarounds in ServiceTitan that add up to hours of manual correction each week. Custom gives them the exact billing logic their trade requires.

Companies building a managed services offering. Some operators are not pure field service -- they provide a tech-enabled service layer to facilities managers or commercial clients who want a single platform for all vendors. They need their own platform to present a coherent product, not a rebranded ServiceTitan login.

What to build: V1, V2, and V3

V1 -- launch (14-16 weeks, $80,000-$100,000)

V1 is the minimum to run daily operations without a spreadsheet. Eight modules, two applications (one for the office, one for technicians in the field).

Dispatch board. A visual board showing all open jobs, all technicians, and the day's schedule. Dispatchers drag jobs between technicians. Each job card shows the customer name, address, job type, estimated duration, and current status. This is the operational core -- every other module feeds into it or depends on it. Cross-platform mobile cuts $30,000-$50,000 from the build compared to separate native iOS and Android apps; for a dispatch-focused tool with no heavy rendering demands, cross-platform is the right trade-off.

Job management. Create a job from a phone call or web request. Assign a job type (install, repair, maintenance). Add notes and attach photos from a previous visit. View equipment history for the customer's address.

Technician mobile app. Show assigned jobs for the day. Tap a job to view the customer history. Navigate to the address. Complete a checklist. Take before and after photos. Collect a digital signature. Generate an invoice on-site. The app must work offline -- this is non-negotiable and is the hardest engineering problem in the entire build (more on this below).

Customer history. Full service history per address: equipment installed, warranties, past invoices, previous technicians. Technicians see this before they arrive. It directly affects average ticket size because technicians can see what has not been serviced recently.

Invoicing and payment. Generate an invoice in the field. Accept a credit card. Email the receipt. Sync the transaction to QuickBooks automatically.

Pricing book. Pre-set prices for every service and part. Technicians select from the book rather than entering prices manually. This keeps pricing consistent across the team and protects margin.

Automated reminders. Appointment confirmation when a job is booked. A reminder 24 hours before. A service-due reminder for customers on maintenance agreements. A review request after the job closes. All triggered automatically from job status changes.

Reports. Revenue by technician, job type, and customer source. Conversion rate, average ticket size, job completion rate. This is where owners and managers spend most of their time.

V2 -- growth (add after proving the model, +$20,000-$25,000)

V2 adds the features that matter once you have a working operation and want to grow recurring revenue.

Customer self-booking through a web portal reduces inbound call volume and lets customers book maintenance visits without calling in. Maintenance agreement billing and automatic renewal management converts one-time customers into recurring revenue. Technician performance dashboards with commission calculations give field managers real numbers to manage against.

V3 -- scale (only relevant above $1M ARR or franchise expansion, +$15,000-$20,000)

V3 is for operators who are either growing into a multi-location business or who are building a platform product for franchisees or managed service clients.

Multi-location support with separate job boards, technician rosters, and reporting per location. A customer-facing portal to view history and pay invoices. White-label configuration for franchise operators: custom domain, color scheme, logo, and login branding. API access for clients who need to pull job data into their own systems.

The two problems that break most field service builds

According to Deloitte's 2023 field service management industry report, the global field service management market is projected to reach $5.9 billion by 2027. As the category grows, more operators attempt custom builds -- and most underestimate the same two problems.

Real-time dispatch sync is the first. When a dispatcher reassigns a job on the web app, the technician's mobile app must update within seconds. This requires persistent connections from both the web app and each technician's mobile app, with a server-side event bus coordinating changes. A company with 50 active technicians has 50 simultaneous live connections to manage. Getting this wrong means a technician drives to the wrong address or shows up for a job that was reassigned an hour ago. The teams that budget for this architecture upfront -- roughly 2-3 extra weeks of backend work -- avoid a painful and expensive retrofit six months after launch.

Offline mode for the technician app is the second. Technicians work in basements, attics, rural areas, and equipment rooms with no signal. The app must handle job completion, photos, and invoicing without a connection, then sync all offline activity back to the server when the phone reconnects -- without creating duplicate records or overwriting updates made from the dispatch board while the tech was offline. This sync logic is genuinely difficult. Every offline action needs a timestamp and conflict resolution strategy. Building it correctly from the start takes an extra 3-4 weeks. Retrofitting it after launch takes 6-8 weeks and breaks live functionality while the migration runs.

Most field service apps that fail in the field fail because of offline handling. The failure mode is always the same: the team deprioritizes offline support during V1, ships a connected-only app, and discovers the problem the first week a technician loses signal in a basement and cannot complete the job record.

RaftLabs has built dispatch systems and technician mobile apps for HVAC, plumbing, and electrical businesses. In every build, the offline sync architecture is the decision that separates apps that work in the field from apps that generate support tickets every Tuesday morning.

Build vs. ServiceTitan: when does custom win?

A custom build is not the right answer for every field service company. The decision comes down to scale, workflow specificity, and business model.

Keep using ServiceTitan when:

• You have fewer than 10 technicians. The Starter plan at $398/month is a good deal for a small operation.

• Your pain with ServiceTitan is about price, not capability. Paying $6,000/year and occasionally working around a limitation is cheaper than a $100,000 build.

• You are not ready to maintain a software product long-term. Custom software requires ongoing engineering investment -- budget 15-20% of the build cost per year.

Build your own when:

• You have 20+ technicians paying $15,000+ per year on ServiceTitan and that number will grow with every technician you add.

• You run a franchise or multi-brand operation that needs a white-labeled platform. ServiceTitan does not offer a white-label option.

• Your service workflows are too specific for ServiceTitan -- commercial service with complex billing, government contracts with compliance reporting, niche services with trade-specific requirements that generic field service software forces you to work around constantly.

• Your business model involves selling software access to franchisees or managed service clients. You need your own platform to do that.

At $18,000/year on ServiceTitan, a $120,000 custom build breaks even in roughly six years. At $25,000/year, break-even is under five. Many companies at this level also have a specific capability gap -- something ServiceTitan charges extra for or cannot do at all -- that shifts the calculus further toward building.

How RaftLabs can help

RaftLabs has built dispatch systems, technician mobile apps, and real-time job management platforms for field service businesses. We have solved the offline sync problem. We have built the WebSocket architecture for real-time dispatch. We have done QuickBooks integrations and Stripe payment flows that handle the edge cases that surface in production.

The first step is a 30-minute scoping call. We will ask about your current workflow, which ServiceTitan features you actually use, and the specific problems driving you toward a custom build. We will give you a realistic cost range and timeline before you commit to anything. If ServiceTitan is still the right answer after that conversation, we will say so.

Book the scoping call