Cluster ABM for ports, terminals and yards
Port and terminal software has one of the smallest, most connected buyer universes in B2B. Operations directors know each other, attend the same events and call each other before choosing a vendor. That makes classic volume lead generation counterproductive and account-based programs the natural fit.
For an anonymous North American company selling yard and port management systems, we built $8M pipeline in 9 months. The first decision was focus: mid-segment ports, where the product could win against large suites. The second was structure: cluster ABM across Dubai, the Netherlands, the US and Canada, so each region had a coherent list, message and set of references.
Inside each cluster, engagement came from formats operators value. Closed-door CXO roundtables let peers discuss congestion and automation without a sales pitch. Simulations showed what the system would do on a real yard. A proof of concept turned interest into evidence the CFO could approve.
Clusters also make events more productive. When a roundtable in Rotterdam or Dubai brings together operators facing the same congestion or automation questions, the conversation is richer, and your team can follow up with a shared set of insights instead of a generic deck.
- Cluster by asset type, size and region, not by generic industry codes
- One roundtable topic per cluster, grounded in an operational problem
- Simulations built on the prospect's layout and volumes
- POC scope agreed with operations, IT and finance before kickoff
- Follow-up content shared across the whole cluster after each roundtable
Reference customers travel further than you think
Logistics buyers want to know who else trusts you. Most vendors assume that reference has to come from the same country and the same asset type. In practice, a credible reference from an adjacent operation often opens doors across borders.
KNNX, formerly DLT Labs, had no funnel when we started. We built GTM, the website, ABM and webinars from scratch, and the company generated $12M pipeline in 28 months. A leading Canadian retailer as a reference customer helped win one of Dubai's largest port operators, followed by Dubai rail and transport companies. The story that mattered was operational: what changed, how quickly and with what integration effort.
We package references so they can be used at every stage: a short story for outreach, a detailed case for evaluation, and a peer call for the final decision.
References work best when they are specific about implementation. Operators want to know how long integration with their terminal operating system or ERP took, what changed for staff on the ground and what the customer would do differently. Honest detail is what makes a reference credible across borders.
- Lead with the operational outcome, not the customer logo
- Match references on problem and complexity, not only geography
- Offer peer calls late in the cycle, when they carry the most weight
- Refresh references with new metrics each year
Designing a proof of concept that ends in a contract
Pilots are where logistics pipeline goes to stall. The operator agrees to a trial, the vendor commits engineers, and months later the champion has moved on or the budget has been reallocated. Most of this is preventable in the first meeting.
A good POC charter names an executive sponsor, a small set of measurable outcomes, the data and integrations required, a fixed duration and a decision date with the commercial terms that follow success. It also involves procurement early, so the contract is not a new negotiation once the pilot works.
Marketing has a role here too. Sharing progress with the wider buying committee, preparing a business case template and lining up a reference call for week six keep momentum when operations get busy.
It also helps to plan for success from the start. If the pilot meets its goals, what does rollout to other terminals, yards or sites look like, and who pays for it? Answering that before kickoff turns a successful pilot into a contract instead of another round of approvals.
- Sponsor, success metrics and decision date written down before kickoff
- Commercial terms for success agreed before the pilot starts
- Midpoint review with finance and IT, not only operations
- A reference call scheduled for the second half of the pilot
- A rollout plan for additional sites agreed as part of the POC
Supply chain technology terms, defined
Supply chain software categories overlap, and buyers use operational terms that vendors sometimes misuse. These definitions help shape positioning, account clusters and content for logistics, yard, port and terminal software.
- TMS (transportation management system): software for planning, executing and optimizing freight movement.
- WMS (warehouse management system): software that manages inventory, picking and operations inside a warehouse.
- YMS (yard management system): software that tracks trailers, containers and moves in the yard between gate and dock.
- TOS (terminal operating system): the core system that runs container terminal operations.
- 3PL (third-party logistics provider): a company that runs warehousing, transport or fulfillment for shippers.
- Supply chain visibility platform: software that tracks shipments and inventory across carriers and partners in near real time.
- Detention and demurrage: charges for holding containers or equipment beyond agreed free time.
- Truck turn time: the time a truck spends inside a terminal or facility from arrival to departure.
- Gate automation: technology that speeds and records entry and exit at terminals and yards.
- Proof of concept (POC): a scoped pilot proving the software works in the operator's environment against agreed metrics.
- Cluster ABM: account-based marketing aimed at a group of similar operators that share a problem, region or asset type.
Common mistakes when marketing logistics and port software
Supply chain technology companies often borrow playbooks from horizontal SaaS, and those playbooks break against a small buyer universe, operational risk and long pilot cycles. The mistakes below appear repeatedly in logistics, yard, port and terminal software marketing, and each one can cost a year with a target account.
The alternative is research-led, cluster-based and patient. See the yard and port software case study and our account-based marketing service.
- Running volume outbound against a list of a few hundred operators and poisoning it for a year.
- Leading with software features instead of throughput, turn times, utilization and safety.
- Using references from the wrong kind of operation, so prospects dismiss them as irrelevant.
- Starting pilots without a sponsor, success metrics, decision date and commercial terms agreed.
- Reviewing a pilot only with operations while finance and IT stay uninvolved.
- Exhibiting at large shows without pre-booked meetings with named operators.
- Ignoring mid-segment ports and terminals that most vendors never contact.
- Expecting horizontal SaaS timelines from buyers who need capex approval.
- Skipping simulations built on the prospect's own layout and volumes, which are often what convince operations leaders to take the next step.
- Letting follow-up from a roundtable stay with one attendee instead of sharing it across the whole cluster.