Implementation, 30 / 60 / 90 — honest version
What a broker TMS implementation actually looks like.
The legacy broker TMS implementation timeline — 6-12 months, $50,000-$150,000, a dedicated PM from the vendor, a 200-line requirements doc — is one of the biggest reasons SMB and mid-market brokerages stay on outdated systems. It does not have to be that. Keelway implementations run from under-24-hours-to-first-load on the SMB tier to a 60-90 day phased rollout on the mid-market tier. This page documents the honest cadence for each.
<24h
SMB time-to-first-load
$799/mo flat tier
30–60d
Mid-market full cutover
Phased per-desk
$0
SMB implementation fee
Self-serve onboarding included
The three implementation tiers
SMB
5–25 brokers · Under 1 week to full productivity
Day 1: Reply address issued, FMCSA backfill on existing carrier book, load-posting templates configured. Days 2-3: rate-confirmation template branded, QuickBooks OAuth. Days 3-5: first loads triaged, ranking weights tuned. Self-serve with email and Slack support. $0 implementation fee.
Mid-market
25–200 brokers · 30–60 days phased
Weeks 1-2: kickoff, SSO + IdP integration, sandbox tenant. Weeks 2-3: historical carrier-data migration, FMCSA backfill, label taxonomy review. Weeks 3-4: first desk shadow mode. Weeks 4-8: phased per-desk cutover with daily syncs. Named CSM throughout. Implementation fee modest, scoped up-front.
Enterprise
200+ brokers · 60–120 days, often overlay
Weeks 1-2: procurement, security clearance, MSA execution. Weeks 2-3: dedicated tenant provisioned, SAML + SCIM live, audit logs to SIEM. Weeks 4-18: per- brand phased rollout. Overlay pattern preferred over outright replacement on sticky legacy TMS investments. See the enterprise multi-brand case study.
Universal
What every tier gets
Carrier data migration with FMCSA backfill. Load template setup. Rate-confirmation template branded to the brokerage. Inbox-AI ranking weights tuned to actual desk mix. Accounting integration (QBO standard, NetSuite enterprise). At least one major load-board integration (DAT One default; Truckstop ITS on request).
The failure modes that quietly kill broker TMS implementations
- One-day cutover across the entire floor. Always fails. Phased per-desk is the only pattern that works at mid-market scale and above.
- Migrating dirty data. Duplicate carrier records, expired insurance docs, stale shipper credit info — clean them in the source TMS before migration. Debugging inside the destination is a tax nobody enjoys.
- No plan for the productivity dip. Senior brokers lose 30-50% of their daily throughput in week 1 on a new system. Without a buffer plan, the brokerage panics and blames the tool.
- Under-scoping the EDI cutover. Working EDI pairs to top shippers took quarters to build and are load-bearing. Always run the new and old EDI pairs in parallel for at least 14 days before retiring the old one.
- Skipping ranking-weight tuning. The difference between a reefer desk's effective top-5 and a flatbed desk's effective top-5 is large. Implementations that skip per-desk weight tuning under-deliver on the AI productivity gain.
Frequently asked questions
How long does a broker TMS implementation take?+
Depends sharply on tier. For a 5-25 broker SMB shop on Keelway TMS at $799/mo flat: under 24 hours from signup to first load triaged, with most brokers fully productive by end of week 1. For a 25-200 broker mid-market 3PL: 30-60 days, phased per-desk. For a 200+ broker enterprise with EDI and multiple brands: 60-120 days with the overlay pattern often preferred over full replacement. Anything quoted under a week for a real mid-market+ implementation is underscoping the carrier-data work.
What does week-1 actually look like at Keelway?+
Day 1: reply addresses issued for each desk and dropped into your DAT/Truckstop postings. Day 1-2: FMCSA backfill on the brokerage's existing carrier book — typically 1,000-10,000 carriers depending on shop size. Day 2-3: load posting templates configured, rate-confirmation template branded, QuickBooks Online OAuth connected. Day 3-5: first loads posted and triaged with Keelway live; ranking weights tuned to the brokerage's actual desk mix. By end of week 1 the floor is productive on the new system.
What's the 30/60/90 cadence on a mid-market deployment?+
Day 30: first desk fully cut over from old TMS to Keelway as system of record. Ranking weights tuned to that desk's freight shape. Coordinator training complete. Day 60: second and third desks cut over. Cross-desk reporting live in the Keelway dashboard. EDI pairs running in parallel between old and new TMS where applicable. Day 90: all desks live on Keelway. Old TMS goes read-only for AR/AP reference. Quarterly business review scheduled with the dedicated CSM.
What's the most common implementation failure mode?+
Underestimating the broker retraining cost. A senior broker can move 20-30 loads/day on muscle memory in their existing TMS; in the first week on a new system that productivity drops to 8-12 loads/day even on better software. The brokerages that fail an implementation try to push through this dip with no plan; the ones that succeed pre-commit a productivity buffer — sometimes pulling forward a slower week, sometimes temporarily reducing posting volume — for the first two weeks per desk. Keelway's implementation plan builds this buffer in by default.
Do you charge an implementation fee?+
For the $799/mo flat TMS plan: no. $0 setup fee, $0 onboarding fee. Implementation is self-serve with email and Slack support. For Enterprise tier deployments: implementation fees range from $0 to roughly 2-3 months of platform fee depending on scope (data migration depth, EDI cutover, dedicated tenant provisioning, named implementation engineer). Quoted up-front against a defined scope, not against ranges. Compare to McLeod LoadMaster where implementation alone is typically $20-$80K.
Planning the implementation?
We'll model the 30 / 60 / 90 for your shape.
Related
TMS migration guide →
The companion guide for brokerages migrating off an existing TMS rather than implementing fresh.
Mid-market McLeod overlay →
An 85-broker 3PL implementation walked end-to-end with the overlay pattern.
Keelway Enterprise →
The contracting and support posture for implementations that need a named implementation engineer.
