Airport BOH Logistics: 2026 Guide

How to Build a Supply Chain Business Case That Survives the CFO

Most supply chain business cases die in the CFO's office. The operational team has spent three months building it. The slide pack is 80 pages. The savings number is impressive. The strategic narrative is compelling. The CFO reads it, asks four questions, and the case never recovers. The investment does not get approved, or it gets approved at half the requested size, or it gets deferred to next year's capital cycle and quietly forgotten.

The problem is rarely the underlying initiative. The problem is the business case. Supply chain business cases are typically written by operators, for operators, using operational language and operational logic. They fail at the CFO test because they do not think like a CFO thinks. The financial framing is weak, the risk picture is light, the benefits are overstated, the executional credibility is unproven, and the linkage to the financial reporting the CFO actually has to defend is absent.

This guide is the practitioner's framework for building supply chain business cases that survive. It covers what the CFO is actually testing for, the eight components a defensible business case must include, the methodology to build it, the common failures that derail approval, and the benefits realisation discipline that converts a one-off case into a credible transformation programme.

What "survives the CFO" actually means

A supply chain business case survives the CFO when three things are true. The financial framework is robust enough to defend against scrutiny. The risk and downside picture is honest enough to be credible. The executional plan is realistic enough that the CFO believes the benefits will actually be delivered.

Most cases fail at least one of these tests. Many fail all three.

The CFO is not the enemy of supply chain investment. The CFO is the gatekeeper of capital allocation, working capital, and financial credibility with the board, the audit committee, and external markets. When the CFO challenges a business case, it is rarely because they oppose the initiative. It is because the case as written exposes the business to risk the CFO cannot defend if it goes wrong. Understanding what the CFO is actually testing for is the first step to writing a case that survives.

The CFO mental model: what they are actually testing

A CFO reviewing a supply chain business case is running a parallel mental model. Understanding what is in that model is what allows the business case writer to address it directly.

The capital allocation test. Of all the investment proposals competing for capital this year, why does this one deserve a share? What is the return relative to alternatives? What is the risk-adjusted comparison? A business case that does not acknowledge it is competing for finite capital reveals naïveté about the corporate environment.

The cash flow test. When does the cash actually move? Capex hits in year one. Implementation cost is typically front-loaded. Benefits typically lag. The CFO is modelling cash flow, not accounting profit. A business case that ignores the timing pattern of cash is treated as financially unliterate.

The reliability of benefits test. How likely is each line of benefit to actually be delivered? What is the evidence base? Has the team done this before? Are the savings assumptions benchmarked against comparable outcomes? Benefits that read as aspirational rather than evidence-based get heavily discounted before they reach the approval threshold.

The downside test. What happens if the benefits come in at 50 per cent of plan? What happens if costs come in at 130 per cent? What happens if the timeline slips by 6 months? A business case without a downside scenario tells the CFO the team has not stress-tested its own thinking.

The executional credibility test. Does the team proposing this have the capability, capacity, and track record to deliver it? Has the change management been properly resourced? Is there an internal sponsor with the authority to remove obstacles? A strong financial case with a weak delivery plan typically fails.

The accounting and reporting test. How will the benefits show up in the financial reports the CFO actually has to defend to the board? Which P&L lines move? When? By how much? A business case that cannot map to the financial reporting structure cannot be tracked, and benefits that cannot be tracked are functionally fictional.

The eight components below address each of these tests directly.

The eight components of a CFO-grade business case

A supply chain business case that survives executive scrutiny has eight components. Each addresses a specific element of the CFO mental model. Missing any of them creates a weakness that the CFO will find.

Component one: the strategic context and decision framing. What problem does this investment solve, why now, and what happens if it does not proceed? This is short, factual, and grounded in the business reality, not vendor marketing. The "do nothing" scenario is named explicitly. The cost of inaction is quantified where possible. A case that cannot articulate the cost of inaction has not earned the right to ask for capital.

Component two: the baseline. Every benefit is measured against a quantified current state. The baseline must reconcile to the financial P&L within an acceptable tolerance. A business case without a defensible baseline cannot be defended at all, because the benefits have no anchor. For more on the baseline discipline, our companion piece How to Build a Decision-Grade Supply Chain Baseline covers the methodology in depth.

Component three: the benefits case. Every benefit line is quantified, evidence-based, risk-adjusted, and time-phased. The four categories that typically appear: hard cost savings (freight, labour, warehousing, working capital release), revenue uplift (improved service, reduced lost sales, new channel enablement), risk mitigation (compliance, resilience, business continuity), and capability or strategic enablement. Each benefit has an owner, a measurement method, and a realistic profile of when it actually shows up in the P&L. Aspirational benefits are kept separate from committed benefits.

Component four: the full cost picture. Every cost is captured: capex, implementation services, software licensing, hardware, integration, training, change management, internal team time, parallel running, post-go-live stabilisation, and contingency. The cost of change management in particular is often underweighted. In our experience, organisations that invest meaningfully in change management consistently outperform those that under-invest. Costs are time-phased to match the cash flow profile.

Component five: the financial framework. NPV, IRR, payback period, and total cost of ownership over five years are calculated to the company's own financial standards. The discount rate is the company's WACC or capital threshold rate, not an arbitrary number. The financial model can be opened, interrogated, and re-run by the finance team. A business case where the finance team cannot interrogate the model is not a serious business case.

Component six: the sensitivity and scenario analysis. Conservative, base, and upside scenarios are modelled and presented. The variables that most affect the outcome (benefit realisation rate, timeline, cost overrun, working capital release) are stress-tested. The downside case is honest. A case with no downside is treated as either dishonest or naïve.

Component seven: the executional plan. The implementation roadmap, the team that will deliver it, the change management approach, the governance structure, the milestone gates, the risk register, and the dependencies. Executional credibility is the single most common reason a financially strong case still fails. The CFO wants to see that the people proposing the investment have thought hard about how it will be delivered.

Component eight: the benefits realisation framework. How will benefits be tracked, who owns each one, what are the reporting mechanisms, and what happens if benefits underperform? A business case without a benefits realisation framework is functionally promising savings that nobody is accountable for. A CFO who has previously approved a case that did not deliver is permanently sceptical of the next case from the same team. The framework is what restores credibility.

The methodology: six steps to a defensible case

The end-to-end methodology for building a CFO-grade business case breaks into six steps.

Step one: scope the case. Define the decision the case is supporting. A capital approval for a single DC? A multi-year transformation programme? A technology selection? The scope drives the depth, the granularity, and the timeline. Trying to build a single case that supports every related decision usually produces a case that supports none of them well.

Step two: build or refresh the baseline. Every business case is built on a baseline. If the baseline is fresh and decision-grade, the case can be built on it directly. If the baseline is weeks-old slide pack quality, the case is in trouble before it starts. Invest in the baseline first.

Step three: quantify the benefits. Work through each benefit line, drawing on the baseline for the anchor and on operational and finance input for the realistic value. Risk-adjust each line. Separate hard committed savings from aspirational upside. Build the cash flow timing properly: when does each benefit actually start, and how does it ramp?

Step four: build the full cost picture. Capture every cost category. Stress-test the implementation services estimate against vendor or partner quotes. Build the change management cost as a percentage of total programme cost based on the change complexity, not the leftover budget. Include working capital movement during transition. Include the post-go-live stabilisation period.

Step five: build the financial framework and scenarios. Construct the NPV, IRR, and payback view against the company's financial standards. Build the conservative, base, and upside scenarios. Test the sensitivity to the variables that matter most. Make the model interrogable.

Step six: pressure-test before submission. The single most underrated step. Walk the case through a sceptical finance representative, a sceptical operational representative, and where possible a sceptical executive who is not the sponsor. Fix the weaknesses they find before the formal submission. A case that has been pre-tested by friendly sceptics is far stronger than one that meets the CFO for the first time in the approval meeting.

The full methodology typically runs six to twelve weeks for a mid-market Australian business case, depending on scope, baseline maturity, and the complexity of the underlying initiative. Enterprise-scale or multi-business-unit cases can run longer. The single biggest variable is the maturity of the baseline coming into the work.

Where business cases go wrong

In our experience advising Australian operations and finance leaders, supply chain business cases fail or get downsized for five recurring reasons. All of them are avoidable.

Overstating benefits. The most common failure mode. Benefits are estimated optimistically, without risk adjustment, without sensitivity analysis, and without an evidence base. Experienced CFOs discount aspirational benefits heavily, often by 30 to 50 per cent, before they will treat the case as credible. The team's credibility is then damaged before the conversation begins. Honest, risk-adjusted, evidence-based benefits land better than inflated ones.

Understating costs. Implementation services estimated at vendor optimistic numbers. Change management treated as a line item rather than a workstream. Internal team cost ignored entirely. Working capital movement during transition missed. Stabilisation cost underestimated. The full cost picture is consistently understated in cases that are written by the team proposing the investment, because they want the case to look strong.

Missing the cash flow timing. Treating the business case as an annualised return view rather than a cash flow view. Capex hits in year one, benefits ramp over two to three years, and the cash flow trough is usually deeper and longer than the case implies. CFOs model cash. Business cases that ignore cash timing get sent back to be redone.

No executional credibility. A strong financial case with a weak delivery plan typically fails. The CFO is testing whether this team can actually execute. A case that names the implementation partner, the internal team, the governance structure, the risk management approach, and the change management plan has earned the right to be taken seriously. A case that hand-waves the delivery section has not.

No benefits realisation framework. A case that promises savings without a tracking mechanism is asking the CFO to take the team's word for it. Mature CFOs do not take the team's word for it. The benefits realisation framework, with named owners, measurement methods, and reporting cadence, is what converts a case from optimism to commitment.

The common thread is that supply chain teams write business cases for themselves rather than for the audience that approves them. The fix is to think like a CFO from the first slide.

Benefits realisation: the discipline that makes the next case easier

The single biggest determinant of how easily the next business case gets approved is whether the last business case delivered. A team with a track record of delivering committed benefits builds credibility that lowers the bar on every subsequent submission. A team with a track record of underdelivery faces a higher bar every time.

A working benefits realisation framework has five elements. A baseline reference point for each benefit. A named owner who is accountable for delivery. A measurement methodology that is documented and agreed upfront. A reporting cadence that surfaces variance early. A management response when benefits underperform, including corrective action and transparent communication.

The benefits realisation framework is built during the business case, not after approval. Approval cases that include the framework win credibility from the finance team and from the CFO directly, because they signal that the proposing team is taking accountability for the commitment, not just asking for the capital.

For more on how transformation programmes deliver against their business cases through structured change and benefits tracking, our Project and Change Management practice covers the delivery layer.

Sector applications

Supply chain business cases are universal in framework but sector-specific in content. The same eight components apply across sectors, but the benefits categories and the CFO's concerns shift.

Retail and ecommerce. Channel profitability, ecommerce fulfilment unit economics, omnichannel cost-to-serve, and working capital release are the dominant benefit categories. The CFO scrutiny typically focuses on whether the ecommerce fulfilment model will scale profitably. The Trace In-store and Online Retail sector page covers the broader context.

FMCG and manufacturing. Network rationalisation, automation business cases, SKU rationalisation, and supplier consolidation are the dominant categories. CFO scrutiny typically focuses on capital efficiency and on whether productivity benefits will hold post-implementation. The FMCG and Manufacturing sector page covers context.

Health and aged care. Workforce optimisation, clinical supply chain efficiency, asset utilisation, and procurement leverage are the dominant categories. CFO scrutiny in this sector also includes regulatory and patient or resident outcome considerations. The Health and Aged Care sector page covers context.

Hospitality and integrated resorts. Back-of-house consolidation, F&B labour efficiency, venue-level cost-to-serve, and procurement leverage are typical benefit categories. CFO scrutiny focuses on guest experience risk alongside financial return.

Government and defence. Program-level cost transparency, sovereign capability development, and asset lifecycle optimisation are typical benefit categories. The CFO equivalent in government (CFO, Treasury, finance executive) typically applies value-for-money tests and risk allocation analysis alongside the financial framework. The Government and Defence sector page covers context.

Property, hospitality and services. Operating cost reduction, asset productivity, and service model redesign are typical categories. The CFO concerns mirror commercial benchmarks.

The 2026 context

Three forces have raised the bar on supply chain business cases in 2026.

The capital efficiency environment has tightened. Higher interest rates, persistent inflation in supply chain cost categories, and uneven revenue growth have pushed boards and CFOs to scrutinise capital allocation harder than they did three years ago. Business cases that would have been approved on strategic narrative alone in 2021 require a defensible financial framework today.

Capex governance has matured. ASIC's focus on directors' duties and on post-investment review of major capital decisions has translated into stricter board-level discipline on business case quality and benefits realisation. Boards are increasingly demanding to see the benefits realisation framework alongside the approval case.

Transformation track records are visible. Many Australian businesses are now several years into ERP, automation, and supply chain technology programmes. Those that overpromised in their original business cases face board-level scepticism on their next proposal. Those that delivered have permission to ask for more.

The CFO-grade business case is no longer a nice-to-have. It is the new approval threshold.

How Trace Consultants can help

Trace Consultants advises Australian organisations on supply chain business case development and benefits realisation. Our positioning is deliberate: we build cases that survive executive scrutiny, with the financial rigour and executional credibility that CFOs and boards expect.

Business case development. We build supply chain and procurement business cases across capital approvals, transformation programmes, technology investments, network redesigns, and operating model changes. The deliverable is a defensible case with a working financial model the business owns.

Baseline and benefits modelling. Every business case sits on a baseline. We build the baseline and the benefits model together, ensuring the case is anchored in a quantified current state rather than aspirational forecasts.

Strategic framing and decision support. Where the case sits inside a broader strategic decision, our Strategy and Network Design practice provides the strategic context.

Procurement and category strategy. Where the case relates to procurement, supplier, or category investment, our Procurement practice provides category-specific commercial framing.

Transformation programme delivery and benefits realisation. Where the case is approved and moves into delivery, our Project and Change Management practice supports the implementation and the benefits tracking that protects the case's credibility post-approval.

Technology business cases. For technology-led cases (WMS, TMS, ERP, planning systems, automation), our Technology practice combines the platform evaluation with the commercial framing.

Explore our Strategy and Network Design services →

Speak to an expert at Trace →

Where to begin

If you are early in this journey, start with three questions. What is the decision the business case is supporting, and who is the actual approver (CFO, board, investment committee)? What baseline does the case sit on, and is it decision-grade? What benefits realisation framework will sit alongside the case at submission, and who owns each line?

If those three questions point to a business case exercise, scope the work to match the decision, invest in the baseline first, and treat the case as a financial product designed to survive financial scrutiny.

Frequently asked questions

What makes a supply chain business case "CFO-grade"? A CFO-grade business case is robust enough financially to survive executive scrutiny, honest enough on risk and downside to be credible, and credible enough on execution that the CFO believes the benefits will be delivered. It addresses the CFO's mental model directly rather than presenting an operational narrative dressed in financial language.

How long does it take to build a supply chain business case? A mid-market Australian supply chain business case typically takes six to twelve weeks to build, depending on scope, baseline maturity, and the complexity of the underlying initiative. Enterprise-scale cases can take longer. A weak baseline is the single biggest cause of delay.

What is the most common reason supply chain business cases get rejected? Overstated benefits combined with understated costs is the single most common reason. The CFO discounts the benefits, inflates the costs, and the case no longer clears the approval threshold. Honest, risk-adjusted estimates land better than inflated ones.

What should a supply chain business case include? Eight components: strategic context and decision framing, baseline, benefits case (quantified and risk-adjusted), full cost picture (including change management), financial framework (NPV, IRR, payback, TCO), sensitivity and scenario analysis, executional plan, and benefits realisation framework.

Do I need a baseline to build a business case? Yes. Every business case is built on a baseline. Benefits are measured against the current state, costs are estimated against the current operating footprint, and risks are evaluated against current capability. A business case without a defensible baseline is not defensible itself.

How should I handle the downside scenario? Honestly. Model a conservative case with 50 per cent benefit realisation, 130 per cent cost outturn, and 6-month delay. Show the financial outcome. A case that survives its own downside scenario is far stronger than a case that pretends the downside does not exist.

What is benefits realisation and why does it matter? Benefits realisation is the tracking discipline that converts approved benefits into delivered benefits. It includes named owners, measurement methods, reporting cadence, and management response when benefits underperform. Without a benefits realisation framework, approved business cases cannot be tracked, and benefits that cannot be tracked are functionally fictional.

Should I include change management cost in the business case? Yes, explicitly and prominently. Change management is typically a major cost line in supply chain transformations, and underweighting it is one of the most common causes of programme failure. Build it as a workstream with its own budget, not as a residual line item.

How does a business case relate to a feasibility study or strategic case? A feasibility study tests whether an initiative can be done. A strategic case tests whether it should be done. A business case tests whether it is financially defensible to do it. Mature organisations sequence these deliberately: feasibility, then strategic case, then business case, then approval.

What happens when benefits underperform after approval? The benefits realisation framework triggers a documented management response: root cause analysis, corrective action, revised forecast, and transparent communication to the approving body. A team that handles underperformance transparently maintains credibility for the next case. A team that hides underperformance damages its credibility permanently.

A supply chain business case that survives the CFO is the difference between an investment approved and an opportunity lost. The framework is not complicated, but the discipline is demanding. Honest baselines, risk-adjusted benefits, full cost pictures, executional credibility, and benefits realisation accountability. The teams that build cases to this standard get their investments approved. The teams that do not, do not.

If you are scoping a supply chain investment in 2026, the case is where the work begins.

Explore our Strategy and Network Design services →

Speak to an expert at Trace →

Related reading: Strategy and Network Design · Procurement · Project and Change Management · Technology · Planning and Operations · Insights

How to Build a Decision-Grade Supply Chain Baseline: A Framework for Australian Businesses

The most expensive mistakes in supply chain transformation are made before the transformation itself begins. They are made in the baseline. A weak current state model leads to a flawed business case, which leads to a misaligned future state, which leads to a programme that overruns, underdelivers, and damages the credibility of the leadership team that sponsored it. The technology is rarely the problem. The baseline is.

Yet in our experience advising Australian organisations across retail, FMCG, hospitality, health and aged care, government, and 3PL, the baseline is also the most consistently underweighted piece of any transformation. Programme teams spend months on the future state, the technology, the change plan, and the implementation roadmap. They spend weeks, sometimes days, on the current state. The asymmetry shows up later in every business case argument, every executive decision review, and every variance conversation post go-live.

This guide is the framework for building a decision-grade supply chain baseline: one that survives board scrutiny, supports scenario modelling, and underpins the downstream decisions on network, technology, operating model, and investment. It covers what a baseline actually is, what "decision-grade" means in practice, the components that have to be in the model, the methodology to build it, how to handle the data gaps that exist in every Australian business, and the common pitfalls that turn a baseline exercise into wasted effort.

What is a supply chain baseline?

A supply chain baseline is the structured, defensible, quantified representation of the supply chain as it operates today. It is the answer to the question "what does our supply chain actually cost, how does it actually perform, and what does it actually look like" before anyone starts proposing what it should become.

A baseline is not a slide pack. It is a model. A working representation of the network, costs, service levels, inventory positions, and capability that the business can interrogate, stress-test, and use as the starting point for every transformation decision that follows.

There is a useful distinction between three terms that are often used interchangeably and should not be. A current state assessment is the exercise of investigating and documenting how the supply chain operates today. A baseline is the quantified model that comes out of that assessment. A diagnostic is the analytical interpretation of the baseline against benchmarks, peers, or future requirements. The assessment is the activity. The baseline is the artefact. The diagnostic is the insight.

The baseline is what survives. Years later, when the transformation is complete and the next one is being scoped, the diagnostic insights have aged and the assessment work has been forgotten, but the baseline model (if it was built properly) is still being refreshed and used.

Why decision-grade matters

Most supply chain baselines are not decision-grade. They are good enough to populate a slide deck but not good enough to defend against a sceptical CFO, a challenging board, or a transformation steering committee asking pointed questions about variance.

A decision-grade baseline meets three tests.

The defensibility test. Can the model be defended line by line under scrutiny from a sceptical executive? Can every cost be traced to a source system? Can every allocation be explained by the cost driver behind it? Can every service level be reconciled to operational records? If the answers are not yes, the baseline will fail at the first hard meeting and the transformation will lose credibility before it has started.

The operability test. Can an operator look at the baseline and recognise the business they actually run? A baseline that the operations team rejects as not reflecting reality is dead on arrival, regardless of how analytically elegant the model is. The baseline must be built with operational input, validated with operational stakeholders, and accepted as a fair representation of how the business actually works.

The scenario test. Can the baseline support scenario modelling? Can it be re-run with different assumptions to test future state options? Can it produce comparable cost, service, and capability views under different network configurations, demand patterns, or operating models? A baseline that cannot move is a snapshot, not a tool.

A baseline that passes all three tests becomes a permanent commercial asset. A baseline that passes only one or two is consumable: useful for the immediate purpose, but not durable enough to support the decisions that follow.

The five components of a decision-grade baseline

A baseline that is going to support real transformation decisions has five components. Models that omit any of them tend to produce conclusions that do not survive contact with the board.

Component one: the network baseline. A complete description of the physical supply chain: facilities (DCs, warehouses, cross-docks, manufacturing sites, retail nodes), flows (inbound, inter-site, outbound, returns), volumes (units, lines, cases, pallets, cubic metres), and the geographic structure that connects them. The network baseline is what every future state network design alternative is compared against.

Component two: the cost baseline. The full cost-to-serve picture covering inbound freight, warehousing and handling, outbound transport, last mile, returns, customer service, technology, and the share of overhead that genuinely scales with serving activity. The cost baseline must reconcile to the financial P&L within an acceptable tolerance. A cost baseline that cannot reproduce reported supply chain cost is not a baseline.

Component three: the service baseline. The current service performance picture: DIFOT, order accuracy, dock-to-stock time, dispatch lead time, perfect order rate, returns rate, customer satisfaction, and the service differentiation patterns (or absence of them) across customers, channels, and segments. Service is the constraint that bounds every cost decision. A baseline that ignores it produces commercially indefensible recommendations.

Component four: the inventory baseline. The current inventory position by SKU, location, and stock class. Holding, ageing, obsolescence, slow-moving, dead, in-transit, safety stock, and cycle stock. Inventory is the working capital lever and the service lever simultaneously, and the inventory baseline is what every future state working capital case is built on.

Component five: the capability baseline. The honest assessment of the organisation's current process maturity, system landscape, data discipline, and team capability. Capability is often the missed component. A transformation that the current organisation cannot execute will fail regardless of how good the future state design is. The capability baseline anchors the change programme.

The five components form an interconnected system. Network, cost, service, and inventory views all need to reconcile against each other. The capability view sets the speed limit on what the transformation can achieve.

The methodology: seven steps to a decision-grade baseline

The end-to-end methodology for building a decision-grade baseline breaks into seven steps. Each has its own data, validation, and governance discipline.

Step one: scope the baseline. Define the boundaries of the baseline before any data is gathered. Geography, business units, channels, time period, level of granularity. A baseline scoped too tightly cannot answer the questions the business actually has. A baseline scoped too broadly produces a model too large to maintain and too aggregated to act on. Scope to the decisions the baseline will support, not to the data that happens to be available.

Step two: define the data model. Specify the structure of the baseline upfront: dimensions, hierarchies, time grain, cost categories, service measures, and the link tables that allow the views to combine. A baseline built without a data model on day one ends up with structural inconsistencies that surface late and cost time to fix. Spend the design effort early.

Step three: gather and validate the data. Pull data from the source systems (finance, ERP, WMS, TMS, planning systems, payroll, customer service) and validate every input against the source. Where data is incomplete, mark it. Where data is questionable, flag it. Where data is missing, document the gap and decide whether to estimate, exclude, or commission a focused collection effort. Data integrity at this step is what makes the baseline defensible later.

Step four: model the current state. Build the working baseline model that reproduces actual cost and service performance within an acceptable tolerance. A baseline that cannot reproduce current-state costs to within an acceptable variance cannot be trusted to evaluate future-state scenarios. The tolerance varies by use case, but typical practice is reconciliation within 5 per cent at total level and within 10 per cent at segment level. Where the model cannot reconcile, the data has a problem, the allocation logic has a problem, or the business has an unexplained variance that itself is a finding.

Step five: stress-test the baseline. Walk the baseline through operational stakeholders. Test it against known facts. Test the outliers. Test the segments where the output looks counter-intuitive. Either the model is wrong, the data is wrong, or the business has a real insight it did not previously have. All three are valuable outcomes.

Step six: document everything. A decision-grade baseline is documented to a standard that allows anyone to interrogate any number. Data sources, allocation logic, assumptions, exclusions, and known limitations are all captured. The documentation is what makes the baseline durable and what allows it to survive personnel changes.

Step seven: hand over and maintain. A baseline that is built and then abandoned is half a baseline. The handover plan covers how the model is owned, who maintains it, what the refresh cycle is, and how it integrates with the ongoing planning and reporting rhythm of the business. A working baseline that is refreshed quarterly is worth more than a perfect baseline that is built once and shelved.

The full methodology typically runs eight to fourteen weeks for a mid-market Australian business, depending on scope, data quality, and the level of granularity required. Enterprise-scale or multi-business-unit baselines can run longer. The single biggest variable is the state of the data when the work begins.

How to handle data gaps

Every Australian business has data gaps. The decision-grade approach is not to pretend they do not exist. It is to handle them transparently.

Categorise the gap. Is it missing, incomplete, low-quality, or inconsistent across sources? Each category has a different remediation approach. Missing data may need to be collected. Incomplete data may need to be sampled and extrapolated. Low-quality data may need to be cleaned. Inconsistent data may need to be reconciled at source.

Quantify the materiality. A data gap that affects 0.5 per cent of total cost can be handled with a documented estimate. A data gap that affects 30 per cent of total cost is a project in itself. Materiality determines the level of remediation effort.

Use defensible proxies. Where data is genuinely unavailable, use industry-standard or operationally-validated proxies. Cost per kilometre for line haul. Cost per pallet-day for storage. Cost per line picked for warehouse labour. Document the proxy and its source. A proxy is defensible. A guess is not.

Mark data quality in the model. Every input in the baseline should carry a data quality flag: actual, calculated, estimated, or proxy. The model output should aggregate the data quality view alongside the cost and service view, so users can see which conclusions are most and least defensible.

Resist the urge to build the perfect baseline. Perfect is the enemy of decision-grade. A baseline that is 90 per cent complete with known gaps documented is more useful than a baseline that is still being built six months later. Decision-grade does not mean perfect. It means defensible.

How a baseline gets used downstream

A decision-grade baseline is not the deliverable. It is the foundation for the decisions that follow. Six downstream uses recur across Australian businesses.

Network design. Every network design alternative is evaluated against the baseline. The baseline answers "what does the current network cost and how does it perform". The network design exercise answers "what alternative configurations would deliver better cost-service trade-offs". Without a credible baseline, network design conclusions are unfalsifiable. The baseline feeds directly into our Strategy and Network Design practice work.

Business case development. Every transformation business case quantifies the value at stake against the current state. The baseline is what defines that current state. A weak baseline produces a soft business case that does not survive CFO scrutiny.

Operating model redesign. Future-state operating model decisions are evaluated against current-state operating cost and capability. Without a capability baseline, the change effort required is consistently underestimated.

S&OP and planning transformation. Planning maturity and forecast accuracy improvements are measured against the baseline. The baseline anchors the value case and the performance management cadence.

Cost-to-serve and customer profitability. Cost-to-serve analysis is one of the most valuable applications of the baseline. The cost baseline component feeds directly into CTS modelling and customer or channel profitability decisions.

Automation and technology investment. Automation business cases are built on baseline labour, accuracy, and throughput data. The baseline is what makes the savings case defensible.

A baseline that is built once and then used across all six downstream applications repays its cost many times over. A baseline that is built for one purpose and then redone separately for each subsequent decision is expensive and inconsistent.

Where baselines go wrong

In our experience advising Australian operations and finance leaders, baseline exercises underdeliver for five recurring reasons. All of them are avoidable.

Treating the baseline as a slide pack rather than a model. A 60-page current state report with no underlying working model dies on the day the next executive question is asked. The baseline must be a model the business owns, not a deliverable the consultant takes away.

Skipping the data quality discipline. A baseline that quietly absorbs bad data without flagging it produces conclusions that look authoritative until they are challenged. The defensibility comes from the data discipline, not from the polish of the output.

Building the baseline without operational input. A baseline built entirely in the analytical team without ground-truth from the operators is rejected on arrival. The operators have to recognise their business in the model. If they do not, the baseline is unusable regardless of how methodologically sound it is.

Failing the reconciliation test. A cost baseline that cannot reconcile to the P&L is not a baseline, it is a hypothesis. Reconciliation to financials is mandatory, not optional.

Building it once and never refreshing it. Supply chains move. A baseline that is not refreshed within twelve months has aged past usefulness. The maintenance plan is part of the baseline, not an afterthought.

The common thread is treating the baseline as a project artefact rather than as a permanent commercial asset. The businesses that get the most from their baselines are the ones that build them once, properly, and then keep them alive.

The 2026 context

The Australian environment in 2026 has made baselines more commercially important than at almost any point in the last decade.

Sustained cost pressure across inbound freight, energy, last-mile distribution, and labour means that supply chain cost is a permanent board-level conversation. The Deloitte 2026 Global Retail Industry Outlook reports that 95 per cent of retail executives surveyed expect global trade policies to push costs higher in the year ahead. Tariff volatility, including the 10 per cent baseline US tariff and higher rates on specific categories, has added cost uncertainty across import-exposed Australian businesses.

Channel and operating model change continues. Omnichannel fulfilment, ecommerce growth, and reverse logistics have rewritten the cost structures retailers and FMCG businesses operate against. Health and aged care reform has rewritten the workforce and logistics cost picture for those sectors. Government procurement and program review continues to push for value-for-money transparency that depends on credible cost baselines.

Transformation programmes are being scoped and approved at pace under that pressure. The risk is that they are being scoped against baselines that are weeks-old slide packs rather than living models. The cost of that asymmetry will show up over the next 24 months in transformation overruns, business case re-baselines, and post-investment reviews that struggle to demonstrate the value originally promised.

The baseline is the cheapest insurance in the transformation portfolio.

How Trace Consultants can help

Trace Consultants advises Australian organisations on supply chain current state assessments, baseline modelling, and the downstream decisions baselines support. Our positioning is deliberate: we deliver decision-grade models the business owns, not slide packs the consultant retains. We are vendor-agnostic, partner-led, and senior on every engagement.

Current state assessment and baseline modelling. We scope, build, validate, and hand over decision-grade baseline models that survive executive scrutiny. The deliverable is a working model the business can interrogate, refresh, and use across the downstream decisions that follow.

Network design and strategy. Where the baseline informs network design, our Strategy and Network Design practice translates the baseline into network footprint, DC role, and infrastructure decisions.

Operating model and capability. Where the baseline exposes operating model or capability gaps, our Planning and Operations and Organisational Design practices support the future-state design work.

Transformation programme delivery. Where the baseline anchors a transformation business case and programme, our Project and Change Management practice supports the delivery.

Procurement and supplier baselines. Where the baseline informs procurement or supplier strategy, our Procurement practice translates the baseline into category and sourcing decisions.

Explore our Strategy and Network Design services →

Speak to an expert at Trace →

Where to begin

If you are early in this journey, start with three questions. What decisions is the baseline being built to support (network design, business case, operating model, S&OP transformation, cost-to-serve, automation investment)? What data is available in your source systems today and what would need to be collected or estimated? Who will own the baseline once it is built, and is there a maintenance cycle in place to keep it alive?

If those three questions point to a baseline exercise, scope it tightly to the decisions it will support, design the data model upfront, and treat the build as a programme rather than a project.

Frequently asked questions

What is a supply chain baseline? A supply chain baseline is the structured, defensible, quantified representation of the supply chain as it operates today. It is a working model of network, cost, service, inventory, and capability that the business can interrogate and use as the starting point for transformation decisions.

How is a baseline different from a current state assessment? A current state assessment is the activity of investigating and documenting how the supply chain operates today. A baseline is the quantified model that comes out of the assessment. The assessment is the exercise. The baseline is the artefact.

How long does it take to build a decision-grade baseline? A decision-grade baseline for a mid-market Australian business typically takes eight to fourteen weeks. The single biggest variable is the state of the data when the work begins. Enterprise-scale or multi-business-unit baselines can take longer.

What data do you need to build a baseline? At minimum: finance data covering supply chain cost categories, ERP transaction data covering volumes and flows, WMS and TMS operational data covering warehousing and freight, planning system data covering forecast and inventory positions, service performance data, and the organisational structure and headcount data covering capability. Data gaps are normal and managed transparently in the model.

What does decision-grade actually mean? A baseline is decision-grade when it is defensible to a board, executable by an operator, and useful for scenario modelling. Defensibility means every number can be traced to a source. Executability means the operators recognise the business in the model. Scenario usefulness means the model can be re-run with different assumptions to test future state options.

Does the baseline need to reconcile to the P&L? Yes. A cost baseline that cannot reproduce reported financial cost within an acceptable variance is not a baseline. Typical practice is reconciliation within around 5 per cent at total level and within around 10 per cent at segment level. Where reconciliation fails, either the data, the allocation logic, or the business has an unexplained variance, and that itself is a finding.

How is a baseline used after it is built? The most common downstream uses are network design, business case development, operating model redesign, S&OP and planning transformation, cost-to-serve and customer profitability analysis, and automation and technology investment cases. A single baseline can support all six.

How often should a baseline be refreshed? A working baseline used for ongoing commercial decision-making is typically refreshed quarterly or at minimum annually. Cost structures, channel mix, and operating model shift over time. A baseline that is not refreshed within twelve months has typically aged past usefulness.

Can a small or mid-market business build a decision-grade baseline? Yes. The methodology is scalable and the tooling required is well within mid-market reach. A small-to-mid-market baseline typically involves less data complexity than an enterprise-scale model and can be delivered in a tighter timeline.

Who should own the baseline once it is built? Ownership typically sits with the supply chain, operations, or transformation leadership team, with finance as a key partner for the cost reconciliation discipline. External advisors build the baseline. The business owns it.

A decision-grade supply chain baseline is one of the highest-leverage investments an Australian business can make before committing to a transformation programme. Built well, it survives years, supports every downstream decision, and pays back many times over. Built badly, it produces a slide pack that lasts a month and a business case that does not survive its first hard meeting.

If you are scoping a transformation, a network redesign, a business case, or an operating model change in 2026, the baseline is where the work begins.

Explore our Strategy and Network Design services →

Speak to an expert at Trace →

Related reading: Strategy and Network Design · Planning and Operations · Project and Change Management · Organisational Design · Procurement · Insights

Cost-to-Serve Analysis: A Framework for Australian Businesses

For most Australian businesses, the standard profit and loss statement hides as much as it reveals. The headline margin looks acceptable. The board accepts the numbers. The CFO signs them off. Underneath, a meaningful share of customers, channels, and SKUs is being sold at a loss. Another meaningful share is generating profit so far above the average that the business does not realise how dependent it has become on a small handful of relationships. The averages disguise the structure. The structure is where the commercial decisions live.

Cost-to-serve analysis is the methodology that exposes the structure. Done well, it produces a decision-grade view of which customers, channels, products, and orders are genuinely profitable, which are marginal, and which are quietly destroying value. Done badly, it produces a 200-page report that sits on a shelf because nobody can defend the numbers or act on them.

This guide is the practitioner's framework for building a cost-to-serve model that survives scrutiny and drives action. It covers what CTS is, why it matters now in the Australian market, the methodology end-to-end, the common traps that derail a CTS exercise, and how to turn the insight into commercial outcomes.

What is cost-to-serve analysis?

Cost-to-serve (CTS) is the total cost of getting a product or service from your business to a specific customer, through a specific channel, at a specific service level. It allocates supply chain, operational, and serving costs to the customers, channels, products, and orders that actually drive them, rather than spreading them as averages across the business.

A standard P&L tells you what the business as a whole earned and what it cost. A CTS analysis tells you which customers, channels, and SKUs actually generated that profit and which absorbed it. The same gross margin product can be wildly profitable through one channel and loss-making through another. The same channel can be highly profitable for one customer segment and value-destroying for another. CTS makes those differences visible.

The Australian Food and Grocery Council has described cost-to-serve as a methodology to determine the likely financial outcomes of supply chain investment and collaborative engagement. The more practical framing is simpler: CTS is the analytical tool that lets a business make defensible commercial decisions about pricing, channel mix, customer rationalisation, service differentiation, and operating model change.

Why CTS matters now in Australia

Three forces have made CTS more commercially relevant in 2026 than at almost any point in the last decade.

The first is sustained cost pressure. Inbound freight, energy, last-mile distribution, labour, and warehousing have all moved structurally higher since 2022. The Circana 2026 Australian FMCG outlook puts annual category spend at more than $175 billion against a backdrop of "uneven growth" and persistent cost and competition pressures. The Deloitte 2026 Global Retail Industry Outlook reports that 95 per cent of retail executives surveyed expect global trade policies to push costs higher in the year ahead. Margins that survived the inflationary years through pricing power are now exposed where pricing power has reached its limit.

The second is channel complexity. The shift to omnichannel fulfilment, ecommerce growth, marketplace expansion, and direct-to-consumer models has created cost structures that the standard P&L was never designed to handle. A product moving through five different channels has five different cost-to-serve profiles. Without analysis, businesses make pricing and investment decisions on a blended average that is no longer fit for purpose.

The third is the maturing data and analytics environment. The tools, data, and computing capacity required to run a credible CTS analysis are now within reach of mid-market businesses, not just enterprise. Five years ago, a CTS exercise was a multi-month consulting engagement. Today it can be a structured six-to-twelve-week diagnostic with a working model handed back to the business.

The convergence of these three forces means that the businesses doing CTS well are pulling further ahead of those that are not. The gap is widening.

The five components of a decision-grade CTS model

A CTS model is decision-grade when it is defensible to a board, executable by an operator, and useful for scenario modelling. Achieving all three requires five components.

Component one: a complete cost taxonomy. Every cost in the supply chain and serving operation must be classified, attributed, and allocated. The taxonomy typically covers inbound freight, warehousing (storage, handling, value-add), outbound transport (line haul, last mile, returns), pick and pack labour, customer service and account management, technology and systems overhead, working capital tied up in inventory, and a share of overhead that genuinely scales with serving activity. A CTS model that omits any major cost category produces unreliable conclusions.

Component two: a defensible allocation logic. Costs must be allocated to customers, channels, products, and orders using drivers that reflect actual cost causation. Warehousing cost allocated by units handled is different to warehousing cost allocated by cubic metres stored, by lines picked, or by orders processed. The right driver depends on the cost behaviour, not on what data is most easily available. The allocation logic must be transparent, documented, and defensible when challenged.

Component three: customer, channel, product, and order dimensions. A CTS model needs to slice the same cost view across at least four dimensions: customer (or customer segment), channel (in-store, ecommerce, wholesale, marketplace, direct, third-party), product (or product category), and order profile (size, frequency, mix, delivery type). The same SKU sold to the same customer through different channels generates different CTS. The four dimensions in combination are where the commercial insight lives.

Component four: a clear service-cost relationship. CTS is not just about cost. It is about the cost of delivering a specific service level to a specific customer. A model that ignores the service dimension misses the most important commercial lever: service differentiation. Pareto-style customers receiving Pareto-style service is the default in most businesses. The opportunity is usually to differentiate.

Component five: a working scenario engine. A static CTS report is a snapshot. A decision-grade CTS model is dynamic, allowing the business to test scenarios: what happens to channel profitability if last-mile freight rises by 15 per cent, if minimum order quantities change, if a customer is moved to a different fulfilment model, if a low-volume SKU is delisted, if delivery frequency to a customer segment is reduced. The scenario engine is what turns CTS from a diagnostic into a decision tool.

A model with all five components becomes a permanent commercial asset. A model missing any of them tends to be used once and shelved.

The methodology: six steps to a working CTS model

The end-to-end methodology for building a decision-grade CTS model breaks into six steps. Each step has its own data, governance, and quality requirements.

Step one: scope the model. Define the question the CTS analysis is answering. Channel profitability for an omnichannel retailer is a different model to customer profitability for a B2B distributor. SKU profitability for an FMCG manufacturer is different again. The scope drives the data, the granularity, and the timeline. Trying to answer every question in one model usually produces a model that answers none of them well.

Step two: build the cost taxonomy and gather the data. Define every relevant cost category and identify the source system for each. Finance systems provide the totals. ERP and WMS provide transaction volumes. TMS provides freight detail. Workforce systems provide labour data. Where data is missing or weak, decisions about proxies, estimates, and quality flags are made transparently. The data gathering step is typically the longest and the most underestimated.

Step three: define the allocation logic. For each cost category, choose the allocation driver based on cost causation. Document the choice and the rationale. Where multiple drivers could be defended, pick the one that best reflects operational reality and note the alternative. The discipline at this step is what makes the model defensible later.

Step four: build the model. Construct the working CTS model, typically in Excel for transparency or in a dedicated analytics platform for scalability. The model should allow each cost to be traced from its source to its allocation destination. Audit trails matter. Models that hide their logic in macros or undocumented formulas fail the defensibility test.

Step five: validate and stress-test. Reconcile model totals back to the P&L. Test the allocation logic with operational stakeholders. Identify customers, channels, or SKUs where the model output looks counter-intuitive and investigate. Either the data is wrong, the allocation logic is wrong, or the business has a real insight it did not previously have. All three outcomes are valuable.

Step six: interpret and act. The model output is not the deliverable. The deliverable is the decisions the model enables. Whale curves, customer-channel matrices, scenario outputs, and action lists are all built from the model. Without an activation plan, the analysis is unfinished.

In our experience, the businesses that get the most value from CTS treat it as a programme, not a project. The first model takes ten to fourteen weeks to build for a mid-market business. The ongoing operational use case extends for years.

The whale curve: what CTS typically reveals

The most-cited CTS output is the profitability waterfall, often called the whale curve. The whale curve plots customers (or SKUs, or channels) ranked from most to least profitable, showing cumulative profit contribution.

In most businesses, the shape is consistent. The top 20 to 30 per cent of customers typically generate well in excess of total profit, often in the range of 150 to 200 per cent. The middle tier sits around break-even. The bottom 20 to 30 per cent typically destroys a meaningful share of the profit generated at the top. The headline business is profitable. The CTS breakdown shows that a significant portion of that profit is being absorbed by customers, channels, or SKUs that cost more to serve than they contribute.

This pattern repeats across sectors. In Australian retail and distribution, it shows up as ecommerce-fulfilment loss-making at certain order sizes. In FMCG, it shows up as long-tail SKUs absorbing distribution and slotting cost. In healthcare and aged care, it shows up as small remote sites driving disproportionate logistics cost. In hospitality back-of-house, it shows up as low-volume venues with the same fixed supply chain overhead as high-volume venues. In 3PL operations, it shows up as legacy clients on rates that no longer reflect cost-to-serve.

The whale curve is not the end of the analysis. It is the start of the commercial conversation.

Where CTS analyses go wrong

In our experience advising Australian operations and finance leaders, CTS exercises underdeliver for five recurring reasons. All of them are avoidable.

Scoping too broadly. Trying to build one CTS model that answers customer profitability, channel profitability, SKU profitability, and route-level profitability simultaneously usually produces a model too complex to maintain and too aggregated to act on. Scope tightly. A focused customer-and-channel CTS model is more valuable than a sprawling everything-at-once model.

Treating the model as the deliverable. A 200-page CTS report with no activation plan is a document, not an outcome. The model is the means. The deliverable is the commercial decision: customer rationalisation, channel re-pricing, service differentiation, network change, operating model redesign.

Allocating costs without defensibility. Allocations that cannot be defended to a sceptical commercial counterpart (sales director, channel head, key account manager) get rejected at the first scrutiny meeting. Spend the time on allocation logic upfront. The defensibility of the model is what makes it usable.

Ignoring service in the cost view. A CTS model that does not capture service differentiation by customer or channel misses the biggest commercial lever. The right answer to a loss-making customer is rarely to walk away. It is usually to move them to a different service profile. The model needs to enable that conversation.

Building a snapshot, not a tool. A static CTS analysis ages quickly. Cost structures shift, channel mixes evolve, customer behaviour changes. A working CTS model that the business can rerun quarterly or annually is worth ten static reports.

The common thread is treating CTS as an analytical exercise rather than a commercial discipline. The businesses that get the most from CTS embed it in their commercial decision-making, not just their finance team's quarterly reporting pack.

Activation: turning CTS insight into commercial outcomes

The point of CTS is action. The most valuable activations typically fall into one of six categories.

Customer rationalisation and re-pricing. The bottom of the whale curve usually contains customers being sold below cost. Some of these are strategic. Most are accidents of legacy pricing, account drift, or service creep. CTS makes the case for re-pricing, renegotiation, or in some cases exit.

Channel and fulfilment model redesign. Where a channel is structurally unprofitable, the answer is rarely to stop selling. It is usually to redesign the fulfilment model: minimum order quantities, delivery frequency, click-and-collect substitution, third-party fulfilment, or pricing changes that reflect the true cost of service.

SKU rationalisation. The long tail of SKUs typically absorbs disproportionate slotting, holding, replenishment, and complexity cost. CTS provides the defensible case for delisting decisions that the commercial team has often resisted on the basis of customer relationships.

Service differentiation. Differentiating service levels by customer value is one of the highest-return outcomes of a CTS exercise. Premium service to premium customers. Standard service to standard customers. Lower-touch service to low-value customers. The CTS model defines the segmentation.

Network and operating model change. CTS exposes the cost penalty of network configurations that no longer fit demand patterns. It feeds directly into network design, DC consolidation, and operating model decisions covered in our Strategy and Network Design practice.

Embedded commercial decision-making. The highest-value use of CTS is permanent: making the model available to commercial, account management, and pricing teams as a live decision tool. Every new customer, every pricing decision, every channel investment runs through the CTS model before approval. The discipline pays back continuously.

Sector applications

CTS is sector-universal in concept but sector-specific in application.

Retail and ecommerce. Channel CTS is the dominant question: in-store versus click-and-collect versus home delivery versus marketplace. Multi-channel CTS exposes the true unit economics of online fulfilment, which in many Australian retailers has been masked by blended margins. The Trace In-store and Online Retail sector page covers the broader retail context this work sits inside.

FMCG and manufacturing. Customer and SKU CTS is the dominant question: which trade customers, which categories, which SKUs are generating profit and which are absorbing it. The FMCG and Manufacturing sector page covers the broader context.

Hospitality and integrated resorts. Venue and outlet CTS is the dominant question: which venues, which F&B outlets, which back-of-house flows are profitable at their current cost-to-serve. Hospitality back-of-house is one of the most under-analysed cost pools in the Australian market.

Health and aged care. Site and service-line CTS is the dominant question: which sites, which clinical or care service lines, which patient or resident cohorts carry which cost-to-serve. The Trace Health and Aged Care sector page covers the broader healthcare supply chain context.

3PL and distribution. Client and rate-card CTS is the dominant question: which 3PL clients are on rates that no longer reflect cost-to-serve, and which value-add services are being delivered below cost. This typically informs rate-card resets at contract renewal.

Government and defence. Service-line and program CTS is the dominant question: which programs and service lines carry which true cost when fully allocated. This is increasingly relevant under the Commonwealth's renewed focus on procurement value-for-money and program-level cost transparency.

How Trace Consultants can help

Trace Consultants advises Australian organisations on cost-to-serve diagnostics, modelling, and activation. Our positioning is deliberate: we deliver decision-grade models, not 200-page reports. We sit with the business through activation, not just analysis. We are partner-led, senior on every engagement, and commercially anchored.

Cost-to-serve diagnostic and modelling. We scope, build, and validate CTS models tailored to the commercial question the business is trying to answer. The deliverable is a working model the business owns, not a static report.

Activation and commercial outcomes. Our Planning and Operations practice supports the activation of CTS insight into customer rationalisation, channel redesign, SKU rationalisation, and service differentiation programmes.

Network design and operating model change. Where CTS analysis exposes structural network or operating model issues, our Strategy and Network Design practice translates the insight into network footprint, DC consolidation, and operating model decisions.

Procurement leverage. Where CTS analysis identifies supplier or category cost issues, our Procurement practice supports sourcing and category strategy responses.

Sector depth. CTS in retail, FMCG, hospitality, health and aged care, 3PL, and government has its own data, allocation, and activation nuances. Trace's sector practices bring the operational depth required to make the model defensible and the activation credible.

Explore our Planning and Operations services →

Speak to an expert at Trace →

Where to begin

If you are early in this journey, start with three questions. What is the specific commercial question you are trying to answer (channel profitability, customer profitability, SKU rationalisation, service differentiation, network change)? What data do you have today, and what would you need to build a defensible model? Who owns activation once the model is built, and do they have the authority to act?

If those three questions point to a CTS exercise, scope it tightly. Run a focused ten-to-fourteen-week diagnostic on the most valuable commercial question, build the model, and use the first activation to fund the next. A working CTS programme typically expands organically once the first activation delivers a measurable outcome.

Frequently asked questions

What is cost-to-serve analysis? Cost-to-serve is the total cost of getting a product or service from your business to a specific customer, through a specific channel, at a specific service level. CTS analysis allocates supply chain and serving costs to the customers, channels, products, and orders that actually drive them, rather than averaging them across the business.

How is CTS different from activity-based costing? ABC and CTS share methodological DNA but differ in scope. ABC is a finance-led costing discipline applied across the whole business. CTS is typically a commercially-focused analysis applied to the supply chain and serving cost pools, oriented toward decisions about customers, channels, products, and service levels. In practice, the two methodologies often overlap.

How long does a CTS analysis take? A focused CTS diagnostic for a mid-market Australian business typically runs ten to fourteen weeks from kick-off to activation plan. Enterprise-scale or multi-business-unit CTS programmes can run longer. The longest step is almost always data gathering and validation.

What data do you need for a CTS analysis? At minimum: sales by customer, channel, and SKU; cost data from finance for the relevant cost categories; transaction volumes from ERP, WMS, and TMS; service level data; and operational drivers (cubic metres stored, lines picked, kilometres travelled, orders processed). Data gaps are normal and managed transparently in the model.

What is a whale curve? The whale curve, sometimes called the profitability waterfall, plots customers (or SKUs, or channels) ranked from most to least profitable, showing cumulative profit contribution. The typical shape across most businesses shows the top 20 to 30 per cent of customers generating well in excess of total profit, the middle tier near break-even, and the bottom 20 to 30 per cent destroying value.

Can a small or mid-market business run a CTS analysis? Yes. The methodology is scalable and the tools required are well within mid-market reach in 2026. A small-to-mid-market CTS analysis typically requires less data complexity than an enterprise-scale model and can be delivered in a tighter timeline.

Does CTS apply to services businesses, not just product businesses? Yes. CTS methodology applies to any business serving customers through different channels at different service levels, including health and aged care, professional services, government program delivery, and hospitality. The cost categories shift but the framework holds.

What is the most common mistake in CTS analysis? Treating the model as the deliverable rather than the activation. A defensible model with no activation plan does not change the business. The deliverable is the commercial decision the model enables.

How often should a CTS model be refreshed? A working CTS model used for commercial decision-making is typically refreshed quarterly or at minimum annually. Cost structures, channel mix, and customer behaviour shift, and a model that is not refreshed loses its decision-grade status quickly.

Can CTS analysis support a business case for transformation investment? Yes, and it often does. CTS quantifies the value at stake from network change, channel redesign, automation investment, and operating model redesign, providing the commercial anchor for the business case.

Cost-to-serve analysis is one of the highest-leverage commercial disciplines in supply chain and operations. Done well, it permanently changes how a business prices, segments, serves, and invests. Done badly, it generates a report nobody can defend. The difference is the methodology, the data discipline, and the commitment to activate rather than just analyse.

If you are facing margin pressure, channel complexity, or transformation investment decisions in 2026, a cost-to-serve analysis is one of the first places to look.

Explore our Planning and Operations services →

Speak to an expert at Trace →

Related reading: Planning and Operations · Strategy and Network Design · Procurement · Warehousing and Distribution · Insights