The complete guide to logistics CRM for freight forwarders.

What a logistics CRM has to do for a forwarder

The generic model is worth reading in its owners’ own words. Salesforce describes CRM as “a system for managing all of your company’s interactions with current and potential customers”. Microsoft’s documentation for Dynamics 365 Sales sets out the process underneath: 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 — “a deal you’re ready to win”, in Microsoft’s phrase — carries an estimated revenue, an estimated close date and a probability (both sources checked September 2026).

Read that as a forwarder and the mismatch is plain. One deal, one amount, one date, once. A customer might send you forty enquiries a year, each priced on its own, and a customer you have shipped for since 2019 is still a fresh fight on every new lane. There is no close date. There is next Tuesday. The rest of this guide covers both halves of the answer: what the CRM has to hold, and the sales discipline it exists to support.

The market: 40,000 firms, hand-to-hand

Sit with those numbers for a moment. In a market where the ten biggest firms control a sliver of the spend, there is no “default vendor” a shipper falls back to. Every customer you have was won by somebody, and every customer you want is currently being served by somebody who can lose them. Fragmentation means the game never ends — and it is played hand-to-hand.

Walk any forwarding market — Nhava Sheva, Jebel Ali, Rotterdam — and the selling you find is owner-led and face-to-face: the founder in the car, visiting shippers, drinking the tea, quoting the lane. There is no reliable statistic for this and we will not invent one; if you run a forwarding business you already know it, because it is your Tuesday. The honest question this guide answers is not how to replace that motion — it is how to give it a memory, a queue and a scoreboard.

Why CRMs fail forwarders

Forwarders buy CRMs in two flavours and get failed by both. The first flavour is the generic CRM — capable, polished, and shaped for someone else’s business. It has no native idea of an enquiry that arrives as an email and must become pipeline, a quote that needs chasing before its validity lapses, a win that is not a win until credit terms and a billing contact exist, a customer that graduates from lead to prospect to account, or wallet share measured in invoiced shipments. All of that becomes custom fields and discipline — and discipline is exactly what a tool is supposed to supply, not demand.

The second flavour is the TMS-module CRM — the contacts tab bolted onto the operations system. It fails the opposite way: it is a passive record. It stores what happened and never asks what should happen next. Nobody hunts from it, because it was never built to hunt from.

The distinction that matters is filing cabinet versus queue. A filing cabinet answers “what happened with this account?” A queue answers “who do I call this morning, and why?” Both flavours above are filing cabinets. Forwarder sales lives or dies on the second question — and a CRM that cannot answer it gets abandoned, quietly, by the reps it was bought for. The full comparison is on vs generic CRM.

Both flavours share a third failure, upstream of everything else: where the work arrives. In forwarding, the enquiry, the agent’s rate reply, the push-back on price and the booking confirmation all land in a mailbox. 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. The pipeline on the screen runs a week behind reality, and the best seller on the floor is punished most by the typing. Sales teams do not abandon a CRM because they dislike software. They abandon it because it asks for the work twice.

Broker CRM vs forwarder CRM

This matters because “freight CRM” searches are dominated by the US brokerage cluster — a bigger, louder software market solving a genuinely different trade. Before comparing features, check which trade the tool was built for:

If you forward freight, a broker CRM is the wrong shape no matter how good it is — and vice versa. The line-by-line version of this argument lives at vs freight broker CRM.

Queue building from trade data

Queue building is prospect list building done so that the output is a working queue, not a spreadsheet. The raw material is trade data — bill-of-lading and customs records that show which companies actually move which freight. The method: pick the lanes where you have rates and agents, pick the HS codes for commodities you know how to handle, and pull the shippers and consignees already moving that freight. You are not guessing who might ship; you are reading who does.

How big should the list be? The working guidance is 150–500 accounts per hunting motion — large enough to survive the attrition of wrong numbers and wrong-fit prospects, small enough that every account can actually be worked on a cadence instead of admired in a spreadsheet.

The last step is the one most teams skip: getting the list off the spreadsheet. A CSV import with column auto-detection and duplicate checks against your existing customers turns 300 rows into 300 pipeline cards with owners — and the moment a card exists, its first-touch clock is running. That is the difference between a list and a board: a list waits for motivation; a board starts counting.

Cadence: the follow-up discipline

The first rule of cadence is verified and dramatic: touch new leads fast. The MIT/Oldroyd Lead Response study found that calling a lead within 5 minutes rather than 30 raises the odds of making contact roughly 100-fold. Harvard Business Review’s 2011 audit found firms that contacted a lead within an hour were about 7× more likely to qualify it than those that waited even an hour longer. Speed is not a nicety; it is the single most leveraged act in the sales week.

The second rule is that nobody sustains speed on motivation. What sustains it is a policy that a machine enforces: first touch within N days, a touch every N days after that, cold after N days of silence, and a closing-soon window for deals with real close dates. From those four numbers, every prospect gets a visible state — and the queue ranks itself every morning.

Note what is deliberately absent: a score. The Focus Engine is rule-based because a rule you set is a rule you can read, argue with and change — and a ranking reps can argue with is a ranking they will actually follow.

Quote follow-up: the broken middle

Between the pitch and the win sits the quote — and the quote is where forwarder sales quietly breaks. A Freightos mystery-shopper study found that 60% of quote requests were never quoted at all, and of the forwarders who did quote, only 8% followed up afterwards (secondary source: the study as reported via Quotiss). Read that as a market-level confession: the industry’s most expensive sales artefact — a priced, lane-specific offer — is usually sent into silence and left there.

The fix is structural, not motivational. In a follow-up queue seeded by next actions, every logged activity ends with an outcome and a next action with a date. When the date arrives, the follow-up surfaces in the queue; when it passes, it escalates. Follow-ups can also arrive from playbooks and automatic events, not just rep memory — and they can be snoozed with a reason instead of silently dropped. The quote you sent on Tuesday stops depending on what a rep happens to remember on Friday.

The hand-off: sales to pricing to finance

Between the enquiry and the cash, one customer conversation crosses four desks — and the CRM usually sees only the first of them:

• Sales brings the enquiry.
• Pricing builds the number — a rate card, a carrier, or four agents emailed and three of them chased — and somebody approves the margin before the quote goes out.
• Operations books the space and opens the job if the quote is won.
• Accounts invoices it, then chases it.

A standalone CRM typically holds 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. 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 re-typing happens one step earlier, between the quote and the booking, and again at the win, between sales and finance.

This is where the CRM’s location matters more than its feature list. SalesCRM AI runs in the same FreighAI workspace as the quotes, job orders and invoices, so a follow-up or an email thread is linked to the quotation, job order or invoice it concerns, and a win hands finance its terms through the activation gate described in the next section — rather than through a forwarded email.

Wallet share: where the money is

The strongest dataset in forwarder sales says the hunt does not end at the first win — it compounds after it. WebCargo/Freightos analysed 500,000 quotes in 2025 and found existing customers win at 22.7% versus 13.4% for new ones — and the curve inside that number is steeper still:

The path from new to existing nearly doubles your win rate, and each additional quote deepens the groove. The strategic conclusion: the second quote to an existing customer is a better bet than the first quote to a stranger — which makes farming a hunting strategy, not a retirement from it. 3PL sales practice recognises this as the hunter-to-farmer handoff, by convention somewhere around three to six months or ten shipments in.

Operationally, wallet share needs two things a generic CRM cannot give you. First, a lifecycle — lead to prospect to account — so a customer’s graduation is a recorded event, not a feeling. Second, a Book of Business built from invoiced revenue: because the CRM sits on the same platform that raises the invoices, wallet share is reported from billing data, per account and per account owner — not from self-reported CRM optimism.

And the lever that opens the wallet is often not price — it is credit terms. Net 30, net 60, net 90 are standard competitive weapons in forwarding, which is why winning a deal here opens an activation gate: contract document, credit limit, payment terms, billing email — captured while the handshake is warm, so finance inherits an account rather than an anecdote. (The policy and collections side of credit control belongs to sibling receivables-ai.com; terms as a sales lever are this site’s ground.)

Manager discipline: forecast & coverage

Everything above is rep discipline. It survives only if the manager’s view enforces it — and the manager’s view is four instruments:

• Targets. Per rep, as revenue or won-deal count, monthly or quarterly. A number a rep didn’t agree to is a number a rep won’t chase.
• Probability-weighted forecast. Every stage carries a win probability; the open pipeline weights against it and lands next to the target. Attainment is a fact on a board, not a mood in a meeting.
• Funnel and stage velocity. Where deals convert, where they stall, and how long each stage really takes — the difference between “we need more leads” and “we lose everything at proposal”.
• The coverage snapshot. Per rep: how many accounts never contacted, how many overdue, how many going cold. This is the question that actually matters on a Monday — whose book is quietly going cold?

The forecast tells you whether you will make this quarter. The coverage snapshot tells you whether you will make the next one — because neglect shows up in coverage months before it shows up in revenue. Most CRMs give managers the first instrument and call it reporting; the honest ones give them the fourth.

What automates, what stays human

The dividing line worth drawing: software should do the remembering, ranking and transcribing; humans do the relationship and every confirmation. Applied to the workflow in this guide, that means five automations:

• The queue ranks itself. The Focus Engine applies your cadence policy and surfaces the day’s work — never-contacted, overdue, going cold, closing soon — with the rule behind every ranking visible.
• The brief arrives before the rep does. The day’s brief is prepared overnight and sent on WhatsApp — the calls to make and the drafts waiting — so a salesperson reads their day without logging in.
• One voice note becomes the record. The rep speaks the debrief from the car; Whisper transcribes it, a conversational assistant asks the gaps one question at a time — outcome? next step? stage change? — and the activity is logged, the quote request created, the follow-up set and the rate card pulled. The rep confirms before anything posts.
• RFQs become leads. Inbound RFQ emails turn into pipeline cards automatically, assigned to the default owner, first-touch clock already running — before any human has read the inbox.
• Documents get checked. At activation, AI validates the credit application and contract documents against what was captured and raises mismatch flags as corrective actions — before finance finds them the hard way.

Equally deliberate is what is not automated: no black-box lead scores, by design. A score nobody can explain is a score reps learn to ignore; a rule everyone can read is a rule the whole floor can trust. The judgment calls — what to say, when to visit, whether to offer terms — stay exactly where they were.

The prize is time. Salesforce’s State of Sales research puts actual selling at 28% of a rep’s week; the rest is admin, data entry and searching. The point of the automations above is not to automate selling — it is to hand those hours back to it. The step-by-step flow is on how it works, and your own numbers go through the calculator.

How to evaluate a logistics CRM

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

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, your current prospect list, 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, and open the record it created an hour later. What the record looks like cold tells you more than the demonstration did.

Getting started: a scoped start

We scope the first workflow, integration requirements and implementation plan with your team. The stages are named, not timed — and they begin with the list you already have:

• Discover. One session on your own material: the prospect list your sales manager keeps outside the CRM, one enquiry you won and one you lost, and the cadence numbers your desk already works to.
• Design and configure. Import your prospect list — CSV with column auto-detection and dedup against existing customers — configure your pipeline stages, and set the four cadence numbers: first-touch days, touch cadence, cold-after, closing-soon window.
• Validate. Reps open the ranked queue each morning and work the top of it; touches get logged by voice on the drive back, each ending in an outcome and a next action that seeds tomorrow’s queue.
• Implement and expand. Set targets per rep, watch the probability-weighted forecast build against them, and run the first coverage review: whose book is going cold, and what does this week do about it?

Measure success in your own operation, on numbers you can see: time to first touch on new leads, overdue follow-ups trending toward zero, quotes that got a call instead of silence — and, a quarter out, wallet share moving on accounts you already had.

Questions buyers ask

Is a logistics CRM the same as a freight CRM? In practice, yes. Forwarders use “logistics CRM”, “freight CRM” and “freight forwarding CRM” for the same thing: a sales system shaped around enquiries, quotes, repeat shipments and credit terms rather than one-off deals. One caution: “freight CRM” searches are dominated by CRMs for US truckload brokers, which are a different product for a different trade.

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, at typical win rates, is most of them — and the losses are where the useful information is. It also stores what happened without asking what should happen next, so nobody hunts from it.

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 the steps on one real enquiry, from the email arriving to the follow-up being scheduled, and on one site visit, from the car park to the logged activity.