A Product Expansion Must Earn the Right to Share the Brand

The falling cost of building software is creating a new product problem: companies can now enter categories that they have not earned the right to occupy.

We can see the temptation everywhere. Consumer platforms are adding payments, recommendations and transactions. SaaS products are attaching AI capabilities because comparable features can be built quickly. At the same time, some AI products are shutting down, infrastructure spending is under greater scrutiny and large companies are publicly signalling that they do not want to release AI simply for the sake of having it.

The relevant question is no longer whether an adjacent feature can be built. In many cases, it can. The harder question is whether it should share the same product and brand.

I think every expansion should have to pass three tests: shared trust, shared behaviour and shared economics.

Shared trust means customers believe the company is a credible provider of the new capability. A restaurant discovery product may have permission to offer reservations because the new action follows naturally from the existing decision. That does not automatically mean it has permission to handle payments, provide financial advice or manage sensitive identity data. The technical distance between those features may be small. The trust distance can be enormous.

Shared behaviour means the expansion strengthens an existing customer habit rather than asking the customer to create an unrelated one. If users already open a product to decide where to eat, booking a table can complete that journey. Adding a loosely connected service because the same account and interface can accommodate it is not the same thing. Login convenience is not product coherence.

Shared economics means the new capability makes the overall business healthier. It may increase retention, improve conversion, reduce service costs or create a credible additional revenue stream. But this has to be measured after including support, compliance, infrastructure and the distraction imposed on the rest of the organisation. A feature can attract usage while still weakening the company.

In roadmap discussions, I often see teams make the case for expansion through customer interest. Customers asked for it. A prototype tested well. A competitor launched something similar. These are useful signals, but they are not sufficient. People will try plenty of features that should never become lasting parts of a product.

This is especially dangerous with AI. A team can add an assistant to an existing workflow and generate immediate curiosity. Yet the assistant may introduce new failure modes, unpredictable costs and expectations the company cannot consistently meet. If it is unreliable, customers do not neatly separate the experimental feature from the established product. The core brand absorbs the disappointment.

Easy copying increases this risk. When competitors can reproduce visible functionality quickly, adding more features does not necessarily create a stronger position. It can instead make the product harder to understand. Customers stay because a product repeatedly solves an important problem, not because its navigation contains the longest list of possibilities.

Product leaders therefore need to treat brand scope as a strategic constraint. Before approving an adjacency, I want to know which existing customer belief it builds on, which current behaviour it completes and which part of the business becomes structurally better. If the answers require a long explanation, the feature probably belongs in a separate experiment, a different product or nowhere at all.

This is not an argument for narrow products forever. Strong products do expand. But good expansion makes the original promise clearer and more useful. Bad expansion uses technical possibility as a substitute for strategy.

When building becomes easier, restraint becomes more valuable. The companies that benefit will not be those that attach the most capabilities to one account. They will be those that understand exactly why each new capability belongs there.