Skip to content

Customer relationship management

Generated from the architecture model

This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.
Vertical CRM
Prototype reference CRM prototype (ConnectSoft.DesignPrototypes)
Managed edition Managed (D33, D34)
Data residency tenant-region (D31)
Catalog Examples catalog · Vision-to-Production path for this vertical

Business problem

Sales and service teams keep customers in three tools with no shared timeline and no way to govern what automation may send.

Product intent

A multi-tenant CRM with accounts, contacts, pipeline, service cases and governed outbound communication through connectors.

What the Factory makes different here: outbound messages are external-class actions with receipts and a per-tenant policy.

Vision-to-Production path for this vertical

Step Factory platform Agents Blueprints
Vision and product plan Agent Mesh, Control plane Product Manager Agent, Enterprise Architect Agent vision
Architecture and domain Template & Library (BC-02) Enterprise Architect Agent service, module, integration
Experience Template & Library, Factory Studio UX track UX Designer Agent, Frontend Developer Agent frontend, ux
Recipe and generation Template & Library (BC-15), Agent Mesh, Tools & MCP Product Manager Agent, Enterprise Architect Agent, Integration Architect Agent, Backend Developer Agent, Frontend Developer Agent, QA Agent module plan from the context map
Quality Observability (BC-22), DevOps / GitOps QA Agent test, pipeline
Delivery and provisioning DevOps / GitOps (BC-23, BC-24), Runtime Cloud (BC-25) DevOps Agent, Infrastructure Architect Agent —
Operations Product Fleet Operations (BC-35..37) — handover, objectives, rollouts, incidents, off-boarding

Delivery workflows exercised: customer-success-workflows, growth-and-marketing-workflows.

Generated product shape

C4Context
    title Customer relationship management system context
    Person(user, "Users", "CRM users and operators")
    System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
    System_Boundary(product, "Customer relationship management") {
        System(ctx_Accounts, "Accounts", "companies, contacts, consent")
        System(ctx_Pipeline, "Pipeline", "opportunities, stages, forecasts")
        System(ctx_Service, "Service", "cases, SLAs, escalations")
        System(ctx_Engagement, "Engagement", "sequences, messages via connectors")
    }
    Rel(user, ctx_Accounts, "uses through the product gateway GW-07")
    Rel(factory, ctx_Accounts, "descriptor, health, rollouts, incidents, off-boarding")
Hold "Alt" / "Option" to enable pan & zoom

Bounded contexts

Context Responsibility Published events
Accounts companies, contacts, consent ContactConsentChanged
Pipeline opportunities, stages, forecasts OpportunityStageChanged
Service cases, SLAs, escalations CaseEscalated
Engagement sequences, messages via connectors MessageSent

Modules and templates

Module Template Notes
Microservice ×4 connectsoft-microservice
API gateway connectsoft-apigateway
Shell + MFEs connectsoft-blazor-saas-shell
Every product also gets the SaaS foundations (tenants, editions, entitlements, billing, metering) and the product host shape (descriptor, health, operations handover) unless it is a library-only product.

Prototype reference

CRM prototype in ConnectSoft.DesignPrototypes shows the intended screens; the UX track (U1–U4) maps prototype destinations to the UX model's screens with keep, merge, rename, retire or new decisions.

Operations as a managed product

Managed: standard objectives; connectors for email and chat certified before use.