Organization GTM workspace
Growth, revenue, and customer success workspaces
Operate acquisition-to-support development work without turning demo data, stale CRM, or missing helpdesk sources into production success.
Canonical acquisition-to-support map
7 governed stages · 0 production-authoritative · 7 require connection, freshness, or approval work.
AEP records development context, approvals, evidence, and requests. It does not mutate global Admin, agent definitions, or customer source records directly.
Canonical GTM taxonomy
Funnel, revenue, and customer-success stages
Each stage shows whether facts are production-authoritative, sample-only, stale, or not connected.
Acquisition
demo sample only, not production success
- Canonical facts
- channel attribution, campaign spend, CAC, ROI/ROAS
- Provenance
- commerce:fixture://solara/commerce-facts @ simulated; dataphin:fixture://solara/data-products @ never
- Production fact
- no
Qualification
demo sample only, not production success
- Canonical facts
- lead source, qualified opportunity, account fit
- Provenance
- dataphin:fixture://solara/data-products @ never
- Production fact
- no
Pipeline
not connected to an authoritative system of record
- Canonical facts
- pipeline stage, forecast, booking probability
- Provenance
- not connected
- Production fact
- no
Bookings
not connected to an authoritative system of record
- Canonical facts
- booking, contract state, procurement state, margin
- Provenance
- not connected
- Production fact
- no
Renewals
not connected to an authoritative system of record
- Canonical facts
- renewal date, contract health, expansion risk
- Provenance
- not connected
- Production fact
- no
Expansion
not connected to an authoritative system of record
- Canonical facts
- expansion motion, account whitespace, commercial owner
- Provenance
- not connected
- Production fact
- no
Support
not connected to an authoritative system of record
- Canonical facts
- priority/SLA, sentiment, customer impact, incident linkage
- Provenance
- not connected
- Production fact
- no
Development initiatives
Governed changes to GTM systems
Recommended work must enter request, policy, approval, provisioning, and evidence paths before execution.
Recommended changes
AEP lifecycle entry points
Links stay inside governed AEP routes and never jump to Admin, chat, or agent-definition surfaces.
Request demand-forecast access before using lift claims
The demo has no live Dataphin source, so the recommendation must enter policy and approval instead of mutating provider state.
Evidence: evt-policy-review · freshness simulatedBoundaries