Pipeline stages that fit freight
Stages should describe the buyer's progress, and freight has a recognisable shape. A workable starting point, adjusted to your business:
- New enquiry: a lane or need has been described but not yet qualified
- Qualified: mode, lane, volume pattern and timing are known
- Quote requested and quote sent: separate stages, because the wait for supplier prices is where deals stall
- Quote follow-up: with a defined next action and date
- Booked: the quote became a shipment
- Repeat or nurture: a shipper who ships again is a different relationship from a one-off
- Lost: with a reason, such as price, timing or lost to another forwarder
Exit criteria
Give each stage a rule for entering the next. Without it, stages describe rep activity instead of buyer progress, and reports mislead.
Lane, mode and incoterm fields
The fields that make a freight CRM useful are the ones a generic CRM does not ship with. Decide which you genuinely use and keep the list short.
- Origin and destination (as structured values, not free text, so you can filter by lane)
- Mode: sea, air, road, or combinations
- Cargo type and rough volume or container type
- Incoterm, since it changes what you are quoting
- Frequency: one-off, occasional or regular flow
- Target ship date or booking window
Repeat shippers and lane history
Much freight revenue comes from shippers who ship again. An account record should show their lanes, the quotes you have sent and what became bookings, so a salesperson opening it sees the relationship, not a blank contact. This is also how you spot lapsed shippers: accounts that used to book monthly and have gone quiet. Define what quiet means for your business and create a follow-up task when an account crosses that line.
Quote-to-booking
The gap between quote sent and booking made is where freight sales leak. Track it explicitly: which quotes are open, how old they are, who follows up, and which quotes turned into shipments. If your quote assembly currently lives in emails and sheets, the freight RFQ management workflow describes how to build one record from request to accepted quote, and the CRM then links to it. The CRM should hold the sales state and the commercial outcome; where costs and supplier prices live is decided per project and does not have to be in the CRM.
Multiple contacts per account
A shipper rarely has one contact. The person who requests a quote is often not the person who approves it or receives the documents. Model contacts per account with a role: requester, decision maker, documents, invoicing. Then follow-ups go to the right person, and a change of employee at the client does not break the relationship history.
Routing enquiries
Decide who receives what: by mode, by region or language, by account owner or by size. Write the rules down, implement them, and keep a fallback owner so nothing sits unassigned. If enquiries arrive from several channels, see freight forwarder lead automation for capturing and qualifying them before they reach the CRM. General routing patterns are covered on the CRM sales workflow implementation page.
Where an existing CRM stays
You do not have to replace your CRM. In many cases the right move is to keep it and restructure it: rebuild the pipeline, add the freight fields, clean the accounts and set up the routing and follow-up rules. That is what our fixed-scope CRM Cleanup & Sales Workflow Setup package is for. A custom build or a migration is a larger, separately scoped job, and it is chosen only when the current tool genuinely cannot hold your process. Licences for the CRM itself are a vendor cost and are not part of our work.
For a comparison with another industry's setup, see CRM implementation for real estate agencies. The same approach applies: model the actual sales object, then automate around it.
Questions
Do we need a new CRM?+
Often not. Restructuring your existing CRM around lanes, modes and quote states is usually enough. A different or custom system is considered only if the current one cannot support your process.
Will you publish or store our rates and margins?+
No. We do not publish rates or margins. What your CRM holds about pricing is decided with you per project.
Can the CRM pull rates from carriers?+
Not by default. Integrations with external rate sources are scoped per project only where an API exists.
How do we handle contacts at the same shipper?+
Model several contacts per account with a role, such as requester, decision maker, documents or invoicing, so follow-ups reach the right person.
What is the smallest useful first step?+
Rebuild the pipeline stages, add the few lane and mode fields you actually filter on and set up routing and follow-up rules on your current CRM.