Identify the operating points where margin starts to leak.
Most margin loss does not appear as one dramatic failure. It often accumulates through small structural points inside normal work: a price not updated, a customer exception repeated, a supplier term accepted, a delay absorbed, or a handoff corrected manually.
VectorMargin focuses on these points because they are usually where profit is absorbed before leadership can see the pattern clearly.
Core idea
Leakage nodes are where normal business activity stops producing normal margin.
What a leakage node is
A leakage node is not simply a cost problem. It is a point where
commercial intent, operating behaviour, timing, and accountability
stop translating cleanly into margin.
The business may still look active and commercially healthy on the
surface. The issue is that one part of the operating model is no
longer carrying its true economic weight.
Primary leakage nodes
The review looks for the few connected points that explain why margin is weaker than expected. These nodes are usually familiar to the business, but not always connected clearly to their margin effect.
Pricing logic
Pricing that once made sense may no longer reflect real delivery cost, supplier movement, exception frequency, labour, fuel, or service intensity.
Customer-level economics
Some customers look strong by revenue but quietly consume margin through coordination, exceptions, credit exposure, and operational complexity.
Operational handoffs
Margin is often absorbed where information moves between sales, operations, dispatch, finance, suppliers, and customer service.
Cash timing
Work can appear profitable while payment timing, supplier terms, working capital pressure, and delayed recovery weaken its real value.
Supplier exposure
Supplier movement, unclear pass-through logic, and weak term discipline can turn normal delivery into hidden margin pressure.
Reporting averages
Standard reporting can hide leakage when stronger customers, routes, services, or jobs average out weaker ones.
What is not a leakage node
Not every weakness deserves the same level of attention. A leakage node matters when the business repeatedly absorbs cost, time, risk, or complexity without clear recovery, ownership, or commercial logic.
Not every cost increase
Some costs are visible and explainable. The concern is when the business keeps absorbing them without clear recovery.
Not every mistake
A mistake becomes relevant when it repeats often enough to become part of the operating model.
Not every difficult customer
The issue is whether the real cost-to-serve is understood and reflected in margin.
Why nodes matter
A business can usually correct a visible loss. The harder problem is a small repeated weakness that becomes accepted as normal. Leakage nodes matter because they show where management attention should go before margin erosion becomes part of the operating model.
Once the node is clear, the discussion becomes more precise: which customer economics should be reviewed, which handoff needs ownership, which supplier terms need discipline, and which pricing logic no longer reflects operating reality.
What this helps leadership decide
The value is not only in seeing that margin is weaker. The value is in understanding where to look first, what to question, and which points may deserve correction before the issue spreads.
Where pricing may need attention
Around the customers, services, jobs, or routes where cost recovery no longer matches operating reality.
Where ownership may be unclear
Especially where several teams see part of the issue, but no one owns the margin consequence.
Which customers need a different view
Revenue alone may not show whether a customer is economically strong, neutral, or quietly expensive to serve.
Which issues are not cost-cutting problems
Some margin pressure is solved through recovery logic, terms, ownership, or commercial discipline — not cuts.
Related margin topics
Leakage nodes are easier to understand when they are reviewed together with operating signals, review method, and business fit.