Voice AI · Specialist Agents · Executive Operations
What if you could talk to your company?
NEXUS turns a spoken instruction into live intelligence, specialist analysis, or visible approval-gated action across real business systems.
A working executive operating system that listens to the mission, asks for the missing context, routes the work to the right agent or tool, and returns evidence-backed results.
NEXUS command layer
Executive sessionNEXUS
Command layer
One voice interface above the systems already in place.
Read
Analyse
Operate
Deployed, connected and working now. Included in the production smoke test.
Present in the product, but not the primary demonstrated path.
Designed and scoped. Not built. Nothing on this page runs on it.
Direction only. No implementation behind it yet.
Every capability on this page carries one of these four labels, written out in words rather than signalled by colour. Nothing scoped is described as working.
The premise
The interface to work is changing.
Today, executive work is fragmented across messages, dashboards, reports, forms, documents and specialist applications. Each system has its own interface, its own requirements and its own workflow.
NEXUS explores a different model: describe the outcome once, then let an intelligent command layer coordinate the right people, agents, evidence and systems.
Sometimes the result is an answer grounded in live business data. Sometimes it is a decision brief built by specialist agents. Sometimes it is a prepared operation waiting for approval. The executive does not disappear from any of them.
From navigating software to directing outcomes.
Mission types
Not every mission is a form to fill.
A voice assistant that treats every request the same way ends up forcing an approval step onto a question that never leaves the building. NEXUS separates three kinds of work, and routes on the difference.
Read
LiveRetrieve live executive context.
The Morning Brief from Notion, WHOOP recovery signals, or a figure read off the protected Spend Tracker dashboard. Nothing is written, nothing is submitted, and no approval step is involved because no external action occurs.
Analyse
LiveRoute a private report through specialist agents.
A financial report goes to the Financial Analyst, then to the Executive Analyst. Evidence is carried from the source rows all the way through to the CEO recommendation, so every claim can be traced back to the row it came from.
Operate
LivePrepare work inside an existing business tool.
A secure cloud browser opens the real system, fills it visibly while the executive watches, and stops at the approval boundary. Preparing the work and performing the external action are two separate acts.
How an operation runs
One instruction becomes a completed operation
Six stages between a spoken sentence and a finished piece of business output. This is the Operate path — a read-only question skips straight to the answer, and a report analysis takes the specialist route instead. The executive is present for all six, and required for one.
Speak
The executive describes the required outcome naturally — no tool selection, no form, no menu. Speech runs over WebRTC to a realtime model, so the reply lands in conversation time.
Clarify
NEXUS identifies what is missing: dates, audiences, objectives, constraints, output requirements. It asks only for what it genuinely needs, and it asks before any work starts.
Structure
The conversation becomes a validated operational brief. A schema turns a flexible sentence into an exact tool and exact field values, in the formats the destination system accepts.
Operate
A secure cloud browser opens the real business tool and completes the workflow the way a person would — scrolling, selecting, typing, waiting on the tool’s own pipelines — while the executive watches the session live.
Approve
Submission stays locked. Everything up to this point is preparation, and nothing has left the building. The executive reads the completed form, inspects the action trace, and can cancel or approve.
Deliver
NEXUS collects the finished output — copy, documents, images, markup — and returns it to the command centre with copy and download controls, alongside the evidence of the run.
Specialist agents
Two-agent workflowFrom financial report to CEO decision brief.
Two specialists, in sequence, each with a job the other does not do. The first decides what the numbers actually say. The second decides what to do about it. Evidence travels from the source rows through to the recommendation, so nothing in the final brief is unattributable.
Specialist handoff
Two-agent workflowNot in the chain
Financial Analyst
LiveValidates the numbers
- →Normalises the uploaded report before any judgement is made.
- →Validates revenue, cost, margin, variance and material financial risk.
- →Works from deterministic calculation and the supplied source only.
- →Retains row-level source references on every finding.
- →Reports in UAE dirhams in the demonstrated workflow.
Executive Analyst
LiveTurns findings into a decision
- →Receives the validated Financial Analyst output, not the raw file.
- →Prioritises the findings that actually change a decision.
- →Produces a CEO summary, recommendations, owners, timing and an action plan.
- →Builds a nine-slide, conclusion-led executive presentation.
- →Invents no new calculations and no unsupported facts.
Marketing Analyst
LiveOpens the marketing conversation
- →Conversational front door for performance, opportunity and campaign decisions.
- →Spoken only: the Marketing Team system handles the multi-agent delivery.
Communications Analyst
LiveOpens the communications conversation
- →Conversational front door for reputation, messaging, stakeholders and communications risk.
- →Spoken only: the Comms Team system handles the multi-agent delivery.
Working demonstration
LiveA private report, analysed without leaving the conversation.
Spoken instruction
“NEXUS, ask the Financial Analyst to analyse a report.”
Command
“NEXUS, ask the Financial Analyst to analyse a report.” NEXUS opens the secure attachment step rather than asking for the numbers out loud.
Attach
The executive selects the file manually — PDF, XLSX or CSV. NEXUS never reaches into a filesystem on its own. Analysis starts automatically once the file is attached.
Queue
The private report enters a durable queue rather than a live request, so a long analysis survives a closed tab and cannot be lost to a timeout.
Normalise
A separate analysis worker parses and normalises the source before any agent reasons about it, which is what makes the later findings reproducible.
Validate
The Financial Analyst produces findings and risks, each one carrying the source rows it rests on.
Decide
The Executive Analyst prioritises, writes the CEO brief with owners and timing, and builds the nine-slide presentation.
Return
The result view shows the execution timeline, the specialist handoff, the evidence, the recommendations, the action plan and the slides.
Three phrases, three different things
Finance is the easiest place for a voice system to guess wrong, because a dashboard, a workspace and an analysis all sound alike when spoken. These stay separate on purpose.
“Open Finance Team”
Opens the existing Finance Team dashboard.
Navigation“Open Financial Intelligence”
Navigates to the analysis workspace.
Navigation“Analyse a financial report”
Starts the two-agent workflow.
WorkflowOn the data behind this
Reports processed through this workflow are private and stored under executive access control. No report contents, file names or figures from a real run appear anywhere on this page. The illustrations below use invented values.
Working demonstration
Approval-gatedFrom a spoken growth challenge to a structured strategy.
Spoken instruction
“NEXUS, build a launch strategy for our property-management service in the UAE. The goal is qualified enterprise leads within 90 days.”
NEXUS collects what a strategy cannot be written without — the offer, the market, a measurable objective, the total budget, the timeline and any constraints — then opens the real Marketing Team system, selects Strategy, fills the brief, and pauses for review and approval.
The strategy is produced by the Marketing Team system itself. NEXUS is the layer that gathered the inputs, operated the tool and held the boundary.
Out of scope
Campaign publishing, media buying and autonomous execution are not part of this. The workflow ends at a prepared brief and a human decision.
What NEXUS collects first
Missing inputs are asked for, one focused question at a time, before the browser opens.
What the strategy contains
Strategy
LiveThe demonstrated path. A spoken growth challenge becomes a filled brief in the real Marketing Team system, paused for review.
Evaluate
SupportedStress-tests a campaign that already exists. Present in the product, secondary in the demonstration.
Ideate
SupportedGenerates and ranks campaign ideas. Present in the product, secondary in the demonstration.
Working demonstration
LiveVoice to a complete communications package.
Spoken instruction
“NEXUS, create a bilingual maintenance notice. Pest control will take place in Buildings 1 and 2 on Monday from 10 AM to 11 AM. Address owners and residents.”
NEXUS converts the request into an operational brief, checks the audience, the schedule, the affected area, the languages and any hero imagery, opens EDM Gate, fills the real form, and pauses for approval. After the executive says “approve and run,” it starts the communications pipeline.
The finished package comes back to Mission Control as approved copy, a PDF, a JPG and SFMC HTML, with copy and download controls beside each one.
Not rebuilt. Operated.
EDM Gate was not modified, wrapped or reimplemented to make this work. NEXUS drives the existing production tool through a controlled browser layer, exactly as a person would.
Returned to the command centre
01
Approved copy
The signed-off English and Arabic text
Copy02
A4 PDF
Print-ready notice, rendered on demand
Download03
Broadcast JPG
Image version for WhatsApp and screens
Download04
SFMC HTML
Email markup ready for the send platform
CopyWorking demonstration
LiveCorporate translation without opening the translation tool.
Spoken instruction
“NEXUS, translate ‘Our office will close at 3 PM on Friday’ into professional corporate Arabic.”
NEXUS captures the complete dictated English, rejects placeholder wording rather than translating it, opens the translation portal, enters the source copy, prepares the form, pauses before running, and returns the reviewed Arabic result.
The executive can copy the final translation, download it, inspect the completed tool, or keep the browser evidence of the run.
Live context
Read-onlyUseful when there is no form to fill.
Much of an executive’s day is not an operation at all. It is finding out where things stand. These paths read live systems, answer, and stop — no draft, no submission, no approval step, because nothing leaves the building.
Morning Brief · Notion
Read-onlySign off Q3 tower launch budget
Finance needs the approved envelope before the media booking window closes.
Resident notice — chiller maintenance
Bilingual notice to go out before the weekend shutdown.
Review broker commission structure
Open question on whether commission sits inside the campaign budget.
Morning Brief reads active priorities from the executive Notion workspace. It can be refreshed from the dashboard or asked for by voice, and it shows the task title, a summary, the owner, a source link and when it last changed.
The rule that matters: it can only report what is in Notion. A quiet morning returns a short brief rather than an invented one.
Spend Tracker · secure browser read
Read-onlyAI Stack Ledger
Full Spending
Salary and income credits are never counted as expenses. The session opens, reads, answers, and closes.
Spend Tracker is a separate protected system, and NEXUS treats it as strictly read-only. The secure browser operator opens it with server-held credentials, reads the live dashboard values, returns one focused spoken answer, and closes the session.
Ask for the highest spend and you get one merchant and one amount. Ask for the highest AI spend and you get one service. Every figure is reported in UAE dirhams.
It never reaches the operator’s submission path, so there is no approval gate here to remember or to forget.
Human performance layer
An operating system aware of the operator.
NEXUS surfaces WHOOP recovery, strain, sleep, heart-rate and HRV signals alongside the command experience — a small read-only corner of a system that otherwise watches business conditions. It offers no medical guidance, and the readings stay private to the operator.
Questions the Spend Tracker path answers
Answers come back in dirhams. Salary and income credits are never counted as expenses. The dashboard is opened read-only and the operator has no route to the submission path, so there is no approval step here — nothing can be changed.
Workspace
LiveThe result should lead into the next action.
A finished report does not have to become another manual task. NEXUS can carry the output it just produced into a prepared email, check the calendar and assemble a meeting, and hold both at the same boundary as every other external action.
The pattern is identical to the browser operator: everything up to the send is preparation, and the send itself is a decision the executive makes.
Prepare an email
LiveRecipients, subject, body and attachment names are all visible before anything is sent. The button reads “Send reviewed” because that is exactly what it does.
Attach a finished output
LiveA decision brief, presentation or approved copy produced earlier in the session can be carried into the draft as an attachment.
Prepare a calendar event
LiveDate, time, timezone and attendees are assembled, and the calendar is checked for conflicts before the event is offered for approval.
Connect a Google account
LiveAuthorisation is per user, and can be disconnected at any time. Refresh tokens are encrypted before they are stored.
Production acceptance in progress
Carrying each newly generated production artifact into a reviewed draft is built and deployed, and its final manual production test is still scheduled. Nothing on this page reports the result of a test that has not been run.
Nexus Video
LiveStart the meeting without leaving the operating layer.
A room can be created by voice, its guest link copied, and the invitation carried straight into the prepared email or calendar event. The meeting lives inside the executive environment rather than in a separate product.
Access is two layers, not one. The invitation is signed and time-boxed; the room token is minted separately and only after the invitation has been checked.
Signed invitation
12 hours
The guest link carries a signed payload with an expiry and stops working after it.
Access token
2 hours
A separate, shorter-lived room token is minted only once an invitation checks out.
Joins as
Guest
No NEXUS account is needed. The guest gets an anonymous identity for that room only.
Opens with
Camera and mic off
The room connects muted and dark. Turning either on is the participant’s decision.
Human control
Autonomous where useful. Accountable where it matters.
NEXUS can interpret, prepare, navigate and complete the draft workflow autonomously. It cannot perform the final external action until the executive gives explicit approval.
That creates a clear boundary between AI assistance and accountable execution. The executive can review the form, watch the browser, inspect the action trace, cancel the operation, or approve it. NEXUS does not send communications, publish campaigns, move money or take unrestricted external action on its own.
01
Visible operation
The remote browser session is embedded in the dashboard. The executive watches the tool being operated rather than reading a summary of it afterwards.
02
Explicit approval
Preparing and submitting are separate acts. The external action waits for a clear execution phrase — “approve and run” — not a passing yes.
03
Isolated execution
Browser control runs as its own deployed service behind an authenticated gateway. Operational credentials never reach the interface the executive is looking at.
04
Preserved evidence
Every operation keeps an action trace and full-page captures, including the moment a step fails — so a failure can be read rather than guessed at.
05
Cancel without a refresh
“Cancel operation” stops the operator job, closes the live window and clears the stale draft, so a different workflow can start immediately. The executive never has to reload the page to get out of a run.
06
Read-only means read-only
The Spend Tracker path reads a dashboard and closes the session. It cannot reach the operator’s submission path at all, so there is no approval step to forget.
The operating model
No rip-and-replace transformation.
NEXUS does not require every department to abandon its specialist tools. It creates an intelligent command layer above them. Deterministic schemas translate flexible human language into the exact values each destination expects — a spoken audience into the enumeration a form accepts, a spoken date into the format it validates.
One command layer, three execution paths
RoutingRead-only intelligence
Answer returned by voice. No approval step, because nothing leaves.
Specialist analysis
CEO brief, action plan and nine slides, with evidence attached.
Controlled operation
Stops at the approval boundary. Nothing is submitted without the phrase.
System status
What is connected, and what each connection actually does.
Not every tile behaves the same way. A read is not an operation, a navigation destination is not an analysis workflow, and a scoped channel is not a working one.
NEXUS Voice
Realtime command and orchestration
Financial Analyst
Evidence-backed financial analysis
Executive Analyst
CEO brief and presentation
Financial Intelligence
Private two-agent report workflow
Morning Brief
Read-only Notion priorities
Spend Tracker
Read-only secure browser intelligence
WHOOP
Read-only performance signals
Marketing Strategy
Approval-gated browser workflow
Marketing Evaluate
Secondary Marketing mode
Marketing Ideate
Secondary Marketing mode
EDM Gate
Approval-gated browser workflow
Translator
Approval-gated browser workflow
Finance Team
Existing destination, distinct from Financial Intelligence
Marketing Analyst
Spoken front door to the Marketing Team
Communications Analyst
Spoken front door to the Comms Team
Gmail
Reviewed draft, explicit send
Google Calendar
Conflict-checked event, explicit approval
Nexus Video
Signed guest room inside the environment
Telegram
Future command and approval channel
Channels
The command layer should travel with the executive.
The long-term interface is not limited to one dashboard. The same controlled mission could begin from a desktop before a meeting, a phone while travelling, or a Telegram message between appointments.
The channel changes, but the operating model stays the same: understand the instruction, clarify what is missing, read or prepare or analyse, request approval where an external action is involved, and return the result.
Desktop
Available nowFull Mission Control: realtime voice, the live operator view, the approval boundary, specialist analysis, results and downloads, and the evidence of every run.
Mobile web
Coming soonVoice briefing, approvals and access to finished results — the same mission, sized for a phone between meetings.
Telegram
Planned channelRemote commands, structured follow-up questions, approval prompts, progress updates and delivery of the finished files.
Technology
What the layer is made of
Next.js · React · TypeScript
Executive command interface
OpenAI Realtime API · WebRTC
Low-latency voice interaction
OpenAI Agents SDK
Conversational routing and tool-aware orchestration
Structured schemas
Validated briefs and deterministic routing
Supabase
Authentication, access control, private report storage, records, events and the durable analysis queue
Railway analysis worker
Isolated financial normalisation and specialist analysis
Railway browser operator
Isolated browser execution
Browserbase · Playwright
Secure visible browser sessions and deterministic tool operation
LiveKit · WebRTC
Embedded executive video rooms
Gmail API
Approval-gated executive email
Google Calendar API
Conflict-checked scheduling
Upstash Redis
Encrypted OAuth token persistence
fflate
Multi-sheet XLSX ingestion
Notion API
Live executive Morning Brief
WHOOP OAuth API
Private human-performance signals
Upstash Redis
Encrypted OAuth state and token persistence
Vercel
Production web application
Expansion
What the command centre becomes next
Scoped and designed, not built. The operating layer is in place and every specialist seat is live, so the next moves are more places to give the instruction from and more kinds of action to prepare. None of the four below is working today.
Telegram command channel
PlannedBrief NEXUS, answer its follow-up questions, approve an operation and receive the finished files from a phone.
Executive email actions
PlannedPrepared correspondence held at the same approval boundary as every other external action.
Wider Spend Tracker questions
PlannedMore question types against the same read-only path. The constraint stays: it reads, it never submits.
Action tracking and meeting prep
PlannedCommitments captured, owners assigned, and a briefing assembled before the room fills.
This is becoming an operating system, not a collection of tools.
NEXUS began as an experiment in voice-controlled browser automation. It can now listen to an executive mission, retrieve live context, route private analysis through specialist agents, operate existing business systems visibly, and preserve the moment where human judgement matters.
The larger idea remains simple: the future of work will not be defined by how many AI tools a company owns. It will be defined by how intelligently those tools, agents and evidence can be coordinated around human intent.
Do not open the software. State the mission.
Access
Ask for a walkthrough.
NEXUS operates live business systems with real credentials and private executive data, so it is not open to the public and there is no public link. Tell me what you want to see — a walkthrough of the running product, a recorded mission from voice to finished output, or a look at the source — and I will set it up.