A marketplace launch — the kind where you ship inside Salesforce AppExchange, AWS Marketplace, the HubSpot ecosystem, or a vertical platform like Epic or Workday — fails in ways a standalone launch can't. By "ecosystem launch" we mean any go-to-market motion where a platform partner sits between you and the buyer, and where their incentives, their listing rules, and their co-sell motion shape what you can say and to whom. You're not running one launch. You're running three at once: one to the platform's product team, one to the platform's field, and one to the end buyer who finds you through the listing.
Most PMMs run them as if they were a single launch with extra logos.
The number isn't a marketplace problem. It's a positioning problem. The seller wrote one story, posted it in the listing, and assumed the platform's gravity would do the rest. It doesn't.
What makes ecosystem positioning structurally different
A direct-sale launch has one buyer, one story, one moment of truth. An ecosystem launch has at least three audiences who each need a different argument, and the arguments have to be consistent without being identical.
The failure mode is the part PMMs underweight. Marketplace listings convert installs cheaply. They convert retention expensively, because the buyer arrived without the context a normal sales cycle would have given them. If the listing oversells, the install cohort looks great and the 90-day cohort looks awful.
A marketplace listing is not a landing page. It's a sales rep that never sleeps, never qualifies, and never renegotiates the promise.
The three positioning briefs you actually need
Before you draft a single piece of launch copy, write three short briefs. One page each. Same product, three lenses.
The order matters. Most teams draft the buyer-facing brief, hand it to the listing team, and discover halfway through review that the platform's listing rules forbid two of their core claims. Working backwards from the platform constraints saves a re-positioning sprint.
The differentiation triangle
For ecosystem launches, the standard "us vs. them" comparison fails. You need a triangle, not a line.
If you can only beat one of the two corners, you have a feature, not a product.
A clean test: explain in three sentences why a buyer would pay you instead of (a) using what's free in their seat, and (b) installing the cheaper listing one row above yours in search. If either sentence is hand-wavy, your positioning brief isn't done.
Sequencing the launch
Direct launches are usually two phases: pre-announce and announce. Ecosystem launches need four, and skipping any of them shows up later as a co-sell complaint or a churn cohort.
We treated the listing like a landing page for the first six months. Installs looked great. Then the renewal data came in and we realized the marketplace cohort was churning at 3x our direct cohort. The fix was rewriting the listing to qualify out the wrong-fit buyer.
What to put in the listing itself
Marketplace listings are constrained — character counts, banned words, mandatory categories. Inside those constraints, the listings that retain best share four traits.
Listing copy that converts and retains
The metric that matters
Ignore install count for the first quarter. The number that tells you whether the launch worked is 90-day net retention by acquisition source, segmented into listing-direct, partner-referred, and self-referred. Listing-direct will be the worst of the three for most teams in their first year. That's not a failure — it's the unqualified-traffic tax. The question is whether it's improving.
We stopped reporting marketplace installs to the board after Q2. We reported 90-day retained ARR by source. The conversation about partner investment changed in one meeting.
What to do Monday
Pull your last ecosystem launch — or your draft of the next one — and answer four questions on a single page:
- Who is the platform PM whose roadmap you're filling, and what's the one sentence that describes the gain to them?
- What does the platform's native feature do, and where does it break?
- Which two competing listings are in your category, and what's the one sentence that distinguishes you from each?
- What's the install-cohort metric you'll report to your CMO at day 30, day 60, and day 90 — and is it the same metric the platform partner manager will be asked about?
If any of the four answers takes more than two sentences, the positioning brief isn't done yet. The launch that follows will inherit the fuzziness, and the marketplace will be unforgiving about it.
Keep reading
How to Build Battle Cards That Sales Actually Uses
Tactical guide to battle cards that field reps open during live deals — not the ones that rot in Drive two weeks after they ship.
When to Refresh Your Positioning (Not Just Your Messaging)
How to tell whether the problem is positioning or execution — the four signals that mean the thesis is wrong, not the copy.
Positioning Audit: How to Score Your Own Work Objectively
Scoring your own positioning is structurally hard — you wrote it. Six disciplines that reduce the bias without outsourcing the audit, plus the rubric.
Launch Playbook
Ship launches that land a point of view — not just a feature list.
Launch Playbook drafts your announcement copy, FAQ, and battle-card patch from your Strategic Context the moment you're ready to ship. Evidence-based, grounded in your positioning, built to be sent — not just presented.
- ✓Drafts announcement, FAQ, and battle-card patch
- ✓Grounded in your positioning, not a generic template
- ✓Ready to ship in the time it takes to brief an agency