The infrastructure, by the trade you actually run.
Three documented blueprints. Each one describes the specific operating apparatus we install inside a $2M–$10M operation in that vertical — the signals that tell you it is needed, the modules themselves, the measurement frame, and the install window.
Seasonal Revenue Smoothing Engine Converts peak-season windfall into year-round operating stability.
HVAC revenue is structurally binary: Q2 and Q3 print cash, Q1 and Q4 consume it. The $2M–$10M shop running on seasonal volume has no revenue floor — it has a revenue cliff. Two bad Januarys in a row and the owner is bridging payroll out of a home equity line. The Smoothing Engine installs the attach infrastructure, membership logic, and IAQ upsell cadence that converts one-time repair and replacement tickets into recurring agreement revenue, so the shoulder season has a base load before the first cold snap arrives.
Diagnostic signals
- SIG.01Q1 revenue runs 40% or more below Q3 peak, and the gap has widened year-over-year.
- SIG.02Maintenance agreement penetration is below 15% of your active customer base.
- SIG.03IAQ and accessory attach rate on new-install tickets is under 20%, measured at point-of-sale.
- SIG.04You have run a seasonal promotion at least twice in the past three years and cannot show a measurable lift in agreement conversion rate from either campaign.
The install
-
MOD.01
Maintenance Agreement Conversion Layer
A scripted, field-executed offer protocol at every tune-up, repair, and new-install ticket so that the conversion pitch is delivered consistently by every tech — not improvised, not skipped when the call runs long.
-
MOD.02
Shoulder-Season Attach Engine
Maps your existing customer database against agreement status, equipment age, and IAQ exposure, then builds a prioritized outbound cadence timed to the six-week window before each shoulder season begins — not after it's already losing revenue.
-
MOD.03
IAQ & Preventive Replacement Trigger Logic
Embeds equipment-age and IAQ-reading thresholds into the dispatch and CRM workflow so techs are surfaced a replacement or accessory recommendation at the right call — defined by system data, not by whether the tech remembered to ask.
Dispatch Density Node Eliminates drive-time drag and rebuilds billable-hour yield per tech.
Plumbing margin doesn't die on the job — it dies in the truck. The dispatcher who improvises call order at 5am, the two-hour gap between a Northside callback and the next ticket three zip codes south, the apprentice who shadows a master all day and bills at half the rate because the routing logic never separated their work: these are structural revenue leaks, not scheduling accidents. The Dispatch Density Node installs geo-clustered zone logic, ticket prioritization rules, and tech-tier routing so that the windshield time eating 2–3 billable hours per tech per day gets converted back into revenue.
Diagnostic signals
- SIG.01Average drive time between jobs exceeds 25 minutes, calculated across your last 90 days of completed tickets.
- SIG.02Tech utilization — billable hours divided by hours clocked — runs below 65% on a rolling monthly basis.
- SIG.03Callback rate (return visits within 30 days on the same ticket issue) is above 8% of completed jobs.
- SIG.04Dispatcher makes routing decisions in real time, without a zone map or call-order protocol, and the system breaks down entirely when that dispatcher is unavailable.
The install
-
MOD.01
Geo-Cluster Zone Architecture
Divides your service territory into defined dispatch zones calibrated to actual call density and drive-time data, then assigns each tech a primary zone so that the default routing decision is already made before the dispatcher picks up the phone.
-
MOD.02
Ticket Prioritization & Call-Order Logic
A decision framework that ranks open tickets by urgency tier, proximity, tech skill level, and estimated job duration — so the dispatcher is executing a ranked queue, not building one from scratch on a whiteboard every morning.
-
MOD.03
Tech-Tier Utilization Routing
Separates master-level and apprentice-level work in the dispatch queue so apprentices run appropriate solo tickets rather than shadowing all day, and masters are routed to complexity-matched calls that bill at the rate their labor cost justifies.
Fleet Optimization Node Converts each vehicle into a tracked P&L and surfaces dead weight in the fleet.
Every operator knows what their trucks cost. Almost none of them know what each truck earns per day. When revenue is tracked at the company level and costs are tracked at the vehicle level, the fleet looks like a cost center — because that's the only dimension being measured. The Fleet Optimization Node installs per-vehicle revenue attribution, utilization scoring, fuel-per-billable-hour tracking, and maintenance cadence logic so each truck has a daily P&L the operator can read, and underperforming assets are visible before they become disposal problems or insurance claims.
Diagnostic signals
- SIG.01You can report total fleet operating cost for the prior year but cannot report revenue-per-truck-day for any individual vehicle in that same period.
- SIG.02Fleet utilization — revenue-generating hours divided by available truck-hours — runs below 70%, or you have no current measurement of it.
- SIG.03At least one vehicle in the fleet has a fuel-cost-to-revenue ratio that hasn't been individually calculated in the last 12 months.
- SIG.04Maintenance scheduling is reactive: trucks go into the shop when they break or when a driver reports a problem, not on a mileage- and utilization-indexed cadence.
The install
-
MOD.01
Per-Truck P&L Layer
A vehicle-level revenue attribution and cost-allocation structure inside your existing dispatch and accounting stack so that each truck produces a daily and monthly P&L the operator can read without running a manual export.
-
MOD.02
Utilization & Deadhead Scoring System
Utilization scoring per vehicle — tracking revenue hours, idle hours, and deadhead miles — surfaces the bottom quartile of the fleet weekly so underutilized assets are identified and redeployed, sold, or reassigned before they continue compounding losses.
-
MOD.03
Predictive Maintenance Cadence Engine
Replaces reactive shop scheduling with a mileage- and utilization-indexed maintenance cadence per vehicle, reducing unplanned downtime and giving the operator a 30-, 60-, and 90-day maintenance cost forecast rather than a surprise repair invoice.
Your trade not listed? The installation logic is trade-agnostic. Roofing, electrical, landscaping, restoration — the blueprints follow the same physics: eliminate owner-dependency, convert variable revenue into recurring, make every asset a measured P&L. Run the diagnostic and we will tell you which blueprint your operation most closely resembles.
Run the diagnostic