Freight · Start here
Find the one freight workflow worth fixing first
A fixed-scope diagnostic for freight forwarders. We map your systems, data, SOPs, exceptions, and operating metrics, then identify the first project worth building — with a business case attached to it. You leave with a plan you own, whether or not you build it with us.
~3 weeks · fixed fee · credited toward implementation
The technology is rarely the first decision
The first decision is which workflow is worth changing — and whether the data behind it is ready. Most AI programs in freight fail on task selection, data readiness, and measurement long before the technology matters. Picking the wrong first workflow is expensive twice: once for the build, and again for the credibility you spend getting the team to try the next thing. This engagement exists to make that first choice deliberate.
Who should book
- Freight forwarders and 3PLs, roughly 20–500 people, running a real operation on a real TMS.
- Leadership that can name a number they want to move — quote turnaround, margin visibility, after-hours capture, reporting lag — even if they cannot yet name the cause.
- Operations running across several disconnected systems: a TMS, a rating tool, accounting, a CRM, and a great deal of email.
- Teams who have been burned by a tool that demoed well and never moved a number.
- Anyone who suspects their data is not clean enough to automate on yet, and wants that assessed before they commit budget.
When it is not a fit
- Companies looking for a demo of an off-the-shelf product. This is a diagnostic engagement, not a sales call with slides.
- Teams that already know exactly what they want built and need only an implementer — you should scope the build directly instead of paying for a roadmap.
- Operations without a system of record. If the business runs on spreadsheets and inboxes alone, the first project is an operational one, and we will say so.
- Anyone who needs a signed outcome guarantee before discovery. We commit to the scope of the assessment, not to a result we have not yet measured.
What you walk away with
Workflow map
Your operational workflows scored on where AI is a genuine force-multiplier today, where it is not yet, and where it would quietly create risk — so the first build targets the right task, not the most obvious one.
Data-readiness audit
What data you have, where it lives, how clean it is, who owns it, and what must be true before an agent or a dashboard can be trusted to run on it.
KPI baseline
Current-state numbers for the metrics the roadmap targets, measured the same way we will measure them later. Without a baseline taken up front, no one can honestly tell whether the build worked.
Sequenced 90-day roadmap
A prioritised plan in the order that compounds — foundation, then visibility, then automation — naming the metric each phase moves and the rough investment each carries.
Architecture direction
Where the work should run, how it integrates with your TMS and surrounding systems, what stays in your control, and the approval points where a person stays in the loop.
How it runs
Systems and workflow interviews
Structured sessions with the people who do the work — ops, pricing, finance, leadership. We trace how a shipment, a quote, and an invoice actually move through your systems, including the workarounds nobody documented.
Data and readiness assessment
We inventory your sources, assess quality and accessibility, and establish a baseline for the metrics you want to move. This is where we find out whether the data can support the thing you want to build, or whether something has to be fixed first.
Roadmap readout
A working session plus a written roadmap: what to build, in what order, the metric each phase moves, the rough investment, and what to deliberately not do. Your team keeps the document.
What we need before we start
None of this is required to book — we collect it once a date is set.
A list of your systems
TMS, rating and quoting tools, accounting, CRM, BI or reporting, and anything critical that runs on email or spreadsheets. Names and rough versions are enough — we do not need access to book.
The metrics you already track
Whatever leadership actually looks at today, in whatever form it exists. If the honest answer is "we do not have reliable numbers", that is a finding in itself, and a common one.
Two or three workflows that hurt
The processes your team complains about, works around, or does after hours. You do not need to diagnose them — that is our job. We just need to know where to look.
The right people for ninety minutes each
Operations, pricing, finance, and whoever owns systems internally. The assessment is only as good as the access we get to the people doing the work.
Who is involved
Alex Orozco, on every engagement
Fifteen-plus years in freight forwarding, international operations, pricing, and process improvement before the AI work. He runs the interviews and writes the roadmap — you are not handed to a junior analyst after the sales call.
Specialist partners, where the build needs them
Data engineering, BI, telephony, and security specialists are brought in by name for implementation work rather than claimed as in-house capability. The roadmap says plainly which parts we would build and which parts a partner would.
Your team, for about ninety minutes each
Operations, pricing, finance, and systems ownership. Leadership joins the week-three readout. We work around your schedule; the sessions are the only real time cost on your side.
Scope and terms
- Fixed scope and a flat fee agreed before we start — no hourly billing and no scope drift.
- Roughly three weeks end to end, paced around your team’s availability.
- If you proceed to a build with us, the assessment fee is credited toward it.
- The roadmap is yours either way. Take it in-house, take it to another vendor, or shelve it — there is no clause that ties the document to us.
- Implementation, licences, and platform costs are quoted separately and are never bundled into this fee.
- No obligation to continue. A recommendation to do nothing yet is a legitimate outcome, and we have given it.
What happens after the readout
Three legitimate outcomes. We will tell you which one we think applies.
Build the first project with us
We scope phase one from the roadmap as a fixed-scope build with the KPI baseline already established, and credit the assessment fee toward it.
Take the roadmap elsewhere
The document is written to be executed by anyone competent — your internal team or another vendor. It names systems and metrics, not proprietary tooling.
Fix the foundation first
Sometimes the honest finding is that the data or the process has to be sorted before automation is worth attempting. If so, the roadmap says that plainly and sequences the cleanup.
FAQ
Is this a sales call?
No. It is a paid, fixed-scope engagement with defined deliverables, and the roadmap is yours whether or not you build with us. If you want a free conversation to work out whether the assessment itself is a fit, book a call — that part costs nothing.
What does it cost?
A flat fee agreed before we start, scoped to the size of your operation and the number of workflows in play. We quote it on the intro call once we know what we are looking at, and it is credited toward the build if you proceed.
Do you need access to our systems?
Not to book, and usually not during the assessment. We work from interviews, documentation, sample reports, and screen-shares. If a specific question needs read-only access to answer properly, we ask for it explicitly and scope it narrowly.
We are on CargoWise. Does that matter?
It helps — CargoWise is common across this segment, and the surrounding rating, accounting, CRM, and reporting systems create integration patterns we have seen before. But the assessment is not CargoWise-specific, and the method works on any system of record.
What if the answer is that we are not ready?
Then that is the finding, and it is worth knowing before you spend a build budget. The roadmap sequences what has to be fixed first. We would rather tell you to wait than sell you a project that cannot succeed.
How is this different from the free consultation?
The free call is thirty minutes and tells you whether there is something here worth pursuing. The assessment is three weeks of structured work with your team and produces a document you can budget and execute against.
Who owns what comes out of it?
You do. The workflow map, the data audit, the KPI baseline, and the roadmap are your documents, with no restriction on how you use them.
Start with one workflow
Book a 30-minute call first. We will tell you whether the assessment is worth it for your operation before you commit to anything.
Book an AI Operations Assessment