FreighAI
FreighAI · Guides
Guide

What should a logistics CRM do for a freight forwarder?

Most CRM products are built around a deal that is worth an amount and closes on a date. Freight is not sold that way. Your customer ships every week, every shipment is priced on its own, and the same lane has to be won again next month.

This guide separates what a general CRM gives you from what a freight forwarding business needs. Use it to write your requirement before you look at any product, including ours.

The short answer

A logistics CRM has to fit how freight is really sold. The pipeline is quotations, not deals. The segment is a lane, not an industry. The enquiry arrives by email and the win is a booking. Judge a product on those four things, not on contact management. Then ask what happens before anyone opens the mailbox.

Why does a generic CRM struggle in a freight forwarding business?

Because the record at the centre of it is the wrong shape.

Salesforce describes CRM as “a system for managing all of your company’s interactions with current and potential customers”, one that lets you “store customer and prospect contact information, identify sales opportunities, record service issues, and manage marketing campaigns” (checked September 2026). All of that is useful to a forwarder.

Underneath it sits a sales process. Microsoft’s documentation for Dynamics 365 Sales sets it out plainly: a lead becomes an opportunity, the opportunity becomes a quote, an agreed quote becomes an order, and the order becomes an invoice, through stages named Qualify, Develop, Propose and Close. The opportunity is where the money lives. Microsoft calls it “a deal you’re ready to win”, carrying an estimated revenue, an estimated close date and a probability.

Read that as a forwarder and the mismatch is obvious. One deal, one amount, one date, once. Your customer sends forty enquiries a year, each priced on its own, most decided within the hour. A customer you have shipped since 2019 is still a fresh fight on every new lane. There is no close date. There is next Tuesday.

Four things are shaped differently in freight:

  • the pipeline is quotations, not deals;
  • the segment is a lane, not an industry;
  • the enquiry arrives in a mailbox, not on a form; and
  • the win is a booking, not a signature.
Generic CRM · Freight CRM
Both products
What both hold
Companies and the people inside themEvery conversation, against the customerAn owner for each accountWhat was won and what was lost
Built around one deal at a time
Generic CRM
  • A lead that converts into an opportunity
  • Estimated revenue and a close date
  • Stages: Qualify, Develop, Propose, Close
  • Products taken from a price list
Built around repeat priced movements
Freight CRM
  • An enquiry priced for one shipment
  • Rates by lane, commodity, service and validity
  • Quote versions, and the line that changed
  • A won quote that becomes a booking and a job
Where a generic CRM and a freight CRM agree, and where each one is built differently.

What is the pipeline in a forwarding business?

It is the quote list. Nothing else comes close.

A pricing desk can send more quotations in a week than a general CRM expects a seller to open in a quarter. If each has to be typed into a deal record afterwards, nobody types them, and the pipeline on the screen is fiction within a month. So the first test is not what the record holds. It is whether the record appears without anybody creating it.

A freight quotation is a denser object than a proposal. It carries origin and destination, mode and service, weight, volume and dimensions, the commodity, the incoterm, the readiness date, the rate and where it came from, the charges either side of the main leg, and the date the price stops being valid.

The regulator makes the point from outside the software market. A US ocean service contract must state its origin and destination port ranges, “the commodity or commodities involved”, “the minimum volume or portion”, “the line-haul rate”, and its effective and expiration dates (46 CFR §530.8, checked September 2026). Lane, commodity, volume, rate, validity: that is the commercial unit here, and a record holding a company, a contact and an amount cannot carry it.

Enquiry to won booking
    1. 01EnquiryOrigin, destination, weight and commodity, in a mailbox.
    2. 02QualifyWork out what is missing, and ask before pricing.
    3. 03RatesYour rate card, a carrier, or an RFQ out to agents.
    4. 04PriceMargin rules, and what this customer paid before.
    1. GATEApproveA person checks the price before it goes out.
    2. 06Quote sentOn the customer’s own thread, with a validity date.
    3. 07Follow upChase, counter, expire or revive.
    4. 08BookingWon. Space is booked and the job is opened.
The commercial run every forwarder makes. The amber step is where a person decides.

How should a freight CRM segment your customers?

By lane and trade route, before anything else.

A general CRM segments by industry, company size, region or campaign source. Those are the right handles when you sell one product to everybody. They are useless when the Tuesday morning question is “who else ships Nhava Sheva to Rotterdam in October, because I have space”.

Two customers in unrelated industries with the same lane are the same commercial opportunity to you. They fill the same container and are hurt by the same rate increase. The Federal Maritime Commission describes the job in those terms for a forwarder located in the United States: an ocean freight forwarder “arranges cargo movement to an international destination” and “books or otherwise arranges space for those shipments on behalf of shippers” (checked September 2026). Space on a route is what is sold, so the route is the natural segment.

A lane-aware CRM should answer these without an export:

  • which customers ship this lane, and how often;
  • what we quoted on it in ninety days, and what we won;
  • which lanes we lose on price, and which on transit time;
  • where we have space or an allocation still to fill; and
  • which agent priced the lane last time, and how long they took to answer.

None of that is exotic analysis. It is the freight version of “show me my pipeline”. A product that cannot group by lane hands the work back to your sales manager, who rebuilds it in a spreadsheet every month.

Where does the work arrive, and what does that cost you?

In the mailbox. All of it.

In a forwarding company, the work arrives as email. Enquiries. Rate replies from agents. Booking confirmations. “Where is my cargo?” Carrier bills. Payment chasers. Someone has to open each one, work out what it is, find the information, write the answer, pass it to the next person, file it, and remember to chase. The inbox is where your company actually runs. And the inbox does nothing to help.

A CRM outside that flow becomes a second job. Somebody opens the mail, does the work, then goes to another screen to say what they did. Two things follow, both expensive. The pipeline is permanently a week behind what is really happening. And the person best at selling is punished most by the typing.

The adoption problem

Sales teams do not abandon a CRM because they dislike software. They abandon it because it asks for the work twice.

How do sales and pricing hand off to each other?

Badly, in most companies, and the CRM usually cannot see it.

  • 01A salesperson brings the enquiry.
  • 02The pricing desk builds the number, which may mean pulling a rate card, checking a carrier, or emailing four agents and chasing three of them.
  • 03Somebody approves the margin.
  • 04The quote goes out.
  • 05If it is won, operations books the space and opens the job.
  • 06Accounts invoices it, then chases it.

Most CRM products hold only the first step. The quote lives in a spreadsheet or a quoting tool, the booking in the TMS, the invoice in accounting. The customer sees one company. Four systems see four fragments, and a person carries the work between them by forwarding email.

The re-keying is a recognised industry problem. The Digital Container Shipping Association describes its booking standard as reducing “the need to rekey booking information in the Shipping Instructions” (checked September 2026). The same thing happens one step earlier, between the quote and the booking, and nobody has standardised that away.

Four layers, one conversation
Layer 01The inbox and WhatsApp

Where the enquiry, the agent’s rate reply, the push-back on price and the booking confirmation arrive.

Layer 02The quoting desk

Rate sources, margin rules, versions, validity and the price that goes out.

Layer 03The CRM record

The customer, the lanes they ship, what they paid before and what is still open.

Layer 04The system of record

The job, the booking, the documents and the invoice. Usually a TMS or accounting system.

One conversation runs through all four. A person approves the price.
Ask any product to show one enquiry crossing all four layers, and ask who types what at each crossing.

What must a logistics CRM hold that a general one does not?

Six things. Ask to see each one on a real record, not a slide.

1. The enquiry in shipment terms

Origin, destination, mode, service, weight, volume, dimensions, commodity, incoterm and readiness date, held as fields rather than pasted into a notes box. When an enquiry is incomplete, the system should know which field is missing and ask for it.

2. Rates, and where each one came from

A price from your rate card, a price read from a carrier and a price an agent emailed back are three kinds of number with three shelf lives. A record that flattens them into one field loses what you need when the customer pushes back.

3. Quote versions and an expiry date

Freight prices move. A third version is normal, and the useful record shows which line changed. A price nobody answered should expire rather than sit in the pipeline pretending to be live.

4. Lane history for this customer

What they paid on this lane last time, what you have quoted since, and what you won and lost. This is the most valuable field a freight CRM holds, and the one a general CRM has nowhere to put.

5. The hand-off to operations

A won quote should reach operations as a job with the detail already in it, not as a forwarded email. Ask what is created the moment the customer says yes, and who has to type it.

6. Money, seen from the sales desk

Credit status and overdue invoices belong on the customer record. A salesperson should know before promising terms, not afterwards. A product holding none of these six is a contact database with a freight logo on it.

How should you evaluate one?

With the same questions for every supplier, asked against your own work rather than their demonstration data. Two decide most of it.

Question one

Does your team still have to open the mailbox?

A good answer is not “we integrate with email”. It shows the reply, the record and the owner all existing before anybody opened the message. If the demonstration begins with a person reading an email and clicking a button, that is what your Monday will look like too.

Question two

What runs by itself?

Chasing an agent who has not replied. Expiring a quote. Nudging a proposal that has gone quiet. Ask which of those happen with nobody remembering them, then ask to watch a week of them in a log.

Ask every supplier the same questions, on your enquiry rather than theirs.
  1. Enquiry capture
    What to ask
    Show an enquiry we forward you now becoming a priced quote
    What good evidence looks like
    A live run on our material, not a prepared record
  2. Rate sourcing
    What to ask
    Where does the price come from when the lane is not on our rate card?
    What good evidence looks like
    Separate handling for rate cards, carriers and human replies
  3. Quote versions
    What to ask
    Show version three of a quote and the line that changed
    What good evidence looks like
    A version history on the record itself
  4. Lane view
    What to ask
    Show every quote on one lane for one quarter, won and lost
    What good evidence looks like
    Grouping by lane inside the product, not an export
  5. The mailbox
    What to ask
    Does your team still have to open the mailbox to do the work?
    What good evidence looks like
    The reply, the record and the owner exist before anyone reads it
  6. What runs by itself
    What to ask
    Which chasers and checks happen with nobody remembering?
    What good evidence looks like
    A week of them, in a log we can read
  7. Hand-off
    What to ask
    What does operations receive the moment a quote is won?
    What good evidence looks like
    A job or booking created with the detail already in it

Two products can both answer yes to “do you have quotations”. One means a document template. The other means rate sourcing, margin rules, versions and expiry. That detail shows up only when you make them run your enquiry.

What does an AI-led freight CRM look like in practice?

One example, and it is ours, so read it as a specimen rather than a recommendation.

FreighAI’s Sales CRM describes itself as an AI-led CRM for SME freight forwarders. Its own page states six things. The day’s plan is built overnight and arrives on WhatsApp with no login. The ranking explains itself, naming the funnel gap, the week’s priority and the lead’s pattern. A salesperson can ask for a customer’s history and get back won deals, the last RFQ and the lane. A voice note after a meeting logs the activity and creates the quote request. Quiet leads and stuck proposals are surfaced with the next move drafted. A manager gets one Friday page of the deals needing sign-off.

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.

On the quoting side, the mechanics this guide has been describing are the ones the platform runs. Suggests a price from what that customer paid on that lane before, within your margin rules. Every version of a quote is kept, and the line that changed is shown. Quotes expire on their own and can be revived if you want. A won quote becomes a job on its own, fully filled in.

Your team approves. They do not compose, forward, file or chase. The reply goes out in their name. FreighAI is an AI-first freight operations platform that can run standalone or work alongside an existing TMS or ERP. It does not require a forced replacement.

Some things stay in the systems you already run: statutory books such as bank reconciliation, accruals and provisions, customer self-service portals, direct customs filing and duty or HS lookup, and full warehouse and fleet management. We scope the first workflow, integration requirements and implementation plan with your team.

What should you bring to the evaluation?

Bring the work, not a requirements document.

  • one enquiry from last week that went smoothly, and one missing half the detail;
  • one you lost, and what you believe you lost it on;
  • the quote you sent for each, with the rate source behind it;
  • three months of quotes on one lane you quote often and win rarely; and
  • the spreadsheet your sales manager keeps outside the CRM, because that spreadsheet is your real requirement.

Then ask the supplier to work on your material while you watch. Afterwards, open the record it created and read it cold. What the record looks like an hour later tells you more than the demonstration did.

Where this shows up in FreighAI
Questions

Common questions

01

Is a logistics CRM the same as a freight CRM?

In practice, yes. Buyers use “logistics CRM”, “freight CRM” and “freight forwarding CRM” for the same thing: a customer system that understands shipments, lanes and quotations rather than generic deals. What matters is whether it holds a rate, a validity date and a lane history.

02

Can we just use our TMS as our CRM?

A TMS holds the job after the business is won. It rarely holds the enquiry you quoted and lost, which is most of them, and the losses are where the useful information is. Put the enquiry, the quote and the lane history somewhere that can see all three.

03

Do we still need a separate quoting tool?

It depends how you get rates. If most lanes price from your own rate cards or a carrier connection, quoting belongs with the CRM record. If most need a partner agent to answer an email, the better question is who writes the RFQ and who chases it.

04

Will our salespeople actually use it?

Only if it asks for less typing than they do today. Adoption fails when a product wants the work recorded after the work is done. Count keystrokes on one real enquiry, from the message arriving to the quote going out.

05

What should stay in the systems we already have?

Statutory books, customer self-service portals, direct customs filing and duty lookup, and full warehouse and fleet management. Decide that boundary before you buy, and write down which system owns each field.

READY WHEN YOU ARE

Bring one enquiry and one lane

Send a real enquiry from last week and the lane it sits on. We will show you what the record would look like afterwards, who would have been asked to approve the price, and what would have carried on without anybody remembering.