Kotler’s five product levels

Kotler’s product-level model expands an offer from the customer’s underlying benefit to the future possibilities around it. It helps teams compete on the complete experience rather than equating “product” with a physical object.

When to use it

• Use the model to clarify customer value, differentiate an offer and identify augmentation that improves willingness to choose or pay.
• Apply it to products, services and mixed offers, validating each layer with customers and economics.

Origins

Philip Kotler presented the five product levels in Marketing Management, first published in 1967. The approach also reflects Theodore Levitt’s argument that businesses should define themselves through customer needs rather than the current form of a product. Kotler emphasised that competition often shifts toward augmentation such as service, delivery, advice and brand.

What it is

Need, want and demand provide context: a need is the underlying problem; a want is a preferred way to satisfy it; demand adds ability and willingness to obtain the offer.

The five levels are:

1. Core benefit: the outcome the customer is buying. An airline passenger buys transport between destinations.
2. Basic or generic product: the minimum form that delivers the benefit, including a flight, schedule and safety capability.
3. Expected product: the conditions customers normally anticipate, such as acceptable comfort and service.
4. Augmented product: differentiating services and signals beyond the expectation, such as reputation, support or loyalty benefits.
5. Potential product: future transformations or additions that may create value, including a more complete service or a deliberately simplified version.

Value and cost must be assessed across the whole offer. An augmentation that customers do not value can reduce margin or add complexity; a core failure cannot be repaired by attractive packaging.

Developments of the model

Levitt’s “marketing myopia” warned that firms can fail when they define the business by a current object rather than the job customers need done. The buggy-whip example illustrates the point: capabilities might have been redirected toward components or materials as transport changed. The lesson is not that every incumbent can pivot, but that need, capability and market evidence should be distinguished.