Skip to content

Marketing automation

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 Marketing
Prototype reference Marketing 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

Campaigns, segments and content are run from spreadsheets and vendor tools with no consent governance.

Product intent

Segments, campaigns, journeys, content and consent with delivery through the communication hub.

What the Factory makes different here: consent and policy gate every outbound journey step (external class).

Vision-to-Production path for this vertical

Step Factory platform Agents Blueprints
Vision and product plan Agent Mesh, Control plane Product Manager Agent, Backend Developer 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
Recipe and generation Template & Library (BC-15), Agent Mesh, Tools & MCP Product Manager Agent, Backend Developer Agent, Frontend Developer Agent, QA Agent module plan from the context map
Quality Observability (BC-22), DevOps / GitOps QA Agent test
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: growth-and-marketing-workflows.

Generated product shape

C4Context
    title Marketing automation system context
    Person(user, "Users", "Marketing users and operators")
    System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
    System_Boundary(product, "Marketing automation") {
        System(ctx_Audience, "Audience", "segments, consent")
        System(ctx_Campaigns, "Campaigns", "campaigns, journeys, steps")
        System(ctx_Content, "Content", "assets, variants")
    }
    Rel(user, ctx_Audience, "uses through the product gateway GW-07")
    Rel(factory, ctx_Audience, "descriptor, health, rollouts, incidents, off-boarding")
Hold "Alt" / "Option" to enable pan & zoom

Bounded contexts

Context Responsibility Published events
Audience segments, consent SegmentRefreshed
Campaigns campaigns, journeys, steps JourneyStepExecuted
Content assets, variants VariantApproved

Modules and templates

Module Template Notes
Microservice ×3 connectsoft-microservice
Shell connectsoft-blazor-saas-shell
Marketing site connectsoft-marketing-site
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

Marketing 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.