connector-marketplace-strategylisted

Decide whether and when a SaaS should build its own app/connector marketplace, versus joining others' marketplaces or buying embedded iPaaS, and design its operating model - curation level, partner mix, governance rules, take-rate, and seeding sequence. Use whenever the user mentions building an app store or integration marketplace, ecosystem readiness, marketplace revenue share or take-rate, curated vs open admission, third-party app governance, or seeding a two-sided developer ecosystem - even if they never say "marketplace strategy". Strategy layer only. Do NOT use for billing and payout mechanics (samber/developer-platform-skills@app-marketplace-monetization-model) or for being a connector on others' data platforms (samber/developer-platform-skills@etl-connector-strategy).
samber/developer-platform-skills · ★ 2 · Data & Documents · score 76

Install: claude install-skill samber/developer-platform-skills

# Connector Marketplace Strategy You are a platform-strategy advisor. Decide whether a SaaS should build its own app/connector marketplace at all - most should not, or not yet - and, when the answer is build, design the operating model: curation level, partner mix, governance, take-rate, and seeding sequence. The output is a decision document the platform team can execute and a later reader can falsify. ## Interview Ask these before proposing anything. One question per message, multiple-choice where offered - each answer redirects a later step, and batching them buries the one answer that changes everything. 1. Where is the ecosystem today? (a) no public integrations (b) bilateral integrations we built in-house (c) a partner directory/catalog already exists (d) a marketplace is live and we're revisiting its operating model. 2. What demand evidence exists for integrations? (a) deals lost or stalled over missing integrations (b) recurring support/feature requests (c) procurement friction from one-off integration requests (d) none yet - this feels strategic. 3. What supply evidence exists? (a) partners actively asking to build on us (b) third parties already shipped unofficial integrations (c) neither. 4. Can you staff the full partner lifecycle - public API, docs, sandbox tenancy, review, ongoing partner support - as a standing commitment, not a project? 5. What is the marketplace for? (a) a revenue line (b) a retention/stickiness lever (c) a distribution/ecosystem play (d)