LOGISTICS INTELLIGENCE / RFQ AUTOMATION
Answer Freight RFQs Automatically
Send us how your quoting works today. Mirage reads incoming RFQs, matches them against your rate tables and lane history, and returns a quote, no manual re-keying for the requests that match.
Running at Ofret across two entities.
THE REALITY
Most RFQs are standard: same lanes, same volumes, same contracted rates a team already knows by heart. They still get typed into a spreadsheet, checked against a rate card, and emailed back by hand, one at a time, all day.
90%+
of Ofret's standard RFQs answered automatically, across both entities
WHAT MIRAGE DOES
From inbox to quote, without the manual lookup
Reads the RFQ, whatever format it arrives in
Email body, attached PDF, spreadsheet, or web form: Mirage extracts origin, destination, mode, volume, dates, and any accessorials mentioned, without needing a template per customer.
Matches it against your own rates, not a generic index
The parsed request is checked against your existing rate tables and contracted lane pricing. A clean match becomes a drafted quote; anything outside contracted lanes or volumes is flagged as non-standard instead of guessed at.
Drops the result into your TMS quoting workflow
Matched quotes push straight into the TMS you already quote from. Nothing new for your team to log into, and no rating engine to replace.
THE OUTPUT
Every RFQ, matched or flagged
| Request | Lane / Volume | Rate Match | Status |
|---|---|---|---|
| RFQ #4471, inbound email | Casablanca → Lille, FTL, 24T | Contracted lane rate found | Quote drafted |
| RFQ #4472, PDF attachment | Tangier → Marseille, LTL, 6 pallets | Contracted lane rate found | Quote drafted |
| RFQ #4473, web form↳ No contracted reefer rate exists for this specific lane, flagged rather than quoted off a nearby lane's rate. | Agadir → Hamburg, FTL, reefer, 22T | No reefer rate on file for this lane | Routed to quoting team |
| RFQ #4474, inbound email↳ Same lane as row 1, but the requested volume falls outside the contracted tier. Flagged for re-pricing instead of auto-quoted at the wrong tier. | Casablanca → Lille, FTL, 24T | Volume 30% above contracted tier | Routed to quoting team |
PROOF
What RFQ automation looks like in production
Ofret
2 tailored logistics environments deployed, one per entity
90%+ of standard RFQs answered automatically, across both entities
1 shared TMS, zero extra software layers added
Transwin
The logistics agent deployed against Transwin's actual freight and customs document mix
70% less manual data entry on freight documents
Same document pipeline now feeds quoting, not just booking and invoicing
Ready to see your own RFQ match rate?
Send us a sample of real incoming RFQs and your current rate tables, and we'll show you exactly what would have auto-quoted.
How a deployment runs: Observe, Map, Build, Run, Expand. See the method
Prefer to talk it through first? Book a call
FAQ
Frequently asked questions
No. Mirage drafts the quote from your rate tables and lane history and shows the match confidence. Standard requests that match cleanly can go out automatically if you turn that on; anything below your confidence threshold routes to a person before it's sent.
A request on a lane, mode, and volume your rate tables already cover. Ofret runs this at 90%+ across both of its entities, the remainder (non-standard lanes, special handling, out-of-contract requests) is exactly what routes to a person instead of being forced through.
It reads the RFQ for origin, destination, mode, volume, and any accessorials mentioned, then matches those fields against your existing rate tables and contracted lane pricing, the same lookup a quoting team does manually, done consistently every time.
No. It sits in front of it. Mirage reads the incoming request (email, PDF, web form) that a rating engine can't parse on its own, and pushes the structured result into your existing TMS quoting workflow.
They're flagged as non-standard and routed to a person with the parsed request already structured, origin, destination, volume, dates, so your team starts from a filled-in form, not a blank one.
Yes. Email bodies, attached PDFs, Excel spreadsheets, and web-form submissions are all read the same way, without needing a specific template per customer or broker.
4 to 6 weeks to a production deployment: indexing your current rate tables and lane history first, then a parallel pilot on real incoming RFQs before anything goes fully automatic.
Pricing starts with a fixed-price pilot run on a real slice of your incoming RFQ volume, so you see the match rate before committing to anything larger. After that, it moves to an annual subscription priced by volume, quoted in your first conversation with us.