Margin Erosion at Meridian Freight: Future State, Options and a Hostile Director

Resist treating the margin number as the problem. It is a symptom; the strategy question is which capabilities are failing.

Analyse several lenses, not only finance

• Revenue and cost structure: decompose the 4.4%. Is erosion driven by rate pressure from the 27% client, by empty running and poor utilisation, by driver wage premiums and agency costs, or by maintenance on an ageing fleet? Each points to a different future state.
• Capabilities: dispatch optimisation, route planning, driver retention, contract pricing discipline, cost-to-serve data quality. A capability gap is the usual root cause behind a margin number.
• Process and technology: is dispatch manual? Is telematics data collected and used, or collected and ignored?
• Organisation and culture: 38% driver turnover is a symptom of pay, scheduling or management. Identify which, because buying vehicles and employing drivers makes it worse if the cause is scheduling.
• External: client concentration, the driver labour market, competitor pricing, and any regulatory limits on subcontracting.

Test the causal chain The client's insourcing threat may rest on price or on service reliability. That distinction determines whether cost reduction or service improvement is the lever, and it should be checked with the client rather than assumed.

Outputs A current state description with quantified gaps - cost per drop, drops per driver-hour, cost per driver lost - a root-cause statement for each, and a short list of internal business needs. Present it as the evidentiary base for choosing among options, and be explicit about what cannot yet be evidenced.

Define the future state first as outcomes and capabilities, then treat options as means to those ends.

Future state, stated independently of the options For example, in 18 months: cost per drop down 12%, driver turnover below 20%, client concentration below 20% of revenue, dispatch supported by real-time data, and third-party capacity contributing around 8% of revenue. Add the capabilities implied (dynamic routing, partner performance management, driver scheduling), the organisation changes, and the constraints - 18-month horizon, conservative risk appetite, no acquisition.

Evaluation criteria, weighted before scoring Capital required, time to benefit, execution risk, operating complexity, reversibility, industrial relations exposure, and fit with risk appetite.

• Owned fleet: highest capital, slowest to benefit, locks in fixed cost during a driver shortage, and carries the greatest industrial exposure.
• Subcontract last mile: asset-light and fast, but transfers service quality and margin, and requires a partner-management capability the firm may not yet have. Check insurance and regulatory constraints.
• SaaS TMS plus capacity marketplace: low capital, but market-making is a new business model requiring commercial capability - a far larger change than the margin problem demands.

Reasoning trap to avoid Judging an option by the loudest objection rather than by evidence. Score each option against each criterion with a documented basis, note confidence levels, and run sensitivity on the two most uncertain assumptions: driver cost inflation, and whether the client stays at a 10% reduction.

Likely recommendation A staged combination - subcontract to remove fixed cost now, license the TMS for visibility - with a decision gate before committing to marketplace revenue. Justify it by reversibility, which is exactly what a conservative risk appetite rewards.

A change strategy explains how the organisation moves to the future state - transition states, capability changes and the engagement required. It is not a project plan.

Transition states Two or three intermediate states with entry and exit conditions:

• T1 (months 0–4): partner shortlist, cost-to-serve baseline established, dispatch data captured.
• T2 (months 5–10): around 30% of volume through partners, new dispatch process live, driver scheduling pilot running.
• T3 (months 11–18): around 60% through partners, marketplace pilot with five external carriers, contract renegotiation with the major client. Each state carries a value check. If T2 does not show cost per drop falling, the strategy is wrong and should stop.

Capability and organisation changes Partner performance management, pricing discipline, data literacy in dispatch, and possibly a commercial role for capacity sales. Name who must do what differently.

The operations director matters more than the board here He controls dispatch and drivers. 'A fantasy' and 'numbers will be gamed' are not objections to data; they are fears about control, headcount and status. Responses:

• Give him a defined role in designing T2 and a decision right over partner operating standards.
• Separate personal consequence from analysis: state honestly what happens to his drivers under each option.
• Agree in advance how success will be measured and who signs off the measurement, which directly answers the 'gamed numbers' objection.
• Record his concerns formally with dates and responses, so they are answered rather than overruled.

If opposition persists, it is a documented risk to the change strategy with a mitigation plan and a sponsor decision - not something to bury.