Go where the users already are. Pick the anchor surface, build native to it, and stop pitching the next big platform as a destination.
Which platform actually carries your audience. Not the one your investors keep mentioning.
Build for the surface's grain, not portable across many. The cost of native compounds; the cost of portable accelerates.
Cost per surface install vs. lifetime spend inside that surface. The number that matters.
Surface-side integrations, featured placement strategy, partner program ROI reads.
When to add the second surface. Almost never the answer you came in with.
Real cohort behavior. Not survey data, not investor charts. Which surface holds the audience now.
Choose the anchor. Commit. Building portable across five surfaces is how teams ship nothing twice.
Use the surface's native primitives. Discord = thread mechanics. Telegram = forwarded message. Roblox = lobby.
Surface-specific live-ops, partner positioning, defensibility against the platform owner.
Telegram (Rugs to Riches, native publishing), web/MMO (Ember Sword), Steam (multiple Top-5 titles), Roblox and Discord on advisory engagements, plus open-web AI tools.
Portable across five surfaces is how teams ship nothing twice. Native to one surface is how teams ship something users actually pass around.
Real risk. Defensibility planning is part of the engagement: surface-side relationships, IP control, multi-surface fallback when the math justifies it.
Yes. Each has different grain and different distribution math. We pick based on audience cohort behavior, not on the surface that's trending in pitch decks.
Cross-platform plans without an anchor surface. 'We'll be everywhere' strategies that delay shipping.
Yes — see 'Why the next big platform won't look like one' in our Insights for the underlying frame.