Launch Playbook for Ecosystem and Marketplace Launches

A marketplace launch with two messages — one for buyers, one for partners — is already broken. It's three messages, minimum, and most teams ship with one.

The standard launch playbook assumes a single buyer reading a single page. Ecosystem and marketplace launches violate that on day one. You're recruiting builders who need to believe demand will arrive, buyers who need to believe supply already has, and an internal sales team who need to know whether they're closing platform deals or app deals or both. Each side reads a different page, hears a different pitch, and signs on for a different reason. If your positioning brief has one ICP block, you're going to ship a launch that lands for one audience and bores the other two.

A marketplace is not a product. It's three products that share a URL.

What "multi-sided" actually means for the brief

The single-audience launch brief — buyer pain, product claim, proof, CTA — is a four-cell grid. The multi-sided brief is the same grid run three or four times, with explicit calls to where the messages overlap and where they conflict.

The conflict is the part teams skip. A buyer wants to hear that the marketplace is curated and quality is high. A partner wants to hear that the bar to list is low and discovery is fair. Both can be true, but the language has to be deliberately different — and the homepage can only foreground one.

The platform-side audience is the one most teams forget. Your AEs need to know whether the marketplace is a deal accelerator (mention on every call), a deal complicator (only mention when asked), or a separate motion (don't mention on core sales calls at all). Without that decision in writing, half your sellers will ignore the launch and the other half will lead with it.

The sequencing problem

Single-product launches sequence audiences by funnel stage: awareness, consideration, decision. Marketplace launches sequence by side — and the order matters more than most teams realize.

You cannot launch buyer-side on day one. An empty marketplace is worse than no marketplace; it tells the buyer the ecosystem is dead. You need partners listed, integrations live, and at least three named launch apps before the buyer-side page goes public. That means partner recruitment runs four to eight weeks ahead of the buyer-facing announcement, in a quieter register, with a different page.

3-5

The quieter register is intentional. Partner recruitment in stealth gives you flexibility on terms, lets you fail privately with the wrong builders, and avoids tipping the news cycle before buyer-side is ready. It also lets your first partners feel like founding partners, not vendor #47, which materially affects how hard they'll co-market.

C

We made the mistake of announcing the marketplace and the partner program in the same press release. Partners felt like a footnote, builders ignored us for six months, and we had to relaunch the program quietly the following quarter.

The nine-step sequence

The template below is the version we hand to PMM teams running their first ecosystem launch. It assumes you have a working product, a defined platform surface (API, SDK, or app framework), and at least one signed partner — if any of those are missing, you're not launching, you're scoping.

Where the messages have to overlap

Three audiences, three briefs, but one brand. The overlap is the connective tissue and it has to be deliberate, not accidental.

The shared message is almost always about the platform's role in the buyer's workflow, not about the marketplace itself. "We're the system of record for X" or "we're the orchestration layer for Y" works for all three audiences because it tells the buyer why integrations matter, the partner why distribution is real, and the AE why the marketplace makes the platform stickier.

When the marketplace becomes the headline ("the largest marketplace for…"), you've inverted the hierarchy. The buyer now evaluates you as a directory, the partner sees a crowded shelf, and the AE has nothing to anchor to in a deal review. Marketplaces are proof; platforms are pitches.

What goes wrong, and what the warning signs look like

Six failure patterns from ecosystem launches that underperformed

The pricing inversion is the one most teams miss. If a partner-built app for outbound enrichment costs $400/month and the native enrichment feature is included in the platform tier, buyers ask the obvious question and someone in sales has to answer it on the call. The answer should be in the launch brief, not invented in real time.

We treated the marketplace like a feature launch. It's a market launch. The difference is that markets don't work if one side shows up and the other doesn't.

The template

The Ecosystem Launch Template covers the three positioning briefs, the partner-recruitment timeline, the platform-side decision worksheet, and the thirty-day dual-scorecard review. It's the document we use with PMM teams running their first ecosystem launch, and a checklist for teams running their fourth.

What to do Monday

Pull your most recent launch brief — single-product or otherwise — and try to write the partner-side and platform-side versions from the same source material. If you can't, that's the gap. The next launch is where it gets expensive.

Frequently asked