Skip to content

ADR-0006: Product Portfolio and Ecosystem

  • Status: accepted
  • Deciders: ConnectSoft Architecture Team
  • Date: 2026-01-01

Context and Problem Statement

ConnectSoft is building a comprehensive product portfolio spanning Core Platform, AI Factory, horizontal SaaS, vertical solutions, and marketplaces. We need to establish a clear structure for organizing this portfolio to ensure clarity, reuse, and stepwise maturity.

The question: How should we structure the product portfolio to enable clarity, reuse, and stepwise maturity across four cycles?

Decision Drivers

  • Need for clear product organization and structure
  • Requirement for reusable components across products
  • Need for stepwise maturity and evolution
  • Requirement for clear value proposition at each stage
  • Need to enable ecosystem growth

Considered Options

Option 1: Flat Product List

Approach: List all products in a flat structure without cycles or organization.

Pros:

  • Simple structure
  • Easy to list products

Cons:

  • No clear progression
  • Difficult to understand dependencies
  • No clear value proposition
  • Rejected - Lacks structure and clarity

Option 2: Four-Cycle Structure (Selected)

Approach: Organize products into four cycles: Core Platform → Cycle 1 (AI Factory SaaS) → Cycle 2 (Horizontal SaaS) → Cycle 3 (AI/Forms/Verticals) → Cycle 4 (Marketplaces).

Pros:

  • Clear progression and dependencies
  • Logical organization
  • Enables reuse and stepwise maturity
  • Clear value proposition at each cycle
  • Supports ecosystem growth

Cons:

  • More complex structure
  • Requires discipline to maintain

Decision

Organize the product portfolio into a four-cycle structure:

Core Platform (Always First):

  • Identity, Config, Audit, Communications, Documents, Billing, AI Gateway, Integration Platform, Support/Self-Service

Cycle 1: AI Factory SaaS

  • AI Factory SaaS (B2D, API-first, first SaaS product)

Cycle 2: Horizontal Product SaaS

  • Digital Marketing Hub, Short Links, Workflow Orchestrator, Headless CMS, CRM/Contacts Hub

Cycle 3: AI Interaction & First Vertical

  • AI Bot Framework, AI Marketing Copilot, Digital Forms SaaS, Insurance Suite

Cycle 4: Marketplaces & Ecosystem

  • Template/Agent/SaaS marketplaces, AdTech Suite, HR Suite, Integration Platform, Support/Self-Service, Mobile apps

Each cycle:

  • Adds new SaaS products
  • Evolves AI Factory (templates, agents, recipes)
  • Improves Core Platform
  • Makes previous SaaS more powerful

Rationale

  • Clarity: Four-cycle structure provides clear organization and progression.
  • Reuse: Each cycle builds on previous cycles, enabling component reuse.
  • Stepwise Maturity: Each cycle demonstrates maturity before moving to next.
  • Value Proposition: Clear value at each cycle for different audiences.
  • Ecosystem Growth: Structure enables systematic ecosystem expansion.

Consequences

Positive Consequences

  • Clear product organization
  • Logical progression and dependencies
  • Enables component reuse
  • Stepwise maturity and evolution
  • Supports ecosystem growth
  • Clear value proposition at each cycle

Negative Consequences

  • More complex structure
  • Requires discipline to maintain cycles
  • May delay some products that could be built earlier