Engage
Platform Architecture & All 80 Screens
The complete screen reference across the six operating areas, the FastAPI and PostgreSQL architecture, and the feature-module registry that adds screens without forking the shell.
The full reference
All 80 screens, in the product’s own six groups.
Enumerated from the shipping application’s navigation definition. Related screens are grouped on one line where the product ships them as a family — the count above is of distinct routes.
◎
Where the whole operation is visible
Command
- Executive Home — The board-level view — objectives, coverage and what moved, without drilling.
- Command Center — The operating picture: missions in flight, agent activity, what needs a decision now.
- Missions — A business objective with agents working it — scope, plan, progress and the decisions taken along the way.
- Global Map — Accounts, territories and activity on a map, because market entry is a geographic question before it is a pipeline one.
- Timeline — Everything that happened, in order, across missions, accounts and channels.
- Signals — The buying and risk signals the platform picked up, and what it did about each.
$
Records, and the intelligence beside them
Sales CRM
- Sales Home — The seller’s landing view — their accounts, their conversations, their next actions.
- Leads — Inbound and discovered leads, scored and routed.
- Accounts — Account intelligence — firmographics, signals, relationships, history and the current state of play.
- Contacts — People, roles and reachability, with consent state attached to each.
- Conversations — Conversation intelligence across every channel: what was said, what it means, what to do next.
- Opportunities — Pipeline with the reasoning behind each stage rather than a stage picker.
- Meetings — Booked, held and outcome-recorded, wired back into the mission that produced them.
✉
Campaigns, email, advertising
Marketing
- Campaigns — Multi-channel campaigns tied to the mission and the objective behind them.
- Communications Command — The control surface for every outbound channel and its gates.
- Email Marketing — Programme design, sending policy and performance — execution gated on provider, consent and suppression.
- Mailing Lists & Segments — Audience construction from live records rather than exported CSVs.
- Templates — Reusable message templates, versioned and judged like any other proposed content.
- Consent Ledger — Who consented, to what, when and by what evidence. The ledger is authoritative over any campaign.
- Suppression — Global and per-channel suppression, applied before send, not reconciled after.
- Preference Center — What a recipient chose to receive, honoured across every channel at once.
- Deliverability — Domain, authentication and reputation health for the sending estate.
- Providers — Which channel providers are configured — and therefore which channels can execute at all.
- Comms Analytics — Channel performance, attributed back to the mission.
- Advertising Command — Paid media alongside owned channels, under the same governance.
- Ad Campaigns, Groups & Creatives — The paid-media hierarchy, managed in-product.
- Ad Audiences, Keywords & Retargeting — Targeting built from the same records the CRM holds.
- Landing Pages — Destinations tied to the campaign and the attribution model.
- Budget & Attribution — Spend control and where the pipeline actually came from.
- Ad Analytics — Paid performance next to owned performance, not in a separate tab of a separate tool.
- Voice Campaigns — Outbound voice under the same consent, suppression and approval chain as email.
↗
Forecast, risk, territory, expansion
Revenue Ops
- Revenue Ops — The RevOps home — the health of the revenue system rather than of one deal.
- Forecast Intelligence & Executive Forecast — A forecast with its reasoning, and the executive view of it.
- Pipeline Coverage & Sales Velocity — Whether there is enough pipeline, and how fast it is actually moving.
- Deal Risk Center & Win/Loss Intelligence — What is slipping and why, and what the closed record says about the pattern.
- Territory, Territory Intelligence & Sales Map — Coverage and assignment, with the map to argue about.
- Whitespace Map & Expansion — Where there is unsold surface inside accounts you already have.
- Renewals, Customer Health & Upsell — The post-sale revenue surface, wired to the same signals.
- Customer Handoff — Sale to delivery, with the context that usually gets lost.
- Quotas, Coaching & Conversation Coaching — Goals, and the coaching loop built from real conversations.
- Playbooks, Account Planning & Mutual Action Plan — The execution artefacts, live in the product rather than in a shared drive.
- Deal Room & Executive Relationships — Collaboration on a deal, and the relationship map behind it.
- Partner & Channel — Indirect revenue under the same model.
- Approval Command Center & Pricing Intelligence — What needs authorising, and the pricing evidence to authorise it with.
- Sales AI Agents & Autonomous Sales Activity — What the agents are doing on the revenue side, and at what autonomy level.
- Executive Revenue Command — The top-level revenue picture.
⚙
Work, approvals and the agents themselves
Operations
- Tasks — Everything the platform or a person owes, in one queue.
- Approvals — The human decisions the system escalated, with what it wanted to do and why.
- Autonomy — The autonomy control centre — how much each surface is allowed to do without asking.
- Agents — The agent roster, what each is for, and what it has been doing.
- Workflows — The orchestration between agents, gates and channels.
▦
Settings, health and administration
System
- System Settings — Configuration for the platform and its channels.
- Authentication — Sign-in and session policy.
- Health & Watchdog — Whether the platform, its agents and its providers are actually working — with alerting behind it.
- Analytics — Platform-wide analytics across missions, channels and revenue.
- Knowledge — The corpus the agents reason over.
- Integrations — Provider and system connections.
- Administration — Users, roles and tenancy.
Under it
Platform & architecture.
| API | FastAPI with asyncpg, serving the application and its data layer |
|---|---|
| Worker | A Python async worker process for agent runs, campaigns and scheduled work |
| Web | A command-center shell served by the API behind nginx — a dark sidebar, dense KPI band, table/detail split and a right-hand intelligence panel |
| Data | PostgreSQL, with persistent volumes and durable task, approval, event and audit records |
| Agents | Discovery, qualification, drafting, conversation and revenue agents, each with an explicit autonomy level |
| Governance | Consent ledger, suppression, preference centre, policy engine, judging pass and approval routing |
| Extensibility | A feature-module registry — a module registers its own screens and navigation without editing the shell |
| Channels | Email, voice and paid media, each gated on provider configuration |
| Packaging | A single all-in-one container image — nginx, API, worker and database under process supervision — behind the platform edge |
| Health | A health endpoint plus an in-product watchdog with alerting |
Extending it
New screens without touching the shell.
The application ships a feature-module registry: a module registers its own screens and its own navigation entries, and the shell picks them up. That is how the revenue, communications, advertising and administration areas were added, and it is how a customer-specific surface gets added without forking the product.