The second product problem.

§I One SKU is a business, not a brand.

The first product of a consumer brand is not, in most cases, the brand. It is a business. A brand begins, architecturally, with the second product. This is a statement founders flinch at, because they have spent eighteen to thirty-six months personally shepherding the first SKU to market and it is not unreasonable for them to regard it as the brand in full. It is not. It is the opening argument. The second product is where that argument either holds or breaks.

What a founder discovers, the moment they begin work on the second product, is that everything they thought was the brand was actually the product. The story was held in place by the container of a single SKU. The second product, by introducing a second container, makes visible the question: is this a brand with two products, or two products that share a label?

The answer to that question is rarely a formulation decision. It is almost always an architecture decision. And the architecture, unfortunately, has to be made before the second product itself exists — which is why most founders treat it as a formulation problem after the fact.

§II The range argument, restated.

We talk, with founders, about two architectures. The first is the range argument: the second product sits alongside the first, within a shared category logic, with a visible and legible family resemblance. The range argument is what most legacy consumer brands use. It is reliable and it compounds.

The second architecture is the system argument: the second product occupies a related but distinct category, bound to the first not by shelf adjacency but by the brand's point of view. This is what Aesop does between its skin and its body ranges. It is what Le Labo does between its fragrance and its home range. It is what Who Gives A Crap does between its toilet paper and its tissue range. The system argument compounds differently, more slowly, and to a higher asymptote.

The two arguments are not interchangeable. A brand that tries to make a range argument from two products that do not share a category logic produces a confused shelf. A brand that tries to make a system argument from two products that are category-adjacent produces a diluted shelf. We see both, weekly. Neither converts.

The second product is not a product decision. It is the first real brand decision the founder makes, and most founders make it unknowingly. — Glow Group, strategy deck framework

§III The four wrong answers.

There are four dominant wrong answers to the second product problem, and we see them in roughly this order. The first is to make a bigger version of the first product. This is a packaging decision dressed as a brand decision; it adds revenue and subtracts brand information. The second is to make a cheaper version. This halves the brand's authority in both SKUs. The third is to make a line extension into an adjacent category the founder does not personally care about. This is the most expensive mistake in our file.

The fourth, subtler, wrong answer is to make a second product that is correct but prematurely launched. Correct architecture, wrong sequencing. The brand had not yet earned the room to make the second argument. This is the most common error in the category, and the one dashboards are worst at preventing. The dashboard sees incremental revenue, not brand debt.

What the four errors share is that each one converts a brand decision into an operational one. The formulation is argued. The pack is argued. The price is argued. The underlying architecture question is never asked.

§IV The right answer, described operationally.

We sit the founder down, with the second product still only a hypothesis, and ask four questions. One: does the second product make the first product taste more correct, more coherent, more like itself? Two: does the second product survive being described without reference to the first? Three: is the founder personally interested in the second product, at the resolution they were personally interested in the first?

The fourth question is the sequencing one: has the first product been boring for two consecutive quarters? If it has not — if the founder is still fussing with the first SKU — the second product is premature, full stop. The brand has not earned room for a second argument. Add the room first.

If the answers to the four questions are yes, yes, yes, and yes, the second product is a brand decision and should be treated as one. The formulation comes later; the architecture comes now. This is the move the compounding brands make, quietly, every time.

§V What the right answer pays.

The second product, done correctly, is the first proof that the brand has a point of view at all. Until then, the point of view is hypothetical; it could be anything the founder claims it is. The second product forces the point of view to show up in material. Once it shows up in material, the brand becomes investable, the retailer begins to understand the architecture, and the customer begins to anticipate the third product before it exists.

This is what compounding looks like at the architecture layer. Most founders do not believe, when they are in it, that the second product is a larger decision than the first. It is. The first is a business. The second is a brand. The third is, with luck, a category reshape. You do not get to the third without doing the second correctly.