Pull the authority, insurance and registration facts, run the out-of-band callback a spoofed email thread cannot survive, and assemble an evidence pack — a named person at the brokerage selects the carrier.
Do not read the aggregate. Break the mismatch rate down by carrier segment before deciding the programme is working — a few segments carry most of what the checks catch.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
New authorities under a year
8.8%
3.6×
Review
Recent contact-detail changes
5.1%
2.1×
Review
Unrated small fleets
4.2%
1.7×
Watch
Long-standing contracted carriers
1.7%
0.7×
Normal
Bar: mismatch-rate lift vs. contracted-carrier baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A cycle ends in the regression suite
The loop closes on a case the next release must pass, not on an explanation. That suite is what the next carrier put forward is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Mismatch rate rises in a carrier segment.
02Diagnose
Which check moved — the pull, the callback or the standard? Packs are read until one answer holds.
03Improve
The fix is versioned with the packs that motivated it.
04Verify
Nothing ships while an affected case is failing.
05Learn
The case is added for good, and the vetting rules change.
Learn → DetectThe return edge. The next detection runs against a longer suite than this one.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, vetting workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Vetting workflow discovery and boundary definition.
02Registry and load-board source assessment.
03Carrier-qualification standard and callback-rule mapping.
04Carrier-record ingestion and normalisation.
05Check logic and evidence binding.
06Confidence scoring and mismatch routing.
07Broker approval workflow.
08Onboarding- and TMS-system integration.
09Identity-verification cases.
10Guardrails and approval controls.
11Pack-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne office, one carrier listProductionProduction onboarding systemsAdvancedMultiple entities / brands
Introduced at Pilot
Checks against your standard✓✓✓
Broker approval✓✓✓
Evidence-quality baseline✓✓✓
Introduced at Production
Reporting by carrier segment—✓✓
Approval workflow in your systems—✓✓
Approved write-back—✓✓
Onboarding-system integration—✓✓
Introduced at Advanced
Multi-entity vetting standards——✓
Multi-stage compliance approvals——✓
High onboarding volume——✓
Multi-entity vetting controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your carrier intake paths and file structure→Carrier-record ingestion and fact mappingWeek 1
02Representative onboarded carriers→Check baseline, source binding and callback configurationWeek 2
03Your written carrier-qualification standard→Qualification-standard and callback-rule mappingWeek 1
04Access to relevant APIs, feeds or exports→Registry, load-board and onboarding assessment, then integration setupWeek 2
05Carriers you would not want loaded→Identity cases and the evaluation suiteWeek 4
06What a pack may never certify→Confidence scoring, mismatch routing, guardrails and approval controlsWeek 3
07Named approvers to decide held carriers→Broker approval workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Each phase occupies the weeks it needs, so the fifth week carries two kinds of work.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Vetting workflow discovery, standard mapping and the automation boundaryW2Registry and onboarding-source integration and the check baselineW3Vetting workflow, confidence logic and approval controlsW4Evaluation suite, identity cases and failure-mode testingW5Onboarding and TMS integration, pilot carriers and targeted correctionsW6One onboarding cycle worked under compliance, then handover
Reading the bandEach bar covers only the weeks its work is named in. The week 5 overlap is real, not padding.
At the end of W6The cycle closes validation and Agent Care assumes monitoring.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Transportation AI agent
Build a carrier-vetting agent around your onboarding chain.
Show us your qualification standard and your onboarding sources. A named person signs every approval, and after Montgomery that signature is the act state law reaches.
