Skip to content

ADR-0013: Vertical Solution Pack Strategy

  • Status: accepted
  • Deciders: ConnectSoft Architecture Team
  • Date: 2026-06-10

Context and Problem Statement

The catalog includes many industry verticals (banking, insurance, healthcare, logistics, etc.) and a dedicated category of solution packs. We must decide how verticals are built so we do not re-implement identity, billing, notifications, CRM, and support per industry.

Decision Drivers

  • Verticals share most non-domain capabilities with the platform and horizontals.
  • Re-implementing shared capabilities per vertical is wasteful and inconsistent.
  • Industry value is concentrated in a thin layer of domain-specific contexts.

Considered Options

Option 1: Build each vertical as a standalone product from scratch

  • Maximum duplication, inconsistent quality. Rejected.

Option 2: Verticals as solution packs composed on the platform (Selected)

Decision

Verticals are delivered primarily as solution packs: pre-composed bundles of existing platform and horizontal building blocks, plus only the genuinely industry-specific bounded contexts (e.g., underwriting, claims, KYC, care plans). Packs are defined with the vertical solution pack template and add no new runtime beyond their industry-specific contexts.

Rationale

  • Concentrates effort on real industry differentiation.
  • Reuses Identity, Billing, Notifications, Audit, Documents, CRM, Support.
  • Aligns with the platform/horizontal/vertical separation.

Consequences

Positive

  • Verticals are fast to assemble and consistent; lower maintenance.

Negative

  • Requires mature platform + horizontals first (see ADR-0012).
  • Some industry edge cases may need targeted extensions to shared capabilities.