Skip to content

Marketplace Roadmap

This document describes how Templates / Agents / Modules marketplaces come online in phases and how they connect to connectsoft.io (public marketplace), partner program, Factory, and platforms. It is written for product managers, architects, and stakeholders planning marketplace evolution.

The Marketplace roadmap focuses on building infrastructure, learning from internal usage, and gradually opening to partners and public contributions. Marketplace assets enable faster delivery and ecosystem growth.

Note

Marketplace Evolution: The marketplace can start as internal and later become external/partner-facing. Phased approach ensures quality and governance before opening to broader contributions.

Marketplace Vision

The marketplace makes reusable assets (templates, agents, modules) discoverable and composable, enabling a future where partners contribute high-quality building blocks.

Vision:

  • Discoverable Assets - Templates, agents, and modules are easy to find and evaluate
  • Composable Building Blocks - Assets can be combined to build solutions faster
  • Partner Contributions - Partners contribute high-quality assets to the marketplace
  • Quality Assurance - All marketplace assets meet security, architecture, and quality standards

See: Marketplace Strategy for marketplace strategy.

See: BDR-0005: Marketplace Phasing for phasing decision.

Marketplace Types

ConnectSoft's marketplace strategy includes three distinct marketplace types, each serving different audiences and use cases:

Template Marketplace

Audience: Developers, architects, Factory users

Purpose: Discoverable and composable code generation blueprints

Assets:

  • Microservice template variants
  • Platform templates (Identity, Audit, Config, etc.)
  • Integration templates
  • Domain-specific templates
  • Overlay recipes

Dependencies:

  • Mature Factory engine with template composition capabilities
  • Template versioning and compatibility system
  • Template quality standards and review processes

See: Templates Marketplace for templates marketplace details.

Agent Marketplace

Audience: Factory users, developers, architects

Purpose: Discoverable and composable AI agents and tools

Assets:

  • Configured AI roles (Architect agent, QA agent, DevOps agent)
  • Domain-specific agents
  • Agent tools and capabilities
  • Agent collaboration patterns

Dependencies:

  • Mature Factory engine with agent system
  • Agent packaging and distribution system
  • Agent quality standards and review processes

See: Agents Marketplace for agents marketplace details.

SaaS & Solution Marketplace

Audience: End customers, product teams, business users

Purpose: Product listings on connectsoft.io for horizontal SaaS, vertical solutions, and solution bundles

Assets:

  • Horizontal SaaS products (Marketing Hub, Short Links, Workflows, CMS, CRM)
  • Vertical solutions (Insurance Suite, AdTech Suite, HR Suite)
  • Solution bundles and industry packages
  • Integration packages

Dependencies:

  • Multiple SaaS and vertical solutions existing and operational
  • Integration Platform for external integrations
  • Support & Self-Service Platform for customer support
  • Mature Core Platform for all SaaS products

See: Modules Marketplace for modules marketplace details.

Marketplace Dependencies and Cycle Positioning

Important

Cycle 5 Positioning: The Marketplace roadmap is explicitly tied to SaaS Cycle 5 in the global ConnectSoft roadmap. Most marketplace features are planned for Cycle 5, after Cycles 1-4 have established mature products and patterns.

The marketplace strategy depends on several foundational components:

Mature Factory Engine:

  • Template composition and overlay system
  • Agent system and orchestration
  • Generation pipelines and quality gates
  • Knowledge system for pattern reuse

Multiple SaaS and Vertical Solutions:

  • Cycle 2: Horizontal SaaS products (Marketing Hub, Short Links, Workflows, CMS, CRM) provide proof points
  • Cycle 3: connectsoft.me Personal Agents Platform provides consumer-facing experimentation and learning
  • Cycle 4: AI Bot Framework, Digital Forms SaaS, and Insurance Suite (first vertical) demonstrate vertical strategy and integration patterns
  • Solution bundles show integration patterns across cycles

Integration Platform and Support/Self-Service:

  • Integration Platform enables external integrations for marketplace items
  • Support & Self-Service Platform provides customer support for marketplace products
  • Both platforms enable marketplace ecosystem growth

Dependency Summary:

Marketplace depends on:

  • Mature AI Factory (Cycle 1)
  • Multiple products live: horizontal SaaS (Cycle 2), connectsoft.me (Cycle 3), AI Bot Framework & Forms & Insurance (Cycle 4)
  • Because of this, most marketplace features are planned for Cycle 5

Quality Standards and Governance:

  • Security and architecture standards
  • Review and curation processes
  • Versioning and deprecation policies
  • Partner contribution guidelines

Phased Marketplace Rollout

flowchart LR
    Phase0[Phase 0: Internal Catalog<br/>Current] --> Phase1[Phase 1: Internal UI<br/>Q3 2026]
    Phase1 --> Phase2[Phase 2: Partner-Facing<br/>Q4 2026/Q1 2027]
    Phase2 --> Phase3[Phase 3: External<br/>2027+]

    Phase0 --> Internal[ConnectSoft Only]
    Phase1 --> Team[Team + Pilot Partners]
    Phase2 --> Partners[Certified Partners]
    Phase3 --> Public[Public Marketplace]

    style Phase0 fill:#e3f2fd
    style Phase1 fill:#f3e5f5
    style Phase2 fill:#e8f5e9
    style Phase3 fill:#fff3e0
Hold "Alt" / "Option" to enable pan & zoom

Phase 0: Internal Catalog Only (Current)

Status: Active

What's Included:

  • Internal catalog of starters/agents/modules
  • Versioning and compatibility tracking
  • Basic review processes
  • Internal usage only

Who Can Publish:

  • ConnectSoft team only

Who Can Consume:

  • ConnectSoft team only

Purpose:

  • Learn what works before opening up
  • Build curation processes
  • Establish quality standards

Phase 1: Internal Marketplace UI (Next)

Target: Q3 2026

What's Included:

  • Internal marketplace UI (Dmitry-only, then team)
  • Template/agent/module discovery
  • Version management
  • Basic search and filtering

Who Can Publish:

  • ConnectSoft team
  • Selected partners (pilot)

Who Can Consume:

  • ConnectSoft team
  • Selected partners (pilot)

Purpose:

  • Improve discoverability
  • Test marketplace infrastructure
  • Refine quality standards

Phase 2: Partner-Facing Marketplace (Later)

Target: Q4 2026 / Q1 2027

What's Included:

  • Partner-facing marketplace (through connectsoft.io with curated items)
  • Partner contributions with review
  • Revenue share model (if applicable)
  • Partner discovery and evaluation

Who Can Publish:

  • ConnectSoft team
  • Certified partners (with review)

Who Can Consume:

  • ConnectSoft team
  • Partners
  • Enterprise customers (private marketplace)

Purpose:

  • Enable partner contributions
  • Expand marketplace assets
  • Test revenue share model

Phase 3: Managed External Contributions (Future)

Target: 2027+

What's Included:

  • Public marketplace (connectsoft.io)
  • Managed external contributions with review
  • Revenue share and billing
  • Community contributions

Who Can Publish:

  • ConnectSoft team
  • Partners
  • External contributors (with review)

Who Can Consume:

  • All users
  • Public discovery

Purpose:

  • Ecosystem growth
  • Community contributions
  • Marketplace as platform

See: BDR-0005: Marketplace Phasing for phasing decision.

Marketplace Ecosystem

graph TB
    subgraph Marketplace["Marketplace Ecosystem"]
        Templates[Templates Marketplace]
        Agents[Agents Marketplace]
        Modules[Modules Marketplace]
    end

    subgraph ConnectSoft["ConnectSoft"]
        Factory[AI Factory]
        Platforms[Platforms]
        Partners[Partner Program]
    end

    subgraph Public["Public Surface"]
        IO[connectsoft.io]
    end

    Templates --> Factory
    Agents --> Factory
    Modules --> Platforms
    Factory --> Platforms
    Partners --> Templates
    Partners --> Agents
    Partners --> Modules
    Marketplace --> IO

    style Marketplace fill:#e3f2fd
    style ConnectSoft fill:#f3e5f5
    style Public fill:#e8f5e9
Hold "Alt" / "Option" to enable pan & zoom

Relationship to connectsoft.io and Partner Program

connectsoft.io Integration

Public Surface:

  • connectsoft.io is the public surface where marketplace items are presented (eventually)
  • Marketplace items appear in product catalog
  • Discovery and evaluation tools
  • Pricing and licensing information

See: IO Domain Strategy for .io domain strategy.

See: Marketplace Strategy for marketplace strategy.

Partner Program Integration

Partner Contributions:

  • Partner docs define who can submit marketplace items
  • Revenue sharing model (link to partner commercial model doc)
  • Quality standards and review process
  • Attribution and licensing

See: Partner Program Overview for partner program details.

See: Commercial Models and Revenue Share for revenue share model.

See: Contributing Templates for template contribution rules.

See: Contributing Libraries for library contribution rules.

Tip

Partner Enablement: Use marketplace items to speed up partner-led implementations. Partners can discover and use templates, agents, and modules to accelerate delivery while maintaining quality standards.

Governance and Quality Control

High-Level Rules

Quality Criteria:

  • All marketplace assets must meet minimal quality criteria
  • Templates/agents must follow security and coding standards
  • Versioning and deprecation must be clearly documented
  • All assets must have documentation and examples

Review Process:

  • Security review for all assets
  • Architecture review for templates
  • Code quality review
  • Documentation review

Versioning:

  • Semantic versioning for all assets
  • Backward compatibility requirements
  • Deprecation policies
  • Migration guides

Important

Curated Marketplace: Marketplace is curated, not a free-for-all. All assets must meet quality, security, and architecture standards. ConnectSoft maintains curation authority to ensure marketplace quality and consistency.

See: Lifecycle - Templates for template lifecycle.

See: Lifecycle - Libraries for library lifecycle.

See: Delivery Standards and Quality Control for quality standards.

See: Security & Compliance for security requirements.

Risks and Open Questions

Key Risks

Fragmentation:

  • Too many similar templates without curation leads to confusion
  • Need clear guidelines for when to create new vs. extend existing
  • Template deprecation and migration challenges

Quality Control:

  • Maintaining quality at scale is challenging
  • Need robust review processes
  • Balance between open contributions and quality

IP/Licensing:

  • IP/licensing concerns for partner content
  • Revenue share model complexity
  • Attribution and licensing clarity

Market Demand:

  • Marketplace may not have sufficient demand initially
  • Need critical mass of assets to be useful
  • Partner adoption may be slow

Warning

Marketplace-Specific Risks: 1. Fragmentation - Too many similar templates without curation leads to confusion 1. Quality Control - Maintaining quality at scale is challenging 1. IP/Licensing - Partner content IP and licensing concerns 1. Market Demand - Marketplace may not have sufficient demand initially

Open Questions

  • How to balance open contributions vs. quality?
  • What's the right revenue share model for marketplace items?
  • How to handle template deprecation and migration?
  • What's the right balance between ConnectSoft templates and partner contributions?

See: Marketplace Strategy for marketplace strategy.

See: Commercial Models and Revenue Share for revenue share model.