The $3.2 Million Problem Nobody Talks About
Here’s an uncomfortable truth about multi-location MEP contractors: the branch your CEO brags about at industry events and the one that keeps your COO up at night are running completely different businesses. Same logo on the trucks. Same name on the building. Entirely different operations.
We analyzed operational data from 200+ multi-location mechanical contractors and found that the performance gap between the best-performing and worst-performing branches within the same company averages 34%. That’s not a rounding error. For a $100M contractor, that gap represents $3.2M in annual margin leakage — money lost to inconsistent processes, tribal knowledge that never transfers, and the operational entropy that comes from letting each branch “do it their way.”
The contractors closing this gap share a common strategy: they’ve consolidated operations onto the operating system for the trades. As Tonya Brooks, COO of Flow Service Partners, puts it:
“With each acquisition, we inherit different tools, workflows, and cultures. To scale, we couldn’t impose uniformity, but we needed consistent visibility. It let us speak a common language. If I talk to the operator at one of our regional offices, we’re looking at the same KPIs, and we can solve problems before they grow.” — Tonya Brooks, COO, Flow Service Partners
Why Standardization Fails (And What to Do Instead)
Most standardization efforts die the same death: headquarters creates a binder of SOPs, distributes it to branch managers, and six months later discovers nobody read it. The failure isn’t in the processes—it’s in the delivery mechanism.
The companies succeeding at multi-location standardization aren’t writing binders. They’re embedding standards directly into their technology workflows. When a technician opens a work order on their mobile device, the process is the software. There’s no separate document to consult. The dispatch logic, the pricing rules, the inspection checklists, the parts ordering workflow—all of it’s codified in the platform.
As Ben McWhorter, Mechanical Manager at Jackson Services, experienced:
“We do a lot of projects that are multi-million dollars which are hard to keep track of with other software. ServiceTitan does a great job where we can do our subcontractors, equipment manufacturers, anything on those projects, we can track and see what we are day to day, from day one to the end of the job.” — Ben McWhorter, Mechanical Manager, Jackson Services
The three-layer standardization model:
Layer 1: Hard Standards (Non-Negotiable)
These are embedded in your technology platform and cannot be bypassed. Examples include pricing rules, safety checklists, billing procedures, and customer communication templates. When a technician in Phoenix follows the same inspection protocol as one in Atlanta—not because they memorized a manual, but because their mobile app walks them through it—you’ve achieved hard standardization.
“Hard standards” are often predicated on whether your organization is more centralized or decentralized. Leila Rookstool, Senior Industry Advisor at ServiceTitan, said, “Coming from a more decentralized background, we never imposed pricing rules or communication templates — but we did have strict accounting controls the organization had to abide by, and that impacted workflows such as 'batch approval' on invoices.”
Layer 2: Soft Standards (Guided Flexibility)
These are recommended practices that allow for regional variation. Branch managers can adjust Dispatch Pro priorities, technician territories, and scheduling buffers based on local conditions, but within guardrails set by the platform. The key is visibility: headquarters sees when and why a branch deviates, rather than discovering it during quarterly reviews. These could also include recommended sales workflows, automated follow-ups — anything an enterprise is sharing as a best practice, the operating company has the opportunity to choose to embrace or not.
Layer 3: Measurement Standards (Universal KPIs)
Every branch measures the same metrics the same way. This sounds obvious, but in practice, Branch A might calculate “technician utilization” as billable hours divided by total hours, while Branch B excludes drive time and Branch C includes training. Without uniform measurement, you can’t benchmark, and without benchmarking, you can’t improve.
The Technology Foundation
Multi-location standardization requires a single operational platform—not five different systems stitched together with spreadsheets. The platform must handle dispatching, job costing, inventory, invoicing, and reporting across all locations with unified data.
ServiceTitan, the #1 platform for the trades, is purpose-built for this. A single instance serves all branches with location-specific configurations (tax rates, pricing, territories) while maintaining standardized workflows, reporting, and customer records. When headquarters pulls a dashboard, they see every branch in real-time—not last month’s numbers reconciled across three different systems. Enterprise Hub centralizes management across every branch, while Titan Intelligence analyzes your data to surface insights that drive decisions.
The results are measurable: contractors switching to ServiceTitan have seen an average 21% revenue increase in their first two years.
What this looks like in practice:
A service call in Denver uses the same diagnostic checklist as one in Dallas
A PM in the Charlotte office can view real-time job cost status on a project in Tampa
The CFO pulls a single WIP report across all locations without waiting for branch controllers to reconcile
Dispatchers at any location can see and route technicians across regions during peak demand
Customer history follows the account, not the branch—so when a national account calls any location, every tech who’s ever touched that building appears in the record
The 90-Day Standardization Sprint
Don’t attempt to standardize everything at once. The companies that succeed follow a phased approach:
Days 1–30: Audit and Baseline. Deploy ServiceTitan across all locations if you haven’t already. Run parallel operations. Measure current state KPIs for every branch using the same definitions. Identify your top-performing branch—they become your template.
Days 31–60: Core Workflow Lock-In. Standardize the three highest-impact workflows first: dispatching logic (powered by Dispatch Pro’s AI-optimized routing), pricing/billing, and safety/inspection checklists. These affect every job. Configure them as hard standards in your platform. Train all teams on the new workflows with the explicit message: this is not optional.
Days 61–90: Visibility and Accountability. Launch standardized dashboards through ServiceTitan’s Reporting & Dashboards with pre-built and customizable analytics. Every branch manager sees the same KPI scorecard every morning. Institute weekly cross-branch performance reviews. Celebrate the branch that improves the most (not the one that was already best).
The #1 newsletter for the trades.
The Payoff
Contractors who complete this standardization process typically see results within one to two quarters: 15–22% improvement in the lowest-performing branches, 8–12% reduction in overhead costs through elimination of redundant systems and processes, and a 25–40% decrease in customer complaint escalations across the organization.
More importantly, standardized operations make your company acquirable, scalable, and resilient. When your best branch manager leaves, the operation doesn’t collapse—because the operation’s in the system, not in someone’s head.
