Product Management · Business Case
Should OpenDesign open a first-party plugin marketplace in Q3? One decision for PM, Eng, Design, and Leadership to land on.
Decision owner: PM · Reviewers: Eng, Design, Leadership
217+ plugins already exist, built for free by the community — discoverable only through a static home rail, with no ratings, no revenue share, no owner of record. One call, before Q3 planning locks.
The Pain
68% of installs come from the top 6 home-rail plugins; the other 211 get near-zero traffic
No ratings, no verification badge — support tickets show users afraid to install unfamiliar plugin code
38 external contributors shipped a plugin this year; only 4 shipped a second one
112 GitHub issues this quarter trace back to plugins with no listed maintainer of record
Every pain point traces to the same root cause: plugins have no marketplace, so they have no owner, no signal, and no incentive.
Options Considered
$ od plugin marketplace --compare-options
# three options weighed for Q3 option_a: status_quo # home rail only, curated by us trust_signal: none creator_incentive: none effort: low option_b: reviewed_marketplace # submission queue + revenue share trust_signal: verified_badge creator_incentive: 70/30_split effort: medium option_c: open_federation # npm-style, no review, self-serve trust_signal: none creator_incentive: tips_only effort: low recommended: option_b # only option that fixes trust AND incentive
Tradeoffs
added time-to-ship for review tooling
creator revenue split, our favor 30%
creators committed for private beta
Recommendation
This is the irreversible step: once revenue share is live, pulling the marketplace back costs trust we won't get back. Sign off here, not after Aug.
Measure of Success
$ od plugin marketplace --track long-tail-install-share
→ Target: 24% → 45% by Q4
Option B — reviewed marketplace with revenue share. Sign-off requested from PM, Eng, Design, and Leadership by Jul 21.