// industries · heavy civil
Your fleet's real status lives in superintendents' heads. Put it in a system.
The Mad Botter deploys and operates one platform inside your compliance boundary — deterministic capture at the edge, a sovereign data layer, and pipelines on top. For heavy civil that means projects, equipment availability, field information, production windows, costs, schedules, and margin exposure connected to one record — across every subsidiary and every active site.
> where is the 200-ton crane, and are its inspections current?
x binder in a truck cab · transfer logged nowhere
> deploy equipment_operations --self-hosted
+ qr identity on every asset, owned and rented
+ inspection cadence enforced by equipment type
+ transfers: request → approve → logged
// illustrative — not customer data
// the operating reality
Expensive equipment, punishing conditions, and no system that knows where any of it is.
When a crawler crane sits idle because an inspection lapsed, or a drill rig moves between sites without anyone tracking its certification status, the financial and safety consequences compound quickly. The answers exist — they just live in superintendents' heads, binders in truck cabs, and filing cabinets at the home office.
Subsidiaries across the Midwest, each previously tracking its own assets independently, if at all.
Active projects running simultaneously, with equipment moving informally between them.
Superintendents and crews whose equipment knowledge lived in their heads rather than in any system.
By QR scan — down from phone calls to the home office and hours of digging through filing cabinets.
// what the system connects
Built around the fleet, the sites, and the paperwork
Every asset — owned or rented, a 300-ton crawler crane or a portable generator — carries a unique identity and a weatherproof QR tag. Scanning it returns type, specifications, current location, inspection history, certification status, and transfer log.
Inspection cadences enforced per equipment type — cranes on a different schedule and checklist than vibratory hammers. Due inspections surface to the responsible superintendent; completed ones reach leadership immediately rather than when paper arrives at the office.
Moves between sites or subsidiaries run through a structured request-and-approval workflow capturing asset, origin, destination, reason, and requesting superintendent — every transfer timestamped, where previously there was no record at all.
What is on which site, what is in transit, what has inspections due, and what is sitting idle — in real time, with an automated daily summary compiled and distributed to the operations team.
// what you could ask
Questions your fleet data should answer instantly
// yours to keep
On-prem. Air-gap-capable. Yours.
Field capture, equipment records, and the project record stay in your environment. No mandatory cloud, no offshore handling — which matters when the work is publicly funded or government-adjacent.
$ deploy equipment_operations --target on_prem
+ asset records → your database
+ inspection evidence → your infrastructure
+ air-gap mode: supported
$ locate mandatory_cloud_dependency
x not found
// illustrative — not customer data
// faq
Heavy civil — straight answers
We run multiple subsidiaries with their own systems. Can one system cover them?
Yes — that is the case we have already built. A Cincinnati-area deep foundations contractor operating five subsidiaries had each one tracking its own assets independently, if at all. We gave operations leadership a single real-time view across all five without forcing every company onto identical processes.
Does this cover rented equipment, or only owned?
Both, held to the same standard. The system tracks the supplier, rental period, inspection requirements, and return workflow for third-party assets, and applies the same inspection rigor it applies to owned equipment.
How does this help when an OSHA or DOT inspector shows up?
On the deployment we built, producing an equipment certification history went from phone calls to the home office and someone digging through filing cabinets — a lag that could stretch to hours — to a QR scan returning the full history in under ten seconds.
Can this run on-prem for publicly funded work?
Yes. The system is self-hosted on infrastructure you own, with least-privilege access and an audit trail, and is air-gap-capable where required. No mandatory cloud and no offshore handling.
What does it cost to start?
The First Line Pilot is $1,500 flat — thirty days, one production line, and a machine-verifiable finish you check against the floor rather than a report you have to trust. Full platform deployment is scoped against your actual systems after that, because by then we both know what they are.
// where to start
Start with the line that is costing you the most.
The First Line Pilot is $1,500 flat: thirty days, one production line, a machine-verifiable finish. We deploy the platform on your hardware, instrument one line, and run it in production — you judge the result on the record it produces.
Fixed price, fixed scope, no discovery theater.