SaaS Ecosystem Catalog Overview¶
This is the master entry point for the ConnectSoft SaaS Ecosystem Catalog - a structured, implementation-ready map of ~1,500 candidate products, services, and components across 30 categories. It exists to drive product strategy, architecture decisions, future microservice/agent generation, backlog generation, and Azure DevOps planning. It is documentation only: no business services are built here.
The catalog is a long-term superset. The authoritative timelines remain the 2026 Roadmap and Platforms Roadmap; this catalog organizes everything those roadmaps will eventually draw from.
Important
The catalog does not imply 1,500 microservices. Most items are modules inside a small number of bounded-context services, reusable libraries, connectors, UI modules, AI agents, workflow templates, or pre-composed solution packs. See the service classification model and ADR-0011.
How This Catalog Is Organized¶
The catalog has two complementary layers plus a machine-readable core:
- Browse layer - 30 lightweight category pages listing every candidate with a one-line description and Status / Cycle / Wave / Tier tag.
- Planning layer - strategy docs, 30 deep-dive analyses, blueprints, planning artifacts, and diagrams.
- Machine-readable core -
master-service-catalog.yaml/.csv(the source of truth for tooling).
Strategy Documents¶
| # | Document | Purpose |
|---|---|---|
| 00 | Executive Summary | What this is and why it matters |
| 01 | Ecosystem Principles | Architectural principles honored across the catalog |
| 02 | Category Map | The 30 categories and their grouping |
| 03 | Platform vs Horizontal vs Vertical | Separation of concerns |
| 04 | Prioritization Model | Scoring and tiers |
| 05 | Implementation Waves | Phases 0-6 |
| 06 | Bounded-Context Map | Foundational and vertical contexts |
| 07 | Service Classification Model | Delivery shapes; avoiding fragmentation |
| 08 | Reference Architecture | How a candidate is built |
| 09 | Roadmap Alignment | Crosswalk to existing cycles/waves |
| 10 | Risks & Governance | Risks, controls, and ownership |
Category Map (30 Categories)¶
flowchart TB
subgraph Core[Core Platform - Tier 0-1]
C1[1 SaaS Core and Tenant]
C2[2 Identity and Security]
C3[3 Config and Flags]
C4[4 Billing and Revenue]
C5[5 Notifications]
C6[6 Audit and Compliance]
C7[7 Data and AI]
C8[8 API and Integration]
C9[9 Infra and SRE]
C10[10 Developer Factory]
end
subgraph Horizontal[Horizontal SaaS - Tier 2-3]
C11[11 CRM and Support]
C12[12 Sales and RevOps]
C13[13 Marketing]
C14[14 E-Commerce]
C23[23 Finance Ops]
end
subgraph Vertical[Verticals - Tier 3-5]
C15[15 Banking]
C16[16 Insurance]
C17[17 Healthcare]
C18[18 Education and HR]
C19[19 Logistics]
C20[20 Manufacturing]
C21[21 Real Estate]
C22[22 Legal and Gov]
C24[24 Media]
C25[25 Hospitality]
C26[26 Energy and ESG]
end
subgraph Ecosystem[AI, Packs, Marketplace, Governance]
C27[27 AI Agents]
C28[28 Marketplace]
C29[29 Solution Packs]
C30[30 Enterprise Governance]
end
Core --> Horizontal --> Vertical
Core --> Ecosystem
Status & Tier Legend¶
- Status -
Live(running today),Documented(has an existing platform/product page),Planned(catalog candidate). - Tier -
Tier 0mandatory foundation throughTier 5future/research. See the prioritization model. - Wave - Phase 0 (documentation) through Phase 6 (advanced AI factory). See implementation waves.
Crosswalk to Existing Structures¶
| Existing structure | Relationship to this catalog |
|---|---|
| 12-category platform framework | This 30-category catalog is a superset; platform categories 1-12 map into categories 1-14 here |
| Core Platform Wave / Tier-1 list | Equivalent to catalog Tier 0-1 in Phase 1 |
| 5 SaaS cycles | Mapped to Phases 2-5 in roadmap alignment |
| SaaS framework DDD blueprint | Source of truth for foundational bounded contexts |