Skip to content

ADR-0004: Core Platform Stack Prioritization

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

Context and Problem Statement

ConnectSoft is building a comprehensive SaaS platform ecosystem with AI Factory capabilities, horizontal SaaS products, vertical solutions, and marketplaces. We need to establish the foundational Core Platform services that all SaaS products and the Factory rely on before building advanced AI/Bot features.

The question: What Core Platform services should be built first, and why should they be prioritized before advanced AI/Bot features?

Decision Drivers

  • Need for foundational services that all SaaS products depend on
  • Requirement for multi-tenant architecture across all platforms
  • Need for stable infrastructure before building advanced features
  • Requirement for consistent patterns across all products
  • Need to prove multi-tenant architecture before scaling

Considered Options

Option 1: Build AI/Bot Features First

Approach: Start with AI Bot Framework and advanced AI features, build Core Platform later.

Pros:

  • Faster time to market for AI features
  • Can demonstrate AI capabilities early

Cons:

  • No stable foundation for SaaS products
  • Each SaaS product would need to build its own infrastructure
  • Inconsistent patterns across products
  • Difficult to scale without Core Platform
  • Rejected - Too risky, no foundation

Option 2: Build Core Platform First (Selected)

Approach: Build Core Platform services (Identity, Config, Audit, Communications, Documents, Billing) first, then build SaaS products and AI features on top.

Pros:

  • Stable foundation for all SaaS products
  • Consistent patterns across all products
  • Multi-tenant architecture proven early
  • Easier to scale with shared infrastructure
  • SaaS products can be built faster with Core Platform

Cons:

  • Longer time to market for AI features
  • Requires upfront investment in Core Platform

Decision

Build Core Platform services first, before advanced AI/Bot features. The Core Platform stack includes:

  1. Identity & Access Platform - Multi-tenant authentication and authorization
  2. Config Platform - Configuration and feature flags
  3. Audit Trail Platform - Tamper-evident audit logging
  4. Communications Platform - Email, SMS, notifications
  5. Documents Platform - Document storage and management
  6. Billing & Subscription Platform - Subscription and usage billing

These Core Platform services must be stable and production-ready before building Cycle 1 (AI Factory SaaS), Cycle 2 (Horizontal SaaS), Cycle 3 (AI/Bot features), and Cycle 4 (Marketplaces).

Rationale

  • Foundation First: Core Platform provides the foundation that all SaaS products depend on. Building AI features without this foundation would require each product to build its own infrastructure.
  • Consistency: Core Platform ensures consistent patterns (multi-tenancy, observability, security) across all products.
  • Scalability: Shared Core Platform services enable scaling without rebuilding infrastructure for each product.
  • Risk Mitigation: Proving multi-tenant architecture early reduces risk for all future products.
  • Speed: Once Core Platform is stable, SaaS products can be built faster using shared services.

Consequences

Positive Consequences

  • Stable foundation for all SaaS products
  • Consistent patterns and architecture
  • Faster development of SaaS products
  • Easier scaling and operations
  • Proven multi-tenant architecture

Negative Consequences

  • Longer time to market for AI features
  • Upfront investment in Core Platform
  • Need to maintain Core Platform services