The logistics buying committee: who actually decides

Four stakeholders, one deal

A typical complex B2B purchase now runs to six to ten decision makers, each gathering information independently (Gartner). In logistics software those roles are unusually well defined, because the software touches a physical operation, a cost line and a systems estate at the same time.

The practical consequence is that the person most likely to reply to your first email is the person least able to buy. That is not a reason to target someone else. It is a reason to plan the next three conversations before the first one happens.

Operations: the pain, without the signature

Head of operations, logistics manager, fulfilment lead, dispatch manager. They live with the problem. They know exactly how many exceptions happened last week and which customer complained.

This is your champion and the reason a first meeting goes well. It is also where most deals stop, because operations budgets are usually consumed by running the operation, and a new system is capital or a new line rather than a reallocation. An operations lead can specify, evaluate, pilot and advocate. In most organisations they cannot approve.

What they need from you is not persuasion, it is ammunition. A champion who agrees with you but cannot articulate the case to finance in finance’s language will lose the internal argument to whatever else is competing for that money. Give them the numbers in their unit and the translation into finance’s unit.

Finance: the signature, without the pain

Finance has never stood on a loading dock. That is not a criticism, it is the job. They are comparing your proposal against every other request for the same money, and the operational vividness that convinced operations is not evidence to them.

What travels is the conversion of operational units into money, done explicitly rather than left implied. Cost per shipment multiplied by shipments. Expedited freight avoided. Hours of manual reconciliation removed, priced at a loaded rate. Working capital released by faster proof of delivery. Whether the saving is a cost reduction or a cost avoidance matters to them and usually does not to operations.

The common mistake is meeting finance at the end, at contracting, when the case has already been built in the wrong language. Bring them in before the pilot, because the pilot is asking operations to spend time and finance should already understand what that time is buying. A pilot finance has not sponsored is a pilot that converts badly, which is covered in why the sales cycle runs long.

IT: cannot say yes, can say no

IT almost never champions logistics software. It arrives with an integration burden into an ERP, a warehouse management system, a transport management system or a set of carrier APIs, all of which IT owns and none of which it wants to touch mid-year.

The asymmetry matters. IT has no upside from the project and carries the risk of it going wrong, so the rational position is caution. A veto arriving in month four, after operations has piloted and finance has modelled, is the most expensive way for a logistics deal to die.

Treat IT as a risk to retire early. Ask in the first or second conversation which systems this has to talk to, who owns each one, and whether that person knows the project exists. A named IT contact engaged early is usually neutral. The same person discovered late is usually an obstacle, and reasonably so.

Procurement: the timeline nobody forecast

Procurement cannot approve the purchase and can comfortably add two months to it. Vendor onboarding, security review, insurance and liability, data processing terms, sometimes a competitive tender that has to be run whether or not the decision is already made.

In larger shippers and 3PLs this is a formal process with its own queue, and it is frequently the difference between a deal landing this quarter and next. It is also the most forecastable delay in the whole cycle, because the steps are published and someone in the buying organisation knows them.

Ask early and specifically: what is the vendor onboarding process, how long has it taken for a comparable supplier, and does anything about our size or location complicate it. The answer costs one question and removes a recurring forecast surprise.

Sequencing the deal

• Start with operations, because they have the pain and will actually reply. Do not mistake their enthusiasm for buying authority.
• Ask who signs, in the first meeting. Not at the end. The answer determines everything after it, and an operations lead who cannot answer it is telling you something important.
• Arm the champion in finance’s language before they need it, so the internal case is built once rather than rebuilt after it fails.
• Surface IT at meeting two, as a scoping question rather than an approval request.
• Ask about procurement before the pilot, because the answer sets your close date and nothing you do later changes it.

None of this is exotic. It is the same multi-threading discipline any complex sale needs, applied to a sector where the four roles are unusually predictable, which means the sequence can be planned rather than discovered.

What a stalled deal is telling you

Logistics deals rarely die loudly. They go quiet, and the quiet has a diagnosis.

A champion who stops replying after a good demo has usually lost an internal argument they did not tell you about, most often to finance. A pilot that keeps slipping by two weeks is usually an operations team without the capacity to run it alongside their day job. A deal that clears operations and finance and then stops is almost always IT or procurement, and the fastest way to find out which is to ask the champion directly rather than to send another follow up.

The general point: silence in this sector is more often an internal blocker than a loss of interest, and the follow up that works names the blocker rather than restating the value proposition.

Related reading

Part of a five guide series on selling logistics and supply chain software. See also why the sales cycle runs long, the three buyers, why volume is the qualifying number, and opening South East Asia.

The vertical argument and named results are on GTM for logistics and supply chain software. For writing messaging each of these four will recognise, see ICP, persona and messaging.