Marketplace Strategy¶
This document defines ConnectSoft's marketplace strategy and phasing. It is written for product managers, architects, and anyone planning the marketplace roadmap.
ConnectSoft's marketplace strategy focuses on templates, agents, modules, and connectors that plug into the Factory and platforms — not random apps. The marketplace will launch in phases: internal-only → private enterprise → public curated.
Warning
Marketplace is Phase 3+ — after Factory and Platforms are proven. Prerequisites include stable extension models, versioning, security review pipelines, and billing infrastructure. Don't rush this.
Marketplace Categories¶
1. Template & Blueprint Marketplace¶
- Microservice templates (specialized for domains)
- Blueprint packs
- Front-end templates, CI/CD pipelines, IaC bundles
2. Agent & Skill Marketplace¶
- Specialized agents & skills for the factory
- Microsoft Agent Framework tools & MCP servers
- QA agents, governance agents with specific policies
3. Module / Microservice Marketplace¶
- Prebuilt microservices and vertical modules
- Production-ready, built on ConnectSoft templates
- Integratable via APIs/events
4. Data / Integration & Connector Marketplace¶
- Connectors/bridges (Greenhouse, Vetspire, etc.)
- RAG data packs
- Integration packs for specific verticals
Phasing Strategy¶
Phase 1: Internal-Only (Current)¶
- Use internally, treat as "packaged modules"
- Learn what works before opening up
Phase 2: Private Marketplace (6-12 months)¶
- For big enterprise customers
- They can publish internal modules for their teams
- Controlled environment
Phase 3: Public Marketplace (12-18 months)¶
- Curated 3rd-party contributions
- Revenue share model (70/30)
- Security & quality review pipeline
Prerequisites¶
Before launching marketplace: - Stable extension model - Versioning & compatibility - Security & review pipeline - Billing & metering infrastructure
Monetization¶
- Revenue Share: 70/30 creator/ConnectSoft
- One-Time Purchase: Template/agent packs
- Subscription: Marketplace access tiers
- Usage-Based: Per execution/run for agents
Supply Side (Templates, Agents, Modules)¶
Who Creates Items¶
- ConnectSoft - First-party templates, agents, and modules
- External Experts - Domain architects, agencies, consultants
- Platform Teams - Internal platform teams contribute governance agents
- Vertical SaaS Companies - Industry-specific companies contribute modules
- Community - Curated community contributions (Phase 3+)
What Gets Created¶
- Templates - Microservice templates, blueprint packs, infrastructure templates
- Agents - Specialized agents, skills, tools, MCP servers
- Modules - Prebuilt microservices, vertical modules, integration modules
Quality Standards¶
- Code Review - All items reviewed before listing
- Testing - Comprehensive tests and examples required
- Documentation - Complete documentation required
- Security - Security review for all items
- Compatibility - Version compatibility clearly stated
Demand Side (Customers and Use Cases)¶
Who Buys Items¶
- Factory Users - Teams using Factory to generate systems
- Platform Teams - Internal platform teams needing governance agents
- SaaS Companies - Companies wanting to drop in modules
- Consultancies - SIs wanting vertical accelerators
- Enterprises - Large organizations building internal marketplaces
Use Cases¶
- Accelerate Development - Use templates to build faster
- Domain Expertise - Leverage specialized agents for specific domains
- Drop-In Capabilities - Use prebuilt modules instead of building
- Governance - Use governance agents for compliance and standards
Phased Rollout¶
Phase 1: Internal-Only (Current)¶
- Use items internally
- Treat as "packaged modules"
- Learn what works before opening up
- Build curation and review processes
Phase 2: Private Marketplace (6-12 months)¶
- For enterprise customers
- They can publish internal items for their teams
- Controlled environment
- Learn from enterprise usage
Phase 3: Public Marketplace (12-18 months)¶
- Curated third-party contributions
- Revenue share model (70/30 creator/ConnectSoft)
- Security and quality review pipeline
- Public launch with select partners
Governance and Quality¶
Quality Standards¶
- Code Review - All code reviewed before listing
- Testing - Items must include tests and examples
- Documentation - Complete documentation required
- Security - Security review for all items
- Compatibility - Version compatibility clearly stated
Governance Process¶
- Submission - Creator submits item for review
- Review - ConnectSoft team reviews code, tests, documentation
- Approval - Approved items listed in marketplace
- Updates - Version updates go through same review process
- Monitoring - Usage and feedback monitored
Revenue Share¶
- 70/30 Split - 70% to creator, 30% to ConnectSoft
- One-Time Purchases - Revenue share on initial sale
- Subscriptions - Ongoing revenue share for subscriptions
- Enterprise - Custom terms for enterprise deals
Related Documents¶
- BDR-0005: Marketplace Phasing - Phasing decision
- Product Portfolio - Marketplace - Marketplace product pages
- Templates Marketplace - Templates marketplace
- Agents Marketplace - Agents marketplace
- Modules Marketplace - Modules marketplace