Every broker email,
every load document — organized automatically.
Connect your inbox. Your loads organize themselves. Find any POD, rate con, or dispute detail in seconds.
Freight runs on email.
Nobody built a system for that.
Rate cons, BOLs, PODs, invoices — all of it moves through Outlook and Gmail. Every party keeps their own copy. When something goes wrong, everyone digs through inboxes and argues.
The 20-minute POD search
Searching Outlook for last month’s POD. Scrolling threads, checking attachments, hoping nothing was forwarded to a personal address.
Reconstructing a disputed load
A chargeback hits six weeks later. Now you’re piecing together the rate con, the emails, the driver’s text, the POD — from memory and inbox archaeology.
Loads stuck in stages you forgot about
Half your book is somewhere between delivered and invoiced. You only notice when the broker stops paying or the shipper calls about a claim.
Three steps. No new software for anyone else on your loads.
- 1
Connect your inbox
Sign in with Outlook or Gmail. Read-only access. We never send or modify email. Disconnect anytime in one click.
- 2
Your loads organize themselves
We quietly scan the last 90 days. Rate cons, BOLs, PODs, and invoices get pulled out and attached to the right load. Nothing leaves your account.
- 3
Ask anything, get answers in seconds
“Show me loads missing PODs.” “What happened with load 48291?” Every answer cites the email or document it came from.
Here’s what happens the moment an email hits your inbox.
Four stages. All in the background. The user sees a clean load card — not a classifier, not a vector store, not a queue.
One for brokers. One for dispatchers. Same data, different job.
Brokers work stage-by-stage. Dispatchers work driver-by-driver. The same canonical load record shows up in both, shaped for the job in front of you.
Every active load at its real stage.
Auto-moves as emails and documents arrive. Drag-to-override any time. Red flags surface themselves.
Your fleet, by driver, with the paperwork already attached.
PODs flagged for factoring. Rate-con archive by broker. Aging view so nobody slow-pays you twice.
Open a load. See every email, document, note, and state change — in order.
Click any extracted field and watch it highlight in the original document. Add a note for something that happened on a phone call. The audit trail is append-only — history never rewrites itself.
The WhatsApp and iMessage problem —
solved without touching either.
Your driver sends PODs on WhatsApp. Your carrier sends rate cons on iMessage. Your shipper emails a lumper receipt from a personal address. None of those are going to change — so we don’t try to change them.
One link. Any channel your team already uses. The document lands structured on the right load — every time.
— any of them, none integrated
Every upload is stamped with evidence — on purpose.
When a dispute lands six months later, you don’t want “the driver texted me something on WhatsApp.” You want a timestamped, geo-tagged, phone-captured, hash-verified record pointing straight at one load.
- Link expires in 7 days (configurable)
- Max 3 uploads per link (configurable)
- PDFs and common image formats only · 25 MB cap
- Virus scan before anything hits your load
- Revoke with one click — you can kill a link mid-upload
Never lose a POD again — but your inbox stays yours.
Five built-in rules watch for the things that fall through the cracks. When one fires, Claude drafts the chase message. You review, copy, and send from your own inbox. We never send on your behalf.
Hi team —
Following up on load #48291 (Dallas → Phoenix) — delivered Apr 23 at 17:40. We haven’t received a POD yet and we’re approaching our factoring cutoff.
Could you send the signed POD at your earliest? Happy to jump on a quick call if the driver needs to re-scan.
Thanks,
Aman
The parts of the job that don’t fit a kanban either.
Ask your data anything.
Claude answers from your own loads, with citations back to the original email or document.
Mode · 33 days · $3,120 (1 invoice)
FreightPath · 31 days · $2,880 (1 invoice)
Every carrier, broker, shipper — already there.
Auto-derived from your email. Click any party to see every load, aggregate stats, and history.
I grew up in trucking. I drove trucks through college. Then I spent a decade building software for Fortune 100s.
My dad owns a carrier. I’ve watched dispatchers chase PODs, I’ve watched brokers reconstruct loads from memory, and I’ve watched drivers send BOLs through six different inboxes before payment lands. At USPS I led an AI platform used by 30,000+ people. This product is what happens when you point that stack at the work my family still does every day.
Shaped with a top-10 US brokerage and a mid-size carrier — before we wrote a line of code.
We are onboarding a small number of additional design partners now. Design partners get the product free, shape the roadmap, and keep that pricing after GA.
Named partners disclosed with consent.
Named partners disclosed with consent.
Your inbox is load-bearing infrastructure.
We treat it that way.
The fastest way to lose a freight customer is to make them nervous about data. Privacy was the first thing we built — not the last.
Read-only inbox access
We can read headers, subjects, bodies, and attachments. We cannot send, reply, modify, or delete anything — the OAuth scopes don’t allow it.
Never sent, shared, or sold
Your data is siloed to your account. We never share one customer’s data with another. We do not sell data. We do not train models on your email.
Non-load email stays invisible
Newsletters, personal mail, and internal chatter are filtered out before storage. You can also exclude specific folders, labels, or threads.
Nothing goes out without you clicking send
Claude drafts chase messages. You copy, paste into your own Outlook or Gmail, review, and send. V1 never transmits outbound email on your behalf.
One-click disconnect and delete
Revoke access any time. Your extracted loads, documents, raw artifacts, and OAuth tokens are purged — 24h from primary, 30 days from backups.
Encrypted end-to-end, audited
Encrypted at rest (AES-256) and in transit (TLS 1.2+). OAuth tokens in a dedicated secret store. SOC 2 Type II audit in progress.
The questions people actually ask.
Yes. We live alongside McLeod, Aljex, MercuryGate, and the rest. We ingest the emails that flow in and out of your TMS — we do not replace it.
Connect your inbox.
Watch your loads organize themselves.
Drop your work email. We’re onboarding design partners weekly — free through V1, with pricing locked after GA.