Marketing OS
MERCURY · governed demand system
Marketing OS
Demand intelligence that moves from market signal to governed campaign.
Marketing OS brings demand signals, strategy, campaigns, content, channels, approvals, and optimisation into one governed growth surface.
Marketing OS
MERCURY · governed demand system
The problem
Marketing teams lose speed when strategy, content, channels, approvals, and performance data live in separate tools with no shared governance layer.
You need governed demand operations instead of disconnected campaign tools.
Strategy, content, channels, and approvals currently live in separate systems.
You want to move faster without skipping review or connector posture checks.
Why businesses choose Marketing OS
One governed demand surface
Keep strategy, campaigns, content, channels, and approvals in a single operating view.
Faster, safer launches
See what is ready, what is blocked, and what needs review before any publish step moves.
Evidence attached to every move
Explain every recommendation with source, freshness, and connector posture.
Marketing OS plugs into Sales, Finance, RTW, and Growth Command Center so demand work is never inspected in isolation.
Connects to
- Market signals
- Campaign calendars
- Content queues
- Meta and Google channels
- Approval gates
How it works
- 1Demand
- 2Strategy
- 3Campaign
- 4Content
- 5Publish
- 6Optimise
Strategy readiness
Keep market context, ICP, objectives, campaigns, and execution readiness in one governed artefact.
Campaign pipeline
Track demand moves from concept through approval, channel readiness, launch review, and learning.
Content production
Surface content state, approval need, connector dependency, and publish readiness before execution.
Evidence posture
Logged-out preview only; tenant evidence loads after sign-in.
Outcome
Operators can see what demand motion is ready, what is blocked, and where to safely review next.
Signal source
Market + channel postureRecommendations explain what changed and what evidence supports the move.
Policy state
Approval visiblePublishing remains review-only until governed downstream paths allow it.
Learning loop
Optimisation attachedPerformance context feeds the next campaign recommendation.
- Publish readiness
- Approval policy
- Connector posture
- Evidence-backed recommendations
Evidence rail
Open the console to inspect tenant-scoped evidence for Marketing OS.
Open evidence in console →Related agents
MERCURY
Product story →MERCURY
Growth intelligence adjacent to read models and outbound paths; message send remains NUNTIUS; orchestration remains ATLAS.
Marketing OS (MERCURY module surface)
Product story →
Marketing OS (MERCURY module surface)
Primary operator workspace for governed marketing operations; MERCURY domain agent manifests in integration topology.
Sales OS (AUCTOR module surface)
Product story →
Sales OS (AUCTOR module surface)
Primary operator workspace for governed sales and pipeline intelligence; AUCTOR domain agent manifests in integration topology.
Growth Command Center
Product story →
Growth Command Center
Single pane for demand-to-revenue posture when one or both commercial modules are active.
Tenant scope (multi-tenant boundary)
Product story →
Tenant scope (multi-tenant boundary)
Makes the tenant visible on 2D/3D maps next to commercial modules (MERCURY, AUCTOR) and Growth Command.
Operator console (Next.js)
Agent profile →
Operator console (Next.js)
Primary control-plane experience for pilots and demos; uses cookie-based JWT to `/api/v1/*` (see `apps/web/middleware.ts`).