The operator console for your revenue layer. Agent native.
Ask for last week’s revenue moments. Tighten a cap. Draft new wall copy and approve it. Cowork is one MCP surface — the same one your dashboard uses — operated from whichever agent you already work in.
Operate the revenue layer in plain language.
Moments, trial pipeline, unrealized revenue — headless.
Draft → approve → apply. You hold the pen.
Two words, fully audited.
Applied with rollback — the audit trail rides along.
MCP works
What you operate from your agent.
Everything the dashboard’s Expansion section exposes, headless: the playbook you tune, the copy you approve, and the numbers that tell you whether it’s working — in the workspace you already have open.
Playbook
The posture ladder, per-class trigger toggles, frequency caps, per-subject cooldowns, and quiet segments — every dial the pack respects, adjustable in a sentence.
Approvals
Draft → approve → apply. Wall copy, advisory text, playbook changes — nothing reaches your users unreviewed, and every approval is logged with its approver.
Analytics
Moments by type × lifecycle, the wall funnel, unrealized revenue split acquisition vs. expansion, conversions with their triggers, and value receipts.
The whole revenue layer, one MCP surface.
A dozen read-only operator tools give any MCP-speaking agent your entire revenue picture — the daily brief, the wall funnel, the trial pipeline, and what a posture change would actually do. The same numbers as your dashboard, one tool call away.
- One protocol, any host — Claude, ChatGPT, Cursor, Copilot, Gemini all drive the same surface.
- Read-only by design — analytics tools can’t change your playbook.
- Always split: new-customer revenue and expansion revenue never blur.
- Honest denominators — conversion rates ship with their caveats attached.
Agent native, not agent locked.
Cowork isn’t a plugin for one vendor’s workspace. It’s an MCP server — the open standard for tool calling — so the operator surface travels with the protocol, not with a single agent.
One surface, any agent.
The same tools resolve in Claude, ChatGPT, Cursor, Copilot, or Gemini. Point whichever agent you already use at the MCP server — there’s nothing agent-specific to learn, port, or rebuild.
No console to log into.
You don’t open a new dashboard to run the revenue layer. You ask in the thread you already have open, and it answers — the playbook, the approvals, and the numbers, all in conversation.
Portable by protocol.
Because it’s MCP, a new agent host tomorrow speaks the same language today. The surface is defined once and works everywhere the standard reaches — your revenue layer is never trapped in one vendor.
Draft. Approve. Roll back.
Operating a revenue layer from chat only works if the guardrails are structural. They are.
Proposes
Every workflow produces a draft artifact — never silently applied. You see exactly what will change before anything ships.
You approve
Explicit approval gates. Every action logged. Every approver named. The audit trail is complete, exportable, and immutable.
Rolls back
Two-phase commit on every mutation. Kill switch per workflow. If a change misbehaves, you revert to the prior state in one click.
Cowork ships with the platform — see pricing →
Operate it from where you already work.
The revenue layer, its playbook, and its numbers — one MCP surface, readable and steerable from whichever agent you already work in.