Build
Salesforce + Zendesk + optional warehouse/dbt views as sales, CS, and finance products.
Revenue learning loops: pipeline, support burden, and renewal context on one fabric — QBR and forecast narratives from governed facts, not CRM-only copilots. Growth suite (Mautic, n8n) mesh installs sit on the same fabric.
Enterprise agent ROI clusters where revenue workflows already cross CRM, support, and finance systems; 2026 GTM agents fail when they only see the CRM slice.
Build
Salesforce + Zendesk + optional warehouse/dbt views as sales, CS, and finance products.
Steer
Account-health MCP and pipeline narratives on dept.sales + dept.customer_success.
Compound
Measure retention and expansion leading indicators; private evals on QBR fact recall.
| Workflow | Buyer pain | Mesh answer |
|---|---|---|
| Pipeline hygiene | Opportunities lack eng/product signal; forecasts are storytelling without evidence. | gtm-pipeline + CRM events linked to operational signals when agents need depth. |
| Renewal risk | CS and support silos; agents cannot cite open severity and usage together. | account-health use case merges CRM + tickets under governed recall. |
| RevOps analytics bridge | Warehouse metrics lag; agents invent numbers from stale dashboards. | dbt/warehouse live views with the same dept.* tenancy. |
Revenue agents underperform when they only see CRM. RevOps needs support burden, product signal, and finance views on one fabric with measurable leading indicators.
Connectors on this map should match /product and /data-products. List the tools. Do not print a readiness label.
Packaged workflows and starting points for this vertical map.