Skip to content

BDR-0005 – Marketplace Phasing

  • Type: Business Decision
  • Status: Accepted
  • Date: 2026-01-01
  • Owner: Dmitry
  • Related Areas: Business Model / Marketplace / Strategy / Roadmap

This decision document defines when and how ConnectSoft will launch its marketplace. It is written for product managers, architects, and anyone planning the marketplace roadmap.

Decision

Marketplace is Phase 3+, after Factory and Platforms are proven. Phasing: Phase 1 (internal-only catalog), Phase 2 (private marketplace for enterprise), Phase 3 (public marketplace with curated 3rd-party contributions). This ensures we have stable extension models, versioning, security review, and billing infrastructure before opening to third parties.

Context

We've discussed a marketplace for templates, agents, modules, and connectors. The question is: when should we launch it?

Options considered:

  1. Launch marketplace immediately (Day 1)
  2. Launch after Factory is proven (Phase 2)
  3. Launch after Factory + Platforms are proven (Phase 3+)
  4. Never launch marketplace

Decision

Marketplace is Phase 3+, after Factory and Platforms are proven.

Phasing:

  1. Phase 1: Internal-only catalog (use internally, treat as "packaged modules")
  2. Phase 2: Private marketplace for big enterprise customers (they can publish internal modules for their teams)
  3. Phase 3: Public marketplace with curated 3rd-party contributions and revenue share model

Rationale

  • Prerequisites Required: Marketplace needs stable extension model, versioning, security review, billing/metering — these don't exist yet
  • Prove Value First: Need to prove Factory and Platforms work before opening to 3rd parties
  • Build Trust: Customers need to trust ConnectSoft before trusting 3rd-party content
  • Learn Internally: Use internal catalog to learn what works before opening up
  • Revenue Focus: Factory and Platforms are higher priority revenue streams initially

Consequences

Positive Consequences

  • Focus on core products first (Factory, Platforms)
  • Time to build proper marketplace infrastructure
  • Learn from internal usage before opening to public
  • Build trust and credibility before ecosystem play
  • Lower risk (don't overextend too early)

Negative Consequences / Risks

  • Slower ecosystem growth (can't leverage 3rd-party content early)
  • Competitors might launch marketplace first
  • Missed opportunity for early marketplace revenue
  • Need to build more content internally (can't rely on 3rd parties)

Mitigation

  • Keep marketplace vision and design in mind when building Factory/Platforms
  • Build extension points that will support marketplace later
  • Start collecting potential marketplace partners early (even if not launching)
  • Can accelerate timeline if market demand is strong

Marketplace Prerequisites

Before launching marketplace, we need:

  1. Stable Extension Model: Clear spec for how templates, agents, modules plug into Factory
  2. Versioning & Compatibility: "This template works with Factory v2.1+"
  3. Security & Review Pipeline: Review code/agents before listing (security, IP, quality)
  4. Billing & Metering: Revenue share and usage-based billing infrastructure
  5. Documentation: Clear guidelines for creators
  6. Legal Framework: Marketplace terms, revenue share agreements, IP protection

Timeline Estimate

  • Phase 1 (Internal): Available now (treat new starters/agents as internal modules)
  • Phase 2 (Private Enterprise): 6-12 months after Factory launch
  • Phase 3 (Public): 12-18 months after Factory launch (or when prerequisites met)

Follow-up Work Required

  • Document marketplace vision and requirements
  • Design extension model with marketplace in mind
  • Build internal catalog system (can evolve into marketplace)
  • Identify potential marketplace partners early
  • Create marketplace roadmap document