Revenue per rig, by lane— built for Swift / Crete / Schneider / Werner-scale national carriers.
Predictive intelligence for the long-haul fleet: per-truck SaaS sized to fleet scale, regional certified-mechanic coverage that rolls to the terminal or yard, a real-time alert-to-dispatch workflow, no upfront capex, and the 17% Trodeon success fee settled only on confirmed completed repairs.
What runs under the hood
Three things a multi-yard carrier actually gets.
Consolidated invoicing across yards
Per-truck SaaS lines and 17% success-fee settlements roll up into one monthly invoice per carrier, every yard in the statement of work landed on the same settlement cycle — so AP trails one number across terminals instead of one per yard.
Reads the existing ELD + J1939 telemetry
The forecast goes through the ELD / J1939 feed the carrier already runs on /integrations, and writes alerts back into the TMS dispatch console — no parallel hardware stack to maintain, no new inbox for the dispatcher to triage.
ROI proof on /roi
The avoided-downtime math lives on /roi — per-lane exposure priced against the per-truck tier, with the 17% success fee model in the same view. Useful before a pilot conversation starts, and useful again at sign-off.
Operator vignette
National carrier — Swift-scale
A national carrier runs N+ terminals on a freight schedule the truck revenue plan does not bend to — a Swift-scale lane set, regional pickups timed to intermodal windows, and customer docks the dispatcher has to clear by appointment. The forecast sizes lead time to that lane exposure, so the dispatched mobile tech closes the repair before the rig re-enters revenue service and the missing turn does not turn into a missed delivery commitment.
Across a multi-terminal national fleet the same per-truck line and the same 17% settlement roll up into one monthly invoice under a single statement of work — every yard in the rollout priced against the same tier, settled against the same downtime ledger the carrier ops team already tracks.
Operator vignette
Large private fleet — 500+ rigs
A large private fleet — grocery, retail DC, fuel hauler, food service distribution — runs internal lanes the public carrier market does not see, with revenue-per-rig math tied to the customer it serves. The forecast reads through the existing ELD / J1939 telematics and only trips on a component the fleet would actually take off the lane, so the dispatch console gets an alert the fleet manager can action against the freight schedule.
A 500+ rig private fleet lands at the Enterprise tier and bills on one monthly invoice against the budget cycle the fleet finance team is already running on — single procurement statement, single settlement, single downtime read.
Per-truck tiers
The right tier lives one click away.
A 500+ Class 8 national carrier lands at Enterprise · $98.10per truck · per month. Regional and smaller carrier-scale rollouts land below. The full per-truck math runs at /pricing.
1–9 trucks
Solo Fleet
Single-yard operators getting Trodeon online with per-truck thresholds, mechanic dispatch, and a downtime ledger you can audit every month.
See pricing →$189
per truck · per month
10–49 trucks
Regional Operator
Multi-yard rollouts with shared dashboards, pooled dispatch coverage, and quarterly ops reviews against your revenue-per-truck-hour baseline.
See pricing →$109
per truck · per month
50+ trucks
Enterprise
Carrier-scale rollouts with CvRP-aware integrations, dedicated dispatch pods, and right-to-repair audit posture. 10% off the Regional rate.
See pricing →$98.10
per truck · per month
The same 17% success fee sits underneath every tier, settled only on confirmed repairs. The full per-truck math runs at /pricing.
Telemetry → dispatched tech
From a sensor reading to a wrench on the rig.
The path the forecast runs — from the moment Trodeon (or the existing telematics feed on /integrations) flags a component anomaly, to the moment the dispatched tech closes the work order. The mobile mechanic network that closes the loop is open to carrier terminals and is browsable at /mechanics.
1. Component anomaly surfaces
A Trodeon sensor — or the existing ELD / J1939 feed on /integrations — flags a degradation curve on a single rig.
2. Forecast lead time assigned
The model assigns a component-specific lead time — hours to days — sized to the failure mode and the carrier’s lane schedule.
3. Dispatch console pages the tech
The dispatcher sees the alert with the lead time, the lane the rig is on, and the parts the mobile tech should arrive with.
4. Certified tech rolls to the rig
A certified tech from the regional dispatch network rolls to the rig — terminal, yard, customer dock, or roadside — parts-loaded for the predicted job.
5. Repair confirmed, fee settled
The tech closes the work order against the forecast; Trodeon settles the 17% success fee only on this confirmed completion.
Buying-committee research
Two analysts. Two starting points.
The procurement analyst opens at /integrations — how Trodeon reads the existing ELD / J1939 telematics feed, what the OEM and right-to-repair posture looks like, and which procurement vehicles a multi-yard rollout can ship against.
The operations analyst opens at /roi — what an avoided breakdown is worth against the per-truck tier and where the 17% success fee sits inside the budget cycle the carrier is already running on.
Procurement fit
No upfront capex. A 17% fee, settled only on outcomes.
Carrier procurement doesn’t have to commit capex to stand Trodeon up. Per-truck SaaS runs at the tier your fleet size lands in — $189, $109, or $98.10 per truck per month — and the same 17% success fee sits underneath every tier, settled only on completed repairs dispatched through Trodeon.
Scope a defined-window pilot against a single terminal first — the success fee math doesn’t kick in until the pilot closes and the per-truck tier is in place. The pilot agreement spills out into a multi-yard statement of work with a single settlement across yards, so AP trails one number against the budget cycle the carrier is already running on.
Run a defined-window pilot
Stand Trodeon up across your yards — before any per-truck commitment.
A real-rig pilot, bounded by start and end dates, with the 17% success-fee settlement documented up front. Operations can trail it against a current rig on the lane; procurement gets the per-truck tier and the settlement ledger before any roll-out decision.
Or research-first: /integrations for telematics and procurement systems questions, and /roi for the avoided-downtime math.