Why a second category is harder than a second city

From outside both look like “plus one unit”. In practice they load the company differently, and confusing them is expensive.

Copying versus inventing

When entering a new city, parts of the operating model can be transferred: recipes, training, roles and quality controls. Logistics, team and local demand still need separate validation. A new category adds another layer: a different product standard, suppliers and quality criteria.

A city therefore tests the portability of the existing model, while a category tests the limits of its applicability. This is a working hypothesis for BOOST BRANDS decisions, not a universal rule for every business.

Where the shared layer breaks

The point of the system is that categories use a shared customer and operating layer. But a shared layer is not universal by default: quality metrics for coffee and for food do not reduce to each other, supply cycles differ, and the visit context overlaps only partially.

So the question before entering a category is not “can we sell this”, but “what exactly from the working layer applies here without being rewritten”.

Four entry criteria

• The category increases the frequency of useful contact, not the number of signboards.
• It can use shared data, processes and a team without requiring an independent system alongside.
• It strengthens the operating system rather than duplicating it with another team and other rules.
• It does not break the discipline of the existing business: attention to the core operation does not drop.

If even one criterion fails, the category stays in roadmap or vision status. That is not a refusal — it is a refusal to announce a launch before it is justified.

Why we do not name dates

Entry timing depends on when the shared layer survives testing, not on a calendar. A named date would turn a roadmap into a promise, and we keep those statuses apart on purpose: a pilot is not a product, a roadmap is not a result, a vision is not an obligation.