What is different in logistics sales
In most industries, winning the customer means winning the revenue. In logistics it only means winning the right to compete for each shipment. A customer can love your service and still move half their volume to a cheaper carrier next quarter without a phone call. Sales is therefore never finished, and the CRM has to watch the relationship, not just the contract.
The business splits into three games with different clocks. Spot and lane business closes in days or weeks, on price and responsiveness. Contracted freight and annual tenders run on a procurement calendar, with RFQ rounds, lane sheets and awards, over three to nine months. Contract logistics, warehousing and dedicated capacity behaves like an enterprise sale with site visits and solution design. One pipeline cannot honestly hold all three.
The decision maker is usually a logistics or supply chain manager, with procurement running tenders at larger shippers. Switching costs are low for freight and high for warehousing, which is exactly why the deal types deserve separate treatment.
An example logistics pipeline
This is the tender and contract pipeline we build for forwarders and carriers. The lane and spot game stays out of it.
| Stage | Exit criterion |
|---|---|
| Lane profile confirmed | Volumes, lanes and service requirements documented. |
| RFQ received | Formal request in hand with deadline and award criteria. |
| Quote submitted | Rates filed before deadline, submission confirmed. |
| Shortlisted | Invited to negotiation or feedback round. |
| Award received | Lanes awarded in writing, volumes and start date known. |
| Implementation running | SOPs agreed, first shipments booked. |
Note the implementation stage. In logistics, an award without a working operational start-up is not revenue yet, and deals genuinely die between award and first shipment. A second pipeline handles contract renewals and structured win-backs. The design rules are the same as in our pipeline design guide: stages are events the customer controls, and separate processes get separate pipelines.
The fields and automations that matter
Fields that pay their way: service type as a fixed list of freight modes and contract logistics, trade lane or region, estimated annual revenue, contract end date, tender deadline as a date, and incumbent carrier. The incumbent field is underrated. Knowing who you are displacing shapes pricing and tells you later who displaces you. Test every further field against the bar in custom fields that earn their place.
Three automations carry the operation. A tender deadline countdown that creates activities at deadline minus ten days and minus three days, because a missed RFQ deadline is a deal lost to calendar management. A contract renewal generator that opens a renewal deal six months before contract end. And the volume decay alarm described in the FAQ, fed by monthly TMS numbers per customer.
Account management needs a cadence, not just alarms. Top twenty customers get a quarterly business review as a recurring activity on the organisation, owned by name, with the TMS trend line as the agenda. The next tier gets a call every quarter. This sounds banal, and it is the discipline that separates forwarders who grow existing accounts from those who only replace what leaks.
Common mistakes
The classic mistake is turning the pipeline into a shipment log. Operational quotes belong in the TMS. The CRM tracks relationships worth winning and tenders worth filing. Mixing the two produces ten thousand tiny deals and zero insight.
The second is celebrating awards as wins. Track the implementation stage until freight actually moves, and set the deal value to what the first year will really carry, not the tender's theoretical maximum.
The third is no renewal machine. Contracted volume has an end date, and the incumbent advantage evaporates if the renewal conversation starts sixty days before expiry. Automate the six month trigger and treat the renewal as a deal that can be lost.
The fourth is ignoring the quiet churn. Logistics customers leave silently. The volume decay alarm is the cheapest early warning system in the industry, and it needs the TMS feed to exist. Data discipline around this feed is covered in data hygiene.
Questions
Should spot quotes go into Pipedrive?
Not individually. A forwarder can issue dozens of spot quotes a day, and each one as a deal would bury the pipeline. Track the relationship deal, and count spot activity as a field or a note. The exception is a spot quote that opens a new customer, which deserves a deal.
How do we model tenders with many lanes?
One deal per tender, with the total annual value on the deal and the lane detail in the TMS or a spreadsheet linked from the deal. Splitting one tender into thirty lane deals makes the pipeline unreadable and the win rate meaningless.
What deal value do we use for contract logistics?
Expected first year revenue is the convention that works. Contract logistics deals run three to five years, but first year revenue keeps the pipeline comparable across freight, warehousing and value-added services.
Does Pipedrive integrate with a TMS?
Rarely out of the box, but the API makes it straightforward through middleware. The valuable direction is TMS to CRM: shipment counts and revenue per customer pushed onto the organisation monthly, so account managers see volume trends without leaving Pipedrive.
How do we spot a customer we are quietly losing?
Volume decay. If the TMS pushes monthly shipment counts into Pipedrive, an automation can open a win-back deal when a customer drops below their normal range. In logistics, customers rarely announce a switch. The volume just moves.