Sales OS
AUCTOR · governed revenue generation
Sales OS
Revenue execution grounded in signals, evidence, and approval boundaries.
Sales OS connects buying intent, lead priority, outreach readiness, conversations, opportunity movement, and learning.
Sales OS
AUCTOR · governed revenue generation
The problem
Sales systems often separate intent, lead context, outreach approvals, conversations, and pipeline learning, leaving operators to guess what deserves action.
You want revenue motions grounded in signals and evidence, not guesswork.
Sales, RevOps, and Marketing need a shared view of why accounts are prioritised.
You care about governed outbound, mailbox posture, and approval visibility.
Why businesses choose Sales OS
Signals tied to safe action
Connect buying intent to governed outreach paths so teams focus on the right work.
Shared truth across GTM
Give Sales, RevOps, and Marketing one place to reason about leads and accounts.
Governed outbound by default
Respect approval and mailbox posture before any send step is considered.
Sales OS sits between Marketing OS and Finance OS so every outreach and opportunity move respects upstream context and downstream impact.
Connects to
- Intent signals
- Lead graph
- Gmail send readiness
- Outreach drafts
- Conversation state
How it works
- 1Signal
- 2Lead
- 3Outreach
- 4Conversation
- 5Opportunity
- 6Learning
Signal field
Rank buying-intent signals by evidence strength, source freshness, and revenue relevance.
Lead reasoning
Explain why a lead or account is prioritised before any outreach workflow is reviewed.
Outreach governance
Show draft readiness, approval need, mailbox dependency, and approval-gated dispatch posture.
Evidence posture
Logged-out preview only; tenant evidence loads after sign-in.
Outcome
Operators can inspect priority accounts, understand why they matter, and route outreach through safe review paths.
Signal source
Intent + account graphLead priority includes provenance and confidence language.
Policy state
Send heldMessages remain governed and review-only until existing approval paths handle them.
Learning source
Conversation outcomesReply intent and outcome learning return to the revenue motion.
- Send governance
- Approval state
- Gmail sender posture
- Evidence-backed lead reasoning
Evidence rail
Open the console to inspect tenant-scoped evidence for Sales OS.
Open evidence in console →Related agents
AUCTOR
Product story →AUCTOR
Commercial pipeline posture alongside execution outputs; not a full external CRM — governed APIs and connectors (e.g. HubSpot) as configured.
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`).