Excel is the default, and that is the problem
Most forwarders run their pricing on a folder of Excel files. There is a reason: Excel is free, every employee already knows it, and a rate sheet from a carrier can be pasted in and tweaked in five minutes.
That is fine for one tariff and one rep. It quietly breaks the moment a sales team has to quote across multiple carriers, multiple modes, multiple customer-specific markups — in real time, while the customer is still on the phone or watching the email thread.
Five ways Excel quietly breaks for sales teams
1. Version drift
Three reps have three slightly different copies. The carrier issued a GRI; only one rep updated their sheet. The other two are quoting last month's number.
2. Surcharges go missing
A clean Excel rate row is just base + lane. Surcharges (BAF, peak season, GRI, FAF, free time penalties) live in a tab nobody opens. They get forgotten on the quote, then claw back margin two weeks later when finance reconciles.
3. Customer-specific markups become tribal knowledge
"For Customer A we always add 8%, except on this lane where they have a contract." That rule lives in one rep's head. When that rep is on holiday, the customer gets a different number.
4. Lookups are linear
"What's the cheapest valid carrier for Shanghai → Rotterdam, FCL 40HC, ETD next Monday?" In Excel, that is a Ctrl-F across a folder. In a real quoting engine, it is one query.
5. There is no audit trail
A customer comes back six months later asking why their quote was X. With Excel you have no idea which version of which sheet produced that number.
What "structured" actually means
The opposite of Excel is not "another spreadsheet, but online". It is a structured rate library where:
- Every tariff is stored as records, not cells: lane, mode, equipment, validity window, base rate, surcharges, free time, transit time.
- Every value links back to the source document it came from.
- Every customer-specific markup is a rule the system applies, not a memory.
- Every quote is a query, not a vlookup.
This is what Tari builds inside Freightools.ai: the carrier tariffs you already have become a queryable library, and Miles uses that library to produce quotes in seconds.
How forwarders move off Excel without disrupting sales
You do not have to migrate everything in a weekend. The realistic path:
- Pick your top five lanes. Move only those tariffs into a structured store first.
- Run dual-track for two weeks. Reps still have Excel; the new tool answers the same queries. Compare.
- Surface customer markups as rules. Write down the tribal knowledge once. Nobody has to remember it again.
- Roll out lane by lane. Excel becomes the fallback, not the source.
Within a few cycles the sales team stops opening Excel for the live lanes — not because they were told to, but because the structured tool answers the question faster.
The hidden cost nobody puts in the budget
The cost of Excel is not the license — it is free. The cost is the senior rep who spends two hours every Monday reconciling sheets, the margin clawed back when a surcharge was missed, and the deal lost because the answer took an hour and the customer had already booked elsewhere. None of those land on a line item, so they never get questioned. They just become "how forwarding works".
Add them up across a year and the spreadsheet most teams call free is usually their most expensive tool.
What breaks first as you grow
Excel does not fail evenly. It fails in a predictable order as a desk scales:
- First, version control goes — more reps, more copies, more drift.
- Then surcharge discipline goes, because more lanes means more tabs nobody opens.
- Then customer rules go tribal, because there are too many to hold in one head.
- Finally audit becomes impossible, because no one can reconstruct which sheet produced which number.
If you recognize your team somewhere on that list, that is your current ceiling — not a warning about some distant future.
What a structured rate library does that a sheet cannot
The argument against Excel is not that spreadsheets are bad — they are extraordinary for what they were built for. The argument is that a rate library is a different kind of object than a sheet, and forcing one into the other is where the failure starts.
A structured rate library treats every rate as a record with typed fields: origin, destination, mode, equipment, validity window, currency, and an explicit list of surcharges, each tied to its source document. Because the fields are typed, the system can do things a sheet fundamentally cannot:
- Expire rates automatically. A validity window is a real date range, so an out-of-date rate stops being offered instead of sitting in row 412 looking valid.
- Apply customer rules consistently. Markups, floors, and account-specific terms are encoded once and applied on every quote, rather than living in a rep's head or a hidden column.
- Answer "why this number" months later. Every value links back to the carrier document it came from, so an audit is a lookup, not an archaeology project.
- Feed other systems. Sales, finance, and the customer portal all query the same source of truth, so the number a customer sees online matches the one the rep would have quoted.
None of these are exotic features. They are the baseline you would expect from any business-critical data — and exactly the things a spreadsheet quietly cannot guarantee once more than one person is involved.
The practical test is simple. Ask how long it takes today to answer three questions: which of our rates are valid right now, what is the correct selling price for customer X on lane Y, and where did this number come from? If those take more than a few seconds each, the sheet has already outgrown its job — the data exists, it is just not structured enough to be trusted under pressure.
What you keep, what you let go
You keep: the relationships, the carrier deals, the people. None of this changes.
You let go of: the version drift, the missing surcharges, and the dependency on a single rep's memory of a markup rule.
If you want to see what your top five lanes look like in a structured library, book a demo and bring a real Excel file. We will load it on the call.