Skip to content

ADR-0005: Platform Factory and SaaS Prioritization

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

Context and Problem Statement

ConnectSoft is building a comprehensive ecosystem with Core Platform, AI Factory, and multiple SaaS products across four cycles. We need to establish the ordering and prioritization of these components to ensure a logical progression and minimize risk.

The question: What is the correct ordering for building Core Platform → AI Factory → Horizontal SaaS → AI/Forms/Verticals → Marketplaces?

Decision Drivers

  • Need for logical progression where each component builds on previous
  • Requirement to minimize risk by proving concepts early
  • Need to demonstrate value at each stage
  • Requirement for reusable components to enable faster development
  • Need to build ecosystem systematically

Considered Options

Option 1: Build Everything in Parallel

Approach: Build Core Platform, Factory, and SaaS products simultaneously.

Pros:

  • Faster overall time to market
  • Can work on multiple fronts

Cons:

  • High risk without proven foundation
  • Inconsistent patterns
  • Difficult to coordinate
  • Rejected - Too risky, no foundation

Option 2: Sequential Build with Cycles (Selected)

Approach: Build sequentially: Core Platform → AI Factory (Cycle 1) → Horizontal SaaS (Cycle 2) → AI/Forms/Verticals (Cycle 3) → Marketplaces (Cycle 4).

Pros:

  • Logical progression where each builds on previous
  • Lower risk by proving concepts at each stage
  • Reusable components enable faster development
  • Clear milestones and value demonstration

Cons:

  • Longer overall timeline
  • Requires discipline to maintain ordering

Decision

Build components sequentially in the following order:

  1. Core Platform Wave - Identity, Config, Audit, Communications, Documents, Billing (stable and production-ready)
  2. Cycle 1: AI Factory SaaS - Factory as first SaaS product, runs on Core Platform
  3. Cycle 2: Horizontal SaaS - Digital Marketing Hub, Short Links, Workflows, CMS, CRM (built using Factory)
  4. Cycle 3: AI Interaction & First Vertical - AI Bot Framework, AI Marketing Copilot, Digital Forms, Insurance Suite
  5. Cycle 4: Marketplaces & Ecosystem - Template/Agent/SaaS marketplaces, additional verticals, Integration Platform, Support/Self-Service

Each cycle:

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

Rationale

  • Foundation First: Core Platform must be stable before any SaaS products can be built reliably.
  • Factory Enables SaaS: AI Factory must be operational before it can generate SaaS products efficiently.
  • Horizontal Before Vertical: Horizontal SaaS products prove the model before building vertical solutions.
  • AI After Foundation: AI/Bot features require stable Core Platform and proven SaaS model.
  • Marketplaces Last: Marketplaces require mature Factory, multiple SaaS products, and ecosystem.

Consequences

Positive Consequences

  • Logical progression with clear milestones
  • Lower risk by proving concepts at each stage
  • Reusable components enable faster development
  • Clear value demonstration at each cycle
  • Systematic ecosystem building

Negative Consequences

  • Longer overall timeline
  • Requires discipline to maintain ordering
  • May delay some features that could be built earlier