Headless Strategy  /  Reference Architecture
Systems of record stay headless. Agents read them & act where you work.
READ + WRITE  ·  MODEL CONTEXT PROTOCOL
5 CONNECTORS  ·  4 OUTPUTS
Systems of Record
Strategy Engine
Output Surfaces
MCP Boundary
Salesforce
Salesforce
CRM
HubSpot
HubSpot
CRM · Marketing
Gong
Gong
Revenue intel
Clay
Clay
Data enrichment
ZoomInfo
ZoomInfo
Firmographics
Runs in
SlackSlack ClaudeCowork
Strategy
Engine
No interface of its own. It reasons over your systems of record and acts through the surfaces you already use.
Claude Claude Cowork 3 MCP connected
Claude
02 Insight generated
I found 3 enterprise deals that stalled 14+ days after demo. Two lost exec-sponsor engagement — flagging as pipeline risk.
01 update_record SalesforceSalesforce
stageDiscovery → Negotiation
close_dateQ3 → Q4 FY26
next_stepExec alignment call
Gong
03Acme Corp — Discovery
GONG CALL · 38:12
Review
Salesforce$120K Opp ZoomInfo1,200 employees
Slack #gtm-risk 04 · SLACK MESSAGE
SE
Strategy Engine APP 9:41 AM
This is next quarter's risk
Acme Corp renewal — no exec sponsor engaged in 21 days. $120K ARR at risk. Pulled from Gong + Salesforce.
4 3 Reply in thread
Headless = the systems of record hold the data; the agent supplies the interface & the action.