We have three products now. Do we message them separately or tell one platform story?
Decide by how they are bought, not by how they are built. If the same buyer, out of the same budget, buys them in one conversation, you need one positioning with the products as capabilities underneath it. If different buyers with different budgets buy them independently, each product needs its own positioning and the company name sits above as an umbrella. Almost everyone errs the same way, inventing a platform story for a suite the market still buys one product at a time, after which the sales team quietly goes back to selling product one. A suite pitch is only honest when the products are genuinely better together, and that is a product commitment before it is a slide.
Go deeper
5 resources, 2 India-specific, 5 link-checked.
📄 Article
✓ Link checkedFreeIntermediate
Dunford's rule that you build for the champion rather than for every persona in the account settles the buyer versus user argument faster than any framework. It also stops teams building four sets of messaging they will never maintain.
Deals with the four places positioning work actually stalls, including teams that cannot agree on their competitive alternatives. Useful once you have tried positioning and it went nowhere.
The clearest Indian example of a company outgrowing its own product name and building an umbrella brand over Freshservice, Freshsales and Freshcaller. Read it as a case in timing: they renamed before shipping more products, not after.
Zoho bundling dozens of apps into one subscription, priced at Rs 1,000 per employee per month in India, is the opposite bet to per-product positioning. A useful counter-example when you are deciding whether your suite story is real.
Exactly your decision, worked through with two examples and the segment problem that comes with it. Dunford also covers when a company story on top is right and when it is the invented platform narrative you are trying to avoid.
