VERTICALS
One binary. A different
record out of each.
A vertical is not a product. It is a prompt pack, a registry entry, a renderer and a credentialed reviewer — running on the same container, on the same hardware, against the same canonical record.
WHAT A VERTICAL COSTS US
Four things, and none of them are in the core.
A prompt pack
What to look for and what it means in this domain.
A registry entity
No open places, custom endpoint types, signal modalities.
A renderer
The mapping from canonical record to the format the industry files.
A reviewer
Someone credentialed in that domain who signs off on ground truth.
Everything else — capture, time alignment, edge reasoning, the evidence chain, egress policy — is identical across verticals. That is why the second one is not priced like the first.
VERTICAL IN ACTION
Emergency medical services
- Live
Where we started, because every job produces a billable claim. The record has value from the day it is created, rather than only at audit.
The record: NEMSIS, the federally standardised patient care report.
- The record writes itself — charting is reconstructed from memory and delivered for review.
- Protocol adherence on every run — interventions are timestamped and source-linked.
- Level of service, evidenced — findings are captured as they occur.
- Structured export to the system you already run — crews keep the software they know.
Simulated run — the record assembles as the event is delivered, the reviewer approves, and the completed return exports to the existing system.
83% of improper payments on ambulance claims trace to documentation failures. Incorrect coding accounts for 0.3%.
CMS, 2024
VERTICAL IN ACTION
Fire and rescue
- Live
Not a second market: the same vertical, in the same account, with a second output schema on vehicles already deployed.
The record: NFIRS, moving to NERIS.
- Radio and cabin audio, time-aligned — fragmented channels share one incident timeline.
- Benchmarks from what actually happened — arrival and scene milestones use observed signals.
- Reported against observed — response times are measured, not remembered.
- Incident record, drafted — an NFIRS and NERIS output is rendered from the same canonical record.
Simulated run — the record assembles as the event is delivered, the reviewer approves, and the completed return exports to the existing system.
Incident data is fragmented across systems. Radio, video and telemetry must align before the full timeline can be reviewed.
Next — utilities, mining, electricity and gas.
The same container on bucket trucks and service vehicles that already carry a cellular router. One gateway fleet, two regulators, a second prompt pack.
The record, electric: a documented job briefing before every job — the first document an inspector asks for after an incident.
The record, gas: operator qualification and leak survey logs, per task and per mile.
ON THE ROADMAP
Mining, ports and terminals
- Roadmap
Terminal tractors, haul trucks and support vehicles. Both score against the same entry screen we apply everywhere.
- The screen we enter on — a record law requires, with evidence that carries money or liability.
- Why not yet — a vertical opens when the previous one is self-funding; sizing a market is not the same as entering it.
- Mining — ~12,500 active US mine sites, each requiring a documented examination every shift. (MSHA)
- Ports — no federal record mandate, and no incumbent either: reporting a near miss today costs an operator a move cycle and a hundred-foot ladder.
The same screen also tells us where not to go. Law enforcement fits and is already owned. Trucking fits and is already owned. Construction fits, and the buyer will not pay for it.