For multi-branch plumbing operators who've outgrown ServiceTitan or Housecall Pro, where emergency dispatch, parts-on-truck, and multi-license, multi-permit work don't fit a packaged product.
Off-the-shelf tools assume a scheduled, single-license, parts-from-the-warehouse job. Plumbing breaks all three, these are the four pressure points where multi-branch operators get stuck.
A burst line doesn't wait for the next open slot. You're constantly re-sequencing by severity, proximity, and who's licensed, and packaged tools that assume a booked calendar fight you on every reassignment.
Whether the tech has the right fitting decides whether the job closes today or rolls to a second truck-roll tomorrow. If parts-on-truck lives in someone's head, you over-stock every van or eat return trips.
Multi-license techs, multi-jurisdiction permits, and inspection sign-offs are real constraints on dispatch, not metadata. Software that can't reason about them sends the wrong tech or ships work that fails inspection.
Work orders in one tool, invoicing in QuickBooks, warranty and permit records in a third, none agreeing. Every dispute or callback becomes a manual hunt, and the back office absorbs the cost.
Solved by software built around how your shop runs: emergency-first dispatch, parts-on-truck intelligence, license- and permit-aware scheduling, one connected back office.
A board that re-sequences by severity, proximity, and license, built to reassign on the fly, not defend a fixed calendar.
Per-truck inventory tracked in real time, restock flags before a van runs dry, and first-trip-fix rates you can actually see.
Multi-license techs and multi-jurisdiction permits modeled as real dispatch constraints, with inspection sign-offs tracked to the job.
Mobile-first and offline-capable, work orders, parts, photos, and customer sign-off that sync when the signal comes back.
One-way QuickBooks sync with retries and logging, plus warranty and permit records tied to the work order, not a third system.
You own the code, the architecture, and the pipeline. No per-seat escalation, no vendor lock-in, no roadmap you don't control.
We ride along with your dispatchers and best techs. Map the emergency flow, the parts reality, and the license and permit constraints, then set the feature scope.
A small senior team, 4 to 8 engineers, US review on every PR, weekly demos. You see the dispatch board work against real jobs, not a status report.
Ship behind a flag, pilot one branch or dispatcher, roll wider when ready. You own the codebase at the end, most operators keep us for phase 2.
A bounded feature (emergency dispatch, a parts module, a permit tracker) ships to production in 6 to 10 weeks. A full operator platform (dispatch + technician interface + back-office) runs 4 to 8 months from kickoff. We ship incrementally; you don't wait months for the first visible thing.
Across Utah, Orange County, and Arizona, One Home Solution runs HVAC, plumbing, electrical, and general repairs on one platform. We shipped a client app, a technician field interface, a back-office dashboard, and an AI pricing engine, with plumbing's emergency dispatch and parts reality handled as a first-class trade, not a checkbox bolted onto an HVAC tool.
Packaged FSM SaaS works well for the operator-shape it was designed for, usually a single-trade, single-location shop on a booked calendar. Plumbing at multi-branch scale breaks those assumptions: emergency-first dispatch, parts-on-truck economics, and multi-license, multi-permit work. Custom is worth it when configuring around those limits costs more than a build, when renewal pricing climbs make you want to own the code, or when the constraint you need modeled simply isn't in the packaged product.
We model the board as a live triage queue, not a fixed calendar. Jobs re-sequence by severity, proximity, and which techs are licensed, and reassignment is a first-class action rather than something the tool resists. The dispatch spine comes from real field-ops work (the ArcGIS routing and offline-first mobile we built for Ocore), so it's a proven foundation, not a from-scratch experiment.
Yes, per-truck inventory is core scope. We track parts at the van level in real time, flag restocks before a truck runs dry, and surface first-trip-fix rates so you can see where return trips leak margin. The goal is to stop choosing between over-stocking every van and eating second truck-rolls.
Yes. Multi-license techs and multi-jurisdiction permits are modeled as real dispatch constraints, the board won't send an unlicensed tech to work that requires the license, and permits and inspection sign-offs are tracked to the job rather than a separate system. How strict the enforcement is gets scoped with your compliance lead in Week 1.
You do. Code, architecture, deployment pipeline, and documentation are all yours at the end, with no vendor lock-in. We can stay on for support and extension, most operators keep us for phase 2, but the IP is yours from day one.
The parent FSM practice: dispatch, technician mobile, and back-office for multi-branch operators and FSM SaaS vendors.
For multi-branch HVAC operators with maintenance-contract lifecycles and warranty-portal integrations.
Routing, dispatch, and real-time visibility for 3PL, last-mile, and fleet operators.
The parent practice: senior US-contracted teams building custom platforms across verticals.
A 15-minute operator-to-engineer call. No deck, no pitch. You tell us where the dispatch board and the parts reality hurt most; we tell you whether a custom build is the right move, and if it isn't, we'll say so.