FIG. 01 — FREIGHT OPERATIONS
The last rep logs off and the spot-request emails keep landing. Tomorrow starts with triage: a stack of expired requests, two dispatchers already on check calls, and customers emailing “where’s my freight” in parallel.
At 6:04pm your last rep logs off. The quotes keep coming. By morning, they’re somebody else’s loads.
The fastest credible quote wins the freight — and after hours, nobody’s quoting. We build AI that answers the emails, reads the BOLs, and makes the check calls, so your team covers more loads with the people you have.
Your dispatcher’s brain is your routing engine. We turn that brain into software before it retires.
FIG. 02 — WHERE THE MARGIN LEAKS
Five workflows capping your loads per rep. The industry built them, not you.
Quotes, tenders, PODs, check calls, and carrier compliance all run on human hands — and the inbox never sleeps. Here’s where the margin leaks:
Quotes age out unanswered
Hundreds of spot-quote emails a day; reps take the easy ones and the rest expire in the inbox. The fastest credible quote usually wins the freight, and after 6pm nobody’s quoting.
Tenders slower than shippers
Tenders arrive by EDI, email, and portal, then get keyed into the TMS by hand. Your accept/decline decision runs slower than the shipper’s routing-guide clock.
Invoices wait on paperwork
PODs and BOLs get collected, matched to loads, and filed by hand. Billing waits days for a signature page somebody photographed in a truck cab.
Check calls, all day
Dispatchers call carriers for status while customers email “where’s my freight” in parallel. Two full-time jobs producing the same answer twice.
Expired certs found late
Carrier packets, insurance certs, and authority checks are processed manually at onboarding, then go stale. An expired cert gets discovered after the load is on the truck.
FIG. 03 — WHAT CHANGES
Five systems on top of your TMS — five before-and-afters.
Email Quote Agent
Today: the inbox decides your win rate. After: spot requests parsed, priced from your rating logic and lane history, and answered in minutes — around the clock. Your reps handle exceptions and relationships, not volume.
Tender Processing Agent
Today: the shipper’s routing-guide clock beats your data entry. After: load details extracted from EDI, email, or portal straight into the TMS, your accept/decline rules applied with margin checks. The clock stops beating you.
POD/BOL Document Agent
Today: billing waits days on a photographed signature page. After: PODs and BOLs captured from email and driver uploads, matched to loads, exceptions like OS&D notes flagged — and invoicing triggered the same day.
Track-and-Trace Agent
Today: two full-time jobs producing the same answer twice. After: status collected from carrier APIs, ELD data, and automated outreach; customers updated proactively; dispatch sees only true exceptions.
Carrier Onboarding Agent
Today: a lapsed cert surfaces after the load is on the truck. After: packets processed, authority and insurance verified against FMCSA data, and expirations watched continuously — so a lapse surfaces before a load does.
TARGETS ARE TARGETS — SET IN THE OMEGA STATEMENT, MEASURED FROM WEEK 1. NOT CLAIMED RESULTS.
FIG. 04 — THE OMEGA METHOD, ON YOUR LANES
You’ll watch it quote your real freight before you pay the last invoice.
- WEEK 0Endgame
Your Omega Statement, signed: e.g. “Every spot request answered within 15 minutes, 24/7.”
- WEEK 1▪ DEPLOYEvidence + Blueprint
We replay a week of your real quote emails through the agent and measure parse accuracy against what your reps actually quoted. Kill/go verdict, then the Build Blueprint with the TMS and rating-engine integration mapped.
- WEEK 2▪ DEPLOYBuild
First Friday deploy: quotes drafting on live inbox traffic, held for rep review, wired to your rating logic in a sandbox.
- WEEK 3▪ DEPLOYBuild
Second Friday deploy: margin rules, exception queues, after-hours behavior — the agent answering a controlled slice of live requests.
- WEEK 4▪ DEPLOYBuild + Launch
Full cutover, monitoring, and the Launch Runway: go-live checklist, response-time dashboard, first-month review scheduled.
Working software every Friday. Your reps grade real quotes, not slideware.
FIG. 05 — THE GROUND RULES, IN WRITING
Your TMS stays the system of record. Your rates stay yours. Plainly stated.
You’ve seen software vendors try to become the system of record and hold the data hostage. These are the rules every freight build ships inside:
- [✓]The TMS is not replaced. We integrate with McLeod, Turvo, Aljex, and comparable systems. Every load, rate, and document the agents touch lands in your TMS — no shadow database.
- [✓]Rate confidentiality preserved. Customer routing guides and negotiated rates are access-controlled and never leave your tenancy. Your pricing logic is your moat; we treat it that way.
- [✓]FMCSA data used per its terms. Authority and insurance verification runs against FMCSA records under their usage terms — no scraping games, no gray-area data brokers.
- [✓]SOC2-friendly architecture. Access controls, encryption, audit logging on every agent action. We claim no certification we don’t hold; we build so your shippers’ security questionnaires come back clean.
- [✓]Humans own the exceptions. Agents quote, match, and chase inside rules you set. Anything outside the rules — margin floors, OS&D disputes, hot accounts — routes to a person.
COMPLIANCE COMMITMENTS REVIEWED BY ENGINEERING LEAD BEFORE PUBLISH
FIG. 06 — A FIRST SPRINT, WORKED
A first Sprint for a shop like yours, worked end to end.
The situation
Picture a 30-person brokerage where the day starts with triage: spot requests piled up overnight, win rate tracking whoever answered first the night before.
The Omega Statement
“Every spot request answered within 15 minutes, 24/7.”
What shipped
Week 1, a week of their real quote emails gets replayed through the agent, and parse accuracy is measured against what their reps actually quoted — before a build dollar is committed. Four Fridays later, the email-quote agent is wired to their rating engine and lane history: parse, price, reply, log to the TMS. The reps take the exceptions and the relationships. The agent takes the inbox — including the 2am one.
Metrics tracked
- RESPONSE TIME
- QUOTE VOLUME
- WIN RATE
- REVENUE PER REP
This is a worked example of a first Sprint — illustrative, not a client result. It’s stamped TEMPLATE until a real engagement replaces it.
FIG. 07 — THE PLAN AND THE PRICE
Three steps. Fixed price. Published.
DISCOVERY FEE CREDITED 100% AGAINST THE SPRINT
FIG. 08 — THE QUESTIONS YOUR OPS FLOOR WILL ASK
Straight answers, before the meeting.
Does this replace our TMS?
No. The TMS stays the system of record; the agents feed it. Quotes, tenders, documents, and statuses all land where your team already works — McLeod, Turvo, Aljex, or comparable — via API where available, documented fallback where not. If we can’t integrate cleanly, Week 1 tells you before you’ve paid for a build.
Our rate logic lives in two senior reps’ heads. Can you even automate that?
That’s the usual starting condition, not a blocker. Week 1 turns their pricing decisions into explicit rules by replaying past quotes with them at the table, and the agent applies those rules with margin floors — anything outside them routes to a rep. The dispatcher’s brain becomes software your shop keeps.
How do you keep our customer rates and routing guides confidential?
They stay in your tenancy under role-based access with audit logging, inside a SOC2-friendly architecture. Rates are never shared across clients, never used to train shared models, and never visible to anyone outside the access list you set.
We’re 30 people with no IT department. Who runs this after launch?
You own it — code, infrastructure, and documentation — and it’s built to run without a resident engineer: managed cloud, monitoring with alerts, and a runbook your ops lead can follow. The Launch Runway includes handover training, and if you want us on call, the Growth Package at $12,500/mo covers iteration and support. No hostage architecture.
Will an AI quote something stupid and cost us a customer?
Not on its own. The agent quotes inside rules you set — margin floors, lane limits, account restrictions — and anything outside them is drafted and held for a rep. During Weeks 2–3 every quote is held for review while your team grades it; you decide when any slice goes fully automatic, and you can pull it back anytime.
A question we didn’t answer? Ask it in a Product Session.
FIG. Ω — THE END STATE
Bring your quote-response numbers.
In one Product Session we’ll show you the margin math on answering in 15 minutes instead of 4 hours — with your volumes, your lanes, your win rates. You leave with a one-page scope and a fixed price.