TL;DR

  • Many companies try to write one positioning statement for structurally different things.
  • A product, product line, platform, and company are not interchangeable positioning targets.
  • The broader the entity, the broader the message becomes. That is useful for investors and analysts, but often useless in actual buying decisions.
  • The rule is simple: position at the level where buyer, competitor set, and value delivery are still consistent.

Teams often say they need positioning when what they really need is a choice about scope.

They start a company-level project because that sounds more strategic. Then halfway through, the work gets dragged toward product details because sales needs something usable. Or the company acquires another product, launches a new module, or starts talking about a platform strategy and suddenly the original statement is so broad that it describes everything weakly and nothing clearly.

That is not usually a failure of the framework. It is a failure to decide what entity the work is actually about.

A positioning statement broad enough to cover structurally different products is usually too broad to win a real deal.

"The company narrative connects products. Product positioning sells them. When teams force those into one statement, they usually lose both."

— Jake McMahon, ProductQuant

The cost is immediate. Sales writes its own messaging. The website starts sounding like category wallpaper. Product marketing cannot tell whether it is speaking to a specific buyer or to an imaginary umbrella audience.

This confusion gets worse as soon as the company introduces a second structurally different offer. One team wants a product story that wins a live evaluation. Another wants a company story that sounds expansive enough for analysts, recruiting, or investor decks. Both needs are real. The mistake is pretending one statement can solve both at the same level of specificity. When altitude is wrong, clarity collapses first.

What Exactly Might You Be Positioning?

There are usually five distinct possibilities.

1. A single product

This is the cleanest case. One product, one buyer set, one main alternative set, one value delivery model. Positioning is most useful here because the competitive reality is still tight.

2. A product line

A product line can share an audience while still needing some internal structure. The positioning has to explain how the pieces relate and why buyers would want more than one.

3. A company

Company positioning matters for investors, analysts, recruiting, and enterprise vendor evaluation. It is usually broader and more narrative-driven than what a specific product buyer needs.

4. A platform

Platforms are positioned differently because the story is not just about direct user value. It is about extensibility, ecosystem logic, developer adoption, and third-party leverage.

5. A portfolio

This is the hardest case. A post-acquisition or multi-product portfolio may contain products with different buyers, different competitors, different pricing logic, and different growth motions. In that case, forcing one product-style positioning across the portfolio usually produces empty language.

EntityBest audienceMain jobCommon mistake
Single productBuyers and usersWin real evaluationsMaking it too broad
Product lineExisting buyers expanding usageExplain relationship and breadthBlurring distinct use cases
CompanyInvestors, analysts, enterprise vendor evaluatorsTell the umbrella storyTrying to use it in product-level deals
PlatformBuilders, technical stakeholders, ecosystem partnersSell extensibility and leveragePositioning it like a single feature-rich app
PortfolioLeadership and market-facing teamsConnect distinct products under one narrativeForcing one message across conflicting structures
Positioning

Pick the altitude before you pick the words.

The same messaging cannot carry a single-product deal, a portfolio narrative, and an investor story equally well.

How Can You Tell You Are Positioning the Wrong Entity?

There are three common signs.

First, the official statement works for too many different products. If you can swap product names and nothing meaningfully breaks, the statement is probably operating too high above the product's actual competitive reality.

Second, sales creates product-specific messaging within weeks. That usually means the market-facing teams still need product-level positioning, even if the company-level narrative exists.

Third, the competitive alternatives change by product. If one product competes against spreadsheets and another competes against enterprise suites, those are different competitive contexts. One statement rarely solves both cleanly.

The practical rule is straightforward: position at the level where the structural characteristics stay consistent. If buyer, competitor, pricing, or value delivery diverge, separate the positionings and connect them with a lighter company narrative above them.

What Should Teams Do Instead?

Run a short pre-check before any positioning project starts.

  • Name the entity explicitly. Product, product line, company, platform, or portfolio.
  • Check whether buyer, competitor, and value delivery stay consistent at that level.
  • If they diverge materially, split the work.
  • Keep company narrative and product positioning separate on purpose.
  • Test whether a salesperson could actually use the final message in a real deal.

Most companies do need some kind of umbrella story. They just should not confuse that with the message that helps a buyer choose one product over its actual alternatives.

The cleanest mental model is this: company narrative explains the portfolio; product positioning wins the deal.

FAQ

Can a multi-product company still have one positioning statement?

It can have one umbrella narrative, but that is not the same as one deal-ready positioning statement for every product. Product-level messaging usually still needs to exist.

When should a team use company positioning?

Company positioning is most useful for investor conversations, analyst briefings, recruiting, enterprise vendor evaluation, and high-level market narrative.

Why do portfolio companies struggle here so often?

Because structurally different products often get forced under one message even when they have different buyers, different alternatives, and different ways of creating value.

What is the fastest diagnostic question?

Ask whether one salesperson could use the statement in a real live deal for a specific product. If the answer is "it depends which product," the altitude is probably wrong.

Sources

Jake McMahon

About the Author

Jake McMahon writes about competitive positioning, product structure, and the strategic mistakes B2B SaaS teams make when they try to force one message across products with different buyers and value models. ProductQuant helps companies separate product-level positioning from company-level narrative before the site and sales story go generic.

Next step

If the message feels broad, check whether the scope is wrong before rewriting the copy.

ProductQuant helps teams separate product positioning, company narrative, and portfolio storytelling before they collapse into category wallpaper.