Skip to content

Sales and revenue operations

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 Sales & RevOps
Prototype reference Sales & RevOps 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

Quotes, contracts and renewals are disconnected from the CRM and billing; forecasts are manual.

Product intent

Quote-to-cash: quotes, approvals, contracts, renewals and forecasts integrated with CRM and billing.

What the Factory makes different here: discount approvals as approval-bound commands with policy thresholds.

Vision-to-Production path for this vertical

Step Factory platform Agents Blueprints
Vision and product plan Agent Mesh, Control plane Product Manager Agent, Integration 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 —
Recipe and generation Template & Library (BC-15), Agent Mesh, Tools & MCP Product Manager Agent, Integration Architect Agent, Backend 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, customer-success-workflows.

Generated product shape

C4Context
    title Sales and revenue operations system context
    Person(user, "Users", "Sales & RevOps users and operators")
    System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
    System_Boundary(product, "Sales and revenue operations") {
        System(ctx_Quotes, "Quotes", "quotes, pricing, approvals")
        System(ctx_Contracts, "Contracts", "contracts, signatures, renewals")
        System(ctx_Forecasting, "Forecasting", "pipeline snapshots, forecasts")
    }
    Rel(user, ctx_Quotes, "uses through the product gateway GW-07")
    Rel(factory, ctx_Quotes, "descriptor, health, rollouts, incidents, off-boarding")
Hold "Alt" / "Option" to enable pan & zoom

Bounded contexts

Context Responsibility Published events
Quotes quotes, pricing, approvals QuoteApproved
Contracts contracts, signatures, renewals ContractSigned
Forecasting pipeline snapshots, forecasts ForecastPublished

Modules and templates

Module Template Notes
Microservice ×3 connectsoft-microservice
CRM and billing clients connectsoft-api-library
Shell 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

Sales & RevOps 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.