Set a product's target cost before the design fixes its spending

A target cost works backward from a supportable selling price and the profit the business requires. It gives the design and commercial teams a cost boundary before specifications and supplier commitments become difficult to change. A cost estimate prepared after the design is complete tells a different story: what the chosen product is likely to cost, whether or not the market will pay enough for it.

Use a credible net selling price, after the discounts and allowances expected for the actual customer population. Keep the evidence for price separate from the desired margin. Neither a revenue target nor an attractive competitor price proves that the proposed product can earn that amount.

ACCA's discussion of target and lifecycle costing connects the market price and required profit with costs incurred before, during and after production. The calculation below applies those ideas to an original hypothetical product. It is a management planning view, not a policy for capitalizing development or recognizing expenses in statutory accounts.

Suppose the proposed net price is $120 and the business requires a 25% margin on revenue. The allowable lifecycle cost is $90 per unit: $120 less $30 of required profit. At an assumed lifetime volume of 20,000 units, revenue is $2.4 million, required profit is $600,000 and total allowable cost is $1.8 million.

The plan also contains $400,000 of development and launch work, $180,000 of support infrastructure and $20,000 of final retirement work. For this illustration, those $600,000 of non-unit costs are assumed fixed across the volume range being considered. They leave $1.2 million for making and delivering 20,000 units, or $60 per unit.

If the current design requires $68 per unit, total lifecycle cost becomes $1.96 million. Expected profit falls to $440,000, about 18.3% of revenue. The design has a $160,000 cost gap against the 25% margin requirement, equivalent to $8 per expected unit. The gap should be visible before the product is approved.

A 25% margin means profit is 25% of selling price. A 25% markup means profit is 25% of cost. At a $120 selling price, a 25% markup permits $96 of cost because $96 multiplied by 1.25 equals $120. That leaves $24 of profit, a 20% margin on revenue.

The distinction changes the cost allowance by $6 per unit in this example. Across 20,000 units, that is $120,000. Put the profit definition in the approval record and show the formula instead of relying on an unlabeled percentage in a spreadsheet.

Also define the profit measure. A gross margin target and a lifetime operating contribution target may include different spending. The $90 allowance above covers the stated lifecycle costs; it should not be compared with a manufacturing-only estimate while development and support disappear from the discussion.

At 15,000 lifetime units and the same $120 price, revenue would be $1.8 million. A 25% margin permits $1.35 million of cost. If the $600,000 non-unit commitment remains, only $750,000 is available for unit-related costs, or $50 per unit.

Using the current $68 design at that volume gives $1.02 million of unit-related cost and $1.62 million total cost. Profit is $180,000, or 10% of revenue. The lower demand case therefore changes the allowable design cost and the margin materially; it is not just a smaller copy of the central forecast.

Revisit the supposedly fixed support estimate as well. Support may rise with the installed base or remain necessary for longer if sales are slower. Show how volume, selling duration and support obligations interact instead of assuming all non-unit spending stays fixed under every scenario.

Check costs calculated as a percentage of the selling price. If the offer also requires a 5% royalty that is absent from the $68 estimate, it consumes another $6 per unit at the proposed $120 price. The remaining allowance for making and delivering the item falls from $60 to $54. A target-cost worksheet should expose that dependency so a later price change also updates the royalty, rather than leaving a fixed dollar assumption behind.

Break the $8 unit gap into decisions the team can evaluate: components, assembly time, testing, packaging, delivery, serviceability or feature scope. Give each proposed change an owner, a supported saving and the customer or operating consequence. A single cost-reduction percentage applied to every line does not explain how the target will be reached.

Watch for cost shifted into another stage. A cheaper component can require more support, and a simplified assembly can make later repair more expensive. Evaluate the full consequence over the expected life, including failure rates supported by testing. The plan should preserve required performance and obligations while changing the design economics.

If the gap cannot be closed, revisit the proposed offer, evidence for a different price, launch scope or decision to proceed. Keep those options explicit. Labeling an unsupported future supplier concession as a saving only hides the unresolved commercial decision.

The lifecycle total adds amounts across the product's life. It does not show when money is paid or collected. Development may consume cash well before the first sale, while support and retirement spending can continue after new sales finish. Add a dated cash schedule and use an appropriate investment appraisal where timing is material.

Keep already spent development visible in the full product outcome, but distinguish it from future costs when deciding whether to change or stop the project. The historical amount may explain overall profitability without being avoidable through today's decision. Retain both views so the team can learn from the project and still make a sound next choice.

At each design release, update the costed specification, committed spending, remaining estimates and sales assumptions. Compare the latest supported lifecycle cost with the approved allowance. A target is useful when it exposes a decision before the commitment, not when it survives unchanged beside a growing collection of unexplained exceptions.