Building vs. Buying Field Service Software: A Contractor's Guide
The classic advice was: never build your own field service software. It's a solved problem, vendors are everywhere, and a small contractor has no business writing code. That advice was right in 2018. It is no longer right in 2026, and the change is so recent that most contractors haven't caught up.
Here's the honest framework for deciding which side of the line your shop sits on.
What changed
Three things shifted in the last 18 months that flipped the math:
- AI-accelerated development cut build time by 60-80%. What used to take a team six months now ships in 4-6 weeks. Cost dropped from $150k+ to $20-35k.
- Modern hosting platforms (Vercel, Convex, Supabase) eliminated infrastructure complexity. You don't need a server admin. Hosting costs $50-100/month for a shop your size.
- SaaS pricing kept climbing. ServiceTitan, Housecall Pro, FieldEdge all raised prices double-digits in 2024-2025 while reducing what's included at lower tiers.
Together, these mean a custom build now pays back in 12-18 months for a 3+ truck shop. That used to take a decade.
When to buy (still)
You should buy SaaS if:
- You're a solo operator or two-truck shop with simple service work
- You have no specialized workflows your CRM has to support (no permits, no maintenance contracts, no install phases)
- You actively want to use the vendor's marketplace ecosystem (reviews, payments, financing add-ons)
- You'd rather pay $79/mo forever than $25k once
For these shops, Housecall Pro Starter or Jobber Core is a legitimate forever-home. You won't outgrow them, and the savings from building custom don't justify the project effort.
When to build
Build custom if:
- You're running 3+ trucks and your monthly software bill is over $400
- Your trade has specificity the off-the-shelf doesn't capture (permits, equipment specs, install phases, maintenance contracts, compliance reporting)
- You've outgrown one CRM and are dreading the migration cost of switching to the next one
- You want software that fits the way you run, not the way a SaaS company assumes you should
- You're tired of being told "that's a feature on our roadmap"
The biggest mental block is "we're not a software company." That's true. But you're not the one building the software — you're the one commissioning it. Same way you'd commission a custom truck buildout or a shop layout. You design what you need, the specialist builds it.
The risk you should actually worry about
The real risk isn't "what if the developer disappears" (the code is yours — another developer can pick it up). The real risk is scope creep. You start with "just a dispatch tool" and six months later you're trying to build an ERP.
Mitigation: ship a focused v1 in 4-6 weeks. Use it. Find the gaps in real work. Then commission v2 with knowledge instead of speculation. This is how every CRM you've ever liked actually got built.
The decision tree
- Annual revenue under $500k? Stay on SaaS. You'll get a better ROI buying ads than building software.
- $500k-$2M, simple workflows? SaaS still fine, but start watching your monthly bill. If it crosses $500/month, the math flips.
- $1M+, specialized workflows? Build. The custom CRM pays back inside two years and saves you forever after.
- $3M+? You should have built two years ago. Do it now before you sign another ServiceTitan multi-year.
What a build actually looks like
For our home service custom builds, the typical engagement:
- Week 1: Ride-along + working session with your office. Map the real workflow.
- Weeks 2-4: Build core: customers, jobs, dispatch, mobile app, invoicing.
- Week 5: You start running real work in it. We watch where it breaks.
- Week 6: Refinements, integrations (QuickBooks, supplier, SMS), training.
- Week 7+: You're off SaaS. We're on retainer for change orders.
Want to see the specifics for your trade? Read the Custom CRM overview or jump to the trade-specific build for electricians, plumbers, or HVAC.