Evaluating Platform Strategies

A platform strategy has to succeed twice: as a product and as a platform. Everything you would normally evaluate about a product strategy still applies, and then a whole additional layer of platform-specific criteria sits on top of it, deciding whether the thing will ignite and defend itself as a platform at all. The trouble is that this second layer is the part teams handle worst. The platform criteria are less well understood than the product ones, stakeholders often don't recognize them as critical, and they frequently aren't even instrumented for monitoring, so they get evaluated loosely or skipped entirely. A platform strategy can look attractive on every product dimension and still be a bad platform bet.

So evaluating a platform strategy means giving that second layer the weight it deserves: testing the platform-specific questions as rigorously as the product ones, and recognizing that a few of them are make-or-break, disqualifiers rather than line items you average into a score.

Disqualifiers, not a scorecard

Product evaluation is mostly additive. Strengths and weaknesses trade off; a product that's weak on one dimension can still win on the strength of others, and the job is weighing the balance.

Platforms don't work that way on their most important criteria. A platform that never reaches critical mass doesn't underperform; it doesn't happen. A platform whose complementors can't earn a better return building on you than they'd earn elsewhere doesn't grow slowly; it fails to attract them at all. These aren't points to be averaged against a strong technology story. They're gates. The first discipline of evaluating a platform is knowing which criteria are gates and being willing to fail the whole hypothesis on one of them, however good the rest looks.

The questions a platform has to answer

A useful platform evaluation works through a specific set of questions. We group them into six categories, each asking something a product evaluation typically doesn't.

• Evolving system of use. Is there a genuine system of use here, one whose value grows as more people adopt and build on it? Two things make it real. The field of use has to be broad enough to leave room for many value-adding complementors, not a narrow slot only you can fill. And it has to have a long runway of potential evolution, so the platform can keep creating and enabling new value for years rather than exhausting its usefulness once the obvious needs are met. Seeing that runway takes long-term vision and the ability to imagine what the system could become. A one-time product with an add-on marketplace is not this; if the system of use doesn't compound with adoption and keep evolving, you don't have a platform, you have a product and a partner program.
• Adopter critical mass. Is there a credible path to the critical mass that makes the platform self-sustaining, judged as share relative to the alternatives, not as an absolute number? Critical mass is a moving target that rises as the ecosystem grows, and platforms often ignite only after a product has earned enough standalone adoption to light the fire. If you can't describe how you cross that threshold, the rest is academic.
• Complementors. Why will complementors invest, and will their return building on you beat what they could earn on their own or on a rival platform? Complementor ROI is the engine. If the answer is vague, or depends on complementors acting against their own economics, the platform won't build.
• Value capture. How does the platform owner actually capture value, and does that capture leave the ecosystem healthy? A platform that extracts everything starves the complementors it depends on; one that captures nothing subsidizes a market it never harvests. The value-capture logic has to work for both sides at once.
• Competing platforms. Who else is trying to be the platform in this space, and what happens when the market tips toward one? Platform competition tends to resolve toward a small number of winners, so evaluating in isolation, as if you were the only candidate, is a common and expensive mistake.
• Organization. Can your organization actually carry a platform? A platform demands different resources, processes, and priorities than a product business is tuned for, and a strategy your company can't govern or sustain fails regardless of how good the idea is. That organizational-fit question belongs inside the evaluation, not as an afterthought once the strategy is chosen. (We treat it in depth in our work on Resources, Processes, and Priorities.)

Any one of the first four can be the disqualifier. The last two shape whether a sound platform can win and whether your company is the one to run it.

Evaluate it as an evolving hypothesis

None of this is a one-time scoring exercise. A platform strategy is evaluated the way any strong strategy hypothesis is: at a fidelity appropriate to where the work is, against evidence, with the bar rising as the commitment grows. Early on, thin, order-of-magnitude answers earn the right to keep exploring, because the investment is small. As real money comes into view, the criteria grow in number and rigor until there are dozens of factors informing the decision, all of them driven by evidence rather than the calendar. The point of the evaluation isn't to produce a number; it's to expose the assumptions the platform depends on and direct your evidence-gathering at the ones that would sink it.

Evaluate the platform on its own terms

The mistake worth avoiding is grading a platform strategy on a product-strategy curve, where a great technology story or an enthusiastic early customer papers over a missing complementor economics or an unreachable critical mass. Evaluate it on its own terms: work the platform-specific questions, treat the decisive ones as pass-or-fail, weigh it against competing platforms rather than in isolation, and make sure your organization can actually carry it. And let evidence, not the calendar, set the bar as the stakes rise.

Turning that into a repeatable discipline, defining the platform hypothesis explicitly and evaluating it against criteria like these, is exactly what our consulting work and Growth Forge® Software are built to make repeatable. Once a platform strategy clears the evaluation, the work shifts to running it, which is its own distinct discipline.

BRI Associates helps companies grow by drawing on decades of practitioner experience in corporate innovation and new business development — practitioners, not pundits or academics — through direct consulting, training workshops, and Growth Forge® Software, built for the unique requirements of corporate innovation and growth organizations.