Legacy freight software your team already works around
The record says one thing. Your team knows another. That gap is not inside the software you own, so changing the software does not close it.
Every email your company receives is read, understood and turned into a task for the right person, with the answer already drafted. Your team approves. Nobody lives in the inbox any more.
Keep your TMS for the records. FreighAI runs the work around them. Replacing it later stays a separate decision.
need DHL quote Gurugram → Ajman, 72kg, by Friday. express.
packing list attached. urgent pls 🙏
Pls quote for shipment as below. Confirmed pkg dims attached, IEC docs to follow…
- 01Legacy freight software is rarely the thing that hurts. If your team works around it, the work you want back is not inside it. It is in email, WhatsApp, a shared drive and two people’s memory.
- 02A new system does not recover that work. It inherits the same email, read by the same team.
- 03FreighAI takes the email and the work behind it. Reading the thread, finding the rate, chasing the agent, drafting the reply, putting a task in front of the right person.
- 04Your current system keeps the records it still holds well. Documents, statutory books, filing and the audit trail stay where they are.
- 05Keep and coexist, stage the replacement, or migrate. Three decisions, three triggers. Nothing here makes migration the default.
How the work left the system
There are four common ways a business ends up here. A freight package bought long ago, and the supplier stopped changing it. An ERP adapted for freight because nothing else fitted the budget. Something built in-house that fitted exactly at the time. Or a system that arrived with a company you acquired. Each was reasonable when it was made.
So the work went around it. A rate is agreed on a call and confirmed on WhatsApp. A revised quote sits in a spreadsheet on a shared drive. An amendment lives in one person’s sent items. The system hears about all of it later, from a person. The record is rarely wrong. It is late, and everyone carries a private sense of how late.
Take one week and count:
- decisions agreed in a channel the system never sees;
- numbers typed a second time somewhere else; and
- chases that depended on one person remembering.
The question is not whether to replace the system. It is where this work should live while you decide.
- 01Enquiry arrivesRead by whoever is free
- 02Rate agreed on a callConfirmed on WhatsApp
- 03Quote in a spreadsheetOn the shared drive
- 04Forwarded to operationsAnd then chased
- 05Amendment in sent itemsOne person has the detail
- 06Keyed into the systemThree days later
What changes when the work has somewhere to live
You can keep the system you run today and add FreighAI around it, or move on from it and let FreighAI be your main system. Start with pricing and operations either way, and add the rest when you are ready.
FreighAI takes over the inbox. It watches every company mailbox, pricing, operations, tracking and accounts, and follows each conversation from start to finish, not one message at a time. It works out what each email is and what it needs. It writes the reply, creates the task, and puts it in front of the right person in the right department. That person reads it beside the original conversation and approves. They do not compose, forward, file or chase. The reply goes out in their name. The follow-ups happen on their own.
None of that asks your current software to behave differently. FreighAI works on the conversation, where the missing work already is.
The second change matters more here. Work that used to be invisible now has an owner and a clock. Work passes from pricing to operations to accounts with the email and everything it found attached. Nobody forwards it, re-keys it or asks for an update.
Your people work in FreighAI. Not in the inbox. Not in five browser tabs.
We scope the first workflow, integration requirements and implementation plan with your team. Start where the workaround costs the most.
Watches every company mailbox, pricing, operations, tracking and accounts, and follows each conversation from start to finish.
FreighAI works out what each email is and what it needs, then takes the action that message calls for. It pulls your rate cards, checks the carrier, looks up the customer’s history, reads the shipment status, and talks to your TMS or accounting system.
Jobs, invoices, documents and the audit trail. It does not move.
Work with an owner, a clock and a queue
Your people work in FreighAI, not in the inbox. Your team approves. They do not compose, forward, file or chase. The reply goes out in their name.
- Nothing waits in a private inboxFreighAI watches every company mailbox, pricing, operations, tracking and accounts, and follows each conversation from start to finish.
Which parts would you use first?
Start where the workaround costs the most, not with the longest product list.
Quotation Agent
For the enquiry nobody types into the system. FreighAI spots what is missing in an enquiry and drafts the email asking for it. It emails all your agents for a lane in one go, with the route and charge lines filled in, then chases the ones who do not reply.
Booking and Job Orders Agent
For the amendment agreed in a chat. A won quote becomes a job on its own, fully filled in.
Tracking Agent
For the customer who writes in. FreighAI answers “where is my cargo?” on the customer’s own thread, from carrier status, for approval.
Invoice Reconciliation
For the bill checked against a printed sheet. FreighAI reads a carrier bill and matches every airway bill back to its job, checking line by line before it is booked.
Payment Collection
For the receivable chased when somebody notices. Follow-ups, chasers and reminders happen on their own, on the same conversation.
Partner Discovery
For the lane you do not hold. A structured way to find and assess partners.
Take on the next one when its workaround starts costing you. Nothing here has to arrive as a set.
What happens to one enquiry
An enquiry arrives. FreighAI reads it, notices the weight is missing and asks for it. It pulls your rate cards, checks the carrier for a live rate, and emails your agents for the lanes you do not hold, then chases them until they reply. It drafts the quote with your margin rules and what that customer paid on that lane last time. Your pricer approves and it goes. It follows up. When the customer pushes back, the counter-offer is already drafted. When the quote is old, it expires. When it is won, the job is created.
Where the rate can be fetched without waiting on a person — a carrier API, a portal read in the background, or your own uploaded rate cards — a priced quote goes out in 10–15 minutes instead of 1–2 hours. That holds for ocean and air just as it does for express; the mode does not change it. Where a lane has to be priced by another agent or over the phone, the wait belongs to whoever is answering — not to the software. FreighAI still writes the RFQ, chases the reply, and turns whatever comes back into a priced, margin-checked quote the moment it lands.
None of that happened inside your old software. The job reached it once, already filled in.
need DHL quote Gurugram → Ajman, 72kg, by Friday. urgent pls 🙏
Hi Marco — DHL Express, AED 425 + AED 35 handling. ETA Thu·18:00, valid 24h. PDF attached.
At Infinity Logistics, average response time fell from more than 60 minutes to about 15 minutes, and the win rate rose from 35% to 73%. Those figures belong to one customer and are not a promise to every business.
What stays in your system, what FreighAI adds and what has to be decided
The first workflow needs a boundary, not a migration plan.
| Area | Stays in your current system | FreighAI adds | Decision required |
|---|---|---|---|
| Job and shipment records | The job, the shipment and the numbers you show customers and auditors | A won quote becomes a job on its own, fully filled in. | Which record anchors the first workflow? |
| Documents and the audit trail | Filed documents and the history you have to keep. Records for traded goods declared to HMRC must be kept for four years, and other countries set their own | Reads PDF, Excel, Word, forwarded email, WhatsApp messages, photos and scans. | Which documents may be read, and who approves what is prepared from them? |
| Statutory books, filing and duty | Ledgers and accruals, direct filing to the customs authority, and any duty or HS lookup | Reads a carrier bill and matches every airway bill back to its job, checking line by line before it is booked. | Does the checked bill return to your system, and by whose hand? |
| Reports and dashboards | Whatever your system reports today | Nothing. Reporting stays where it is | Which numbers must still come from your system? |
| Warehouse, fleet and customer portals | Stock and bays, trips and vehicles, and any customer portal | Answers on the thread, for the customers who write in instead | Who approves that answer, and where is it recorded? |
| The enquiry, the chase and the reply | Nothing today. This part lives in email, WhatsApp and one person’s head | FreighAI works out what each email is and what it needs, then takes the action that message calls for. Follow-ups, chasers and reminders happen on their own, on the same conversation. | Which mailbox starts the workflow, and who owns each step? |
| Where your team works | Your current screens, for the record | Your people work in FreighAI, not in the inbox. | Which screen does each role open first? |
- Job and shipment records
- Stays in your current system
- The job, the shipment and the numbers you show customers and auditors
- FreighAI adds
- A won quote becomes a job on its own, fully filled in.
- Decision required
- Which record anchors the first workflow?
- Documents and the audit trail
- Stays in your current system
- Filed documents and the history you have to keep. Records for traded goods declared to HMRC must be kept for four years, and other countries set their own
- FreighAI adds
- Reads PDF, Excel, Word, forwarded email, WhatsApp messages, photos and scans.
- Decision required
- Which documents may be read, and who approves what is prepared from them?
- Statutory books, filing and duty
- Stays in your current system
- Ledgers and accruals, direct filing to the customs authority, and any duty or HS lookup
- FreighAI adds
- Reads a carrier bill and matches every airway bill back to its job, checking line by line before it is booked.
- Decision required
- Does the checked bill return to your system, and by whose hand?
- Reports and dashboards
- Stays in your current system
- Whatever your system reports today
- FreighAI adds
- Nothing. Reporting stays where it is
- Decision required
- Which numbers must still come from your system?
- Warehouse, fleet and customer portals
- Stays in your current system
- Stock and bays, trips and vehicles, and any customer portal
- FreighAI adds
- Answers on the thread, for the customers who write in instead
- Decision required
- Who approves that answer, and where is it recorded?
- The enquiry, the chase and the reply
- Stays in your current system
- Nothing today. This part lives in email, WhatsApp and one person’s head
- FreighAI adds
- FreighAI works out what each email is and what it needs, then takes the action that message calls for. Follow-ups, chasers and reminders happen on their own, on the same conversation.
- Decision required
- Which mailbox starts the workflow, and who owns each step?
- Where your team works
- Stays in your current system
- Your current screens, for the record
- FreighAI adds
- Your people work in FreighAI, not in the inbox.
- Decision required
- Which screen does each role open first?
Nothing in the second column has to move for the first workflow to start.
Keep and coexist, stage the replacement, or migrate
Three decisions, three triggers. Nothing here makes migration the default, and nothing makes it wrong.
Keep it, and let FreighAI work alongside it
Choose this when the system still holds the records honestly and what hurts is the work around it. It is the common case. Coexistence needs a boundary, not a project: one workflow, one mailbox, one owner, one measure. Keep your TMS for the records. FreighAI runs the work around them.
Stage the replacement, one piece at a time
Choose this when parts of the system have to go, but not all at once. Microsoft’s architecture guidance describes incrementally migrating a legacy system by replacing specific pieces of functionality, and says both systems have to coexist and communicate while that happens. It is equally clear about where staging does not fit, such as when the original has to be decommissioned quickly.
In freight terms, staging starts where coexistence starts. The work moves first. The records move last, because they carry the obligation.
Migrate to a new system
Choose this when replacement is justified on its own. The supplier no longer supports the software. The business has changed shape and the data model cannot follow. Or an obligation cannot be met where you are.
The support trigger is not an operations decision. The National Cyber Security Centre says obsolete products no longer receive security updates, and that the only fully effective way to remove that risk is to stop using the product. That belongs on the security agenda, on its own timetable.
Six months of managed work also writes the replacement brief for you. Every workaround FreighAI takes over becomes a requirement with a volume and an owner. Martin Fowler, who named the staged pattern, warns that a replacement looks easy to specify until somebody has to describe how the current thing behaves. By then, you can describe it.
Is the system still the honest home for the records?
FreighAI takes the email and the work behind it. Nothing else changes.
The work moves first. The records move last, because they carry the obligation.
Unsupported software, or a data model that cannot follow the business. Its own project, with its own plan.
What has to be available before the first workflow starts
A first workflow needs less from an old system than people expect, because the work being taken over never reached it.
| What is needed | Why | If it is not there |
|---|---|---|
| A mailbox | The workflow starts where the work arrives | This is the one thing that cannot be worked around |
| Your rate cards, in whatever form they exist | So a quote is priced without waiting on anybody | The lane goes to your agents, and the RFQ and the chasing are run for you |
| Somewhere for the approved result to land | So the record does not end up in two places | Then where it lands is part of what we scope with your team |
- A mailbox
- Why
- The workflow starts where the work arrives
- If it is not there
- This is the one thing that cannot be worked around
- Your rate cards, in whatever form they exist
- Why
- So a quote is priced without waiting on anybody
- If it is not there
- The lane goes to your agents, and the RFQ and the chasing are run for you
- Somewhere for the approved result to land
- Why
- So the record does not end up in two places
- If it is not there
- Then where it lands is part of what we scope with your team
Notice what is not on that list. No data migration, no schema change, no upgrade of the old software, and no connector claimed because a system was discussed. We scope the first workflow, integration requirements and implementation plan with your team. There is no universal timeline. Nobody can date this work before those three rows are answered.
The objections we hear most
Our system is old but it works. Why change anything?
You may not need to. What changes here is not the system. It is the work that never reaches it. If the only way you have found to handle more of that work is to hire more people, start there.
Should we not fix the system first?
That order sounds right and often costs a year. The work you want back is not in the system, so a new one does not return it.
Is this just one more place to look?
Your people work in FreighAI, not in the inbox. The task, the thread and the drafted reply sit on one screen. If your team ends up opening two places for one task, the design is wrong.
Our system has no interface anyone can connect to. Does that stop this?
Usually not for a first workflow. Reading a thread, finding the rate, drafting the reply and assigning the task do not touch the old system. Where the approved result belongs, and who carries it there, is answered in scope.
We have been told we must migrate before we can use AI agents.
You can keep the system you run today and add FreighAI around it, or move on from it and let FreighAI be your main system. Start with pricing and operations either way, and add the rest when you are ready. Anyone who states the sequence before seeing your work is selling the sequence.
Common questions
Is FreighAI a replacement for our current freight software?
No. FreighAI takes the email and the work behind it. Where the record lives stays your decision.
Our supplier no longer supports the software. Does that change the answer?
It changes the urgency and moves the decision to a different table. Unsupported software is a security question before it is an operations one, and the national guidance quoted above answers it. Taking the work off your people is worth doing alongside that.
Do we have to move our history?
Not for a first workflow. What FreighAI needs about a customer can be given to it or shown to it. A broader move of history belongs to a migration and gets its own plan and validation.
Can we switch the old system off once the new work is running?
Only when the records inside it are no longer needed where they are. Records for traded goods declared to HMRC must be kept for four years, and other countries set their own. Most businesses keep the old system readable for that period, or export the records first and prove the export is complete.
What if we replace the system next year?
That is a boundary question: which system holds the record, and where the approved result lands. We scope the first workflow, integration requirements and implementation plan with your team. The same conversation happens again, with the new system in it.
- Microsoft Azure Architecture Center — Strangler Fig pattern: incremental migration, coexistence, and when it does not fitverified 2026-09-03
- Martin Fowler — Strangler Fig Application: why gradual replacement beats a single cut-oververified 2026-09-03
- National Cyber Security Centre — Obsolete products: software that no longer receives security updatesverified 2026-09-03
- GOV.UK — Archiving your trade documents: HMRC-declared traded-goods records kept for four yearsverified 2026-09-03
- Infinity Logistics customer reference, 15 May 2026 — response time and win rateverified 2026-08-31
No system is named as legacy here, and no vendor’s product is described. No replacement-project failure rate is repeated, because the figures in circulation cannot be traced to a datable source. The retention period quoted is one country’s.
Bring a thread and a workaround.
Pick one real email thread from last week and the spreadsheet or chat that goes with it. We will map what stays in your system, what FreighAI would read, draft and chase, and where your team approves.