What implementation looks like.
Setup takes 24 hours once required access is ready. Here is how that access works, who does what on each side, and what the first 90 days look like.
Required access, before setup
“Required access is ready” means the connector is in place for the workflows in scope. Your TMS remains the system of record for execution; nothing is replaced.
- 1
The Navion connector
We deploy a connector into your environment. Your team configures it to grant Navion access to your TMS and to your document management system, where everything collected during an order lives: BOLs, scale tickets, delivery tickets, detention records, proof of delivery. Access stays under your control.
- 2
Order request channels
The inboxes, portals or other channels where order requests arrive today, so requests can enter the workflow the way they already do.
- 3
People
An IT contact to deploy and configure the connector, a dispatch or operations reviewer, and a billing contact.
Brought in during the rollout
Customer requirements are not a prerequisite. They come in over the 90 days, working with your team.
SOPs, if you have them
If your operation has written SOPs, we ingest them. Many carriers don’t, and that is fine: the workflow starts from how your people work today.
Customer requirements
Over the 90 days we work with your team to incorporate the customer rules your people apply: notice windows, required documents, billing conditions. Per division, where divisions work differently.
Your first 90 days
$0 implementation
DAY 1
Get connected.
24-hour setup once required access is ready.
MONTH 1
See the impact.
Less chasing. Cleaner orders. Your team feels the difference.
BY DAY 90
Fully rolled out.
Agreed workflows live. Results measured on your freight.
The timeline is a rollout sequence, not a measured ROI curve. Results are measured on your freight against the baseline agreed before setup.
Who does what
Your team
- IT deploys the connector and configures TMS and document access.
- Dispatch and operations leads walk through the workflows in scope, share SOPs where they exist, and approve the checks that apply.
- Billing confirms the handoffs and the documents each customer requires.
Navion
- An implementation lead owns the rollout from kickoff through go-live and stabilization.
- Workflows go live within the agreed scope, and customer requirements are incorporated with your team across the 90 days; your people keep control of requirements and approvals.
- After stabilization, the rollout hands off to Customer Success for the ongoing relationship.
Agreed before setup
Scope, measurement and terms are agreed with your team before setup starts:
- The covered workflows and the automation available for them.
- The billable order definition and the orders covered.
- The baseline, the measurement period and the financial benefits that count.
- Contract terms. Implementation is $0 and the first 90 days are unpaid.
Start with one order.
Bring the order, customer rule or billing handoff where the work gets stuck. We will work through the access and scope from there.
Talk about our operation