Implementation
Live in 30 to 45 days.
Five phases, a named delivery team, and a shared Slack channel with ours. Implementation is configuration, not construction: Autopilot already knows the load lifecycle.
The five phases
From kickoff to every load.
Data starts flowing in week two or three, so value shows up before go-live.
Setup
Days 1–5Kickoff with your team. We walk the load lifecycle stage by stage, open a shared Slack channel with your champion, and assign a delivery manager who stays with you past go-live.
Integration
Days 3–14We connect your TMS and map your fields, including the ones your team invented. Workspaces split the way your business does: by revenue code, terminal, office or branch.
Tuning
Days 10–30Loads are flowing. We configure checkpoints against your actual SOP: timing, quiet hours, exclusions, what it says and in whose name. Your feedback on real messages drives it.
Rollout
Go-liveSign-off, then a controlled subset first: one pod, one customer or one division. A week or so on live freight, then expansion in waves.
Observation
Days 30, 60, 90Structured reviews of what Autopilot handled, what it escalated and where exceptions clustered. Write-backs verified. Then it just becomes your normal cadence.
Week by week
Who does what, and when.
| When | What happens | Who |
|---|---|---|
| Week 1 | Kickoff, lifecycle walkthrough, shared Slack channel, delivery manager assigned | Chain + your champion |
| Week 2 | TMS connected, fields mapped, workspaces split | Chain |
| Week 3 | Loads flowing; first checkpoints live on real freight, reviewed together | Chain, with your feedback |
| Weeks 4–5 | Tuning: timing, tone, quiet hours, exclusions, escalation recipients | Chain, with your feedback |
| Go-live | Sign-off; a controlled subset goes live first | Chain + your team |
| After | Wave-by-wave expansion; 30/60/90-day reviews | Chain + your champion |
Multi-division rollouts and TMSs that need new mapping work take longer. We'll tell you which you are on the kickoff call, not in week six.
The champion
The biggest variable is on your side of the table.
Across customers, no-touch rates run from 70% to 94%. The gap is rarely technical. It's whether someone internally owns the change.
- Owns the SOP: decides what Autopilot says and when, because they already know what a good check call sounds like.
- Owns the edge cases: each decision becomes a checkpoint instruction and never has to be made again.
- Gives feedback in week three, not week ten.
- Holds the floor accountable, because habit check calls drag the number down no matter how good the agent is.
What it costs to implement
Nothing. Here's the fine print.
No implementation fee, no integration fee, and no professional services line. The one exception: some TMS vendors charge their own module fee for the connection, and that shows up as a labeled pass-through.
What do you need from our team?
A champion, TMS access, about an hour on the kickoff call, and honest feedback during tuning. No engineering time, no workflow authoring.
Can we start with just track and trace?
Most customers do. It's the deepest product and the fastest to value. Booking and documents layer on once you have a number you trust.
What if our TMS isn't on your list?
Tell us on the first call. We'll say honestly whether it's a two-week mapping job or longer, and there's still no integration fee.