How it works
One email, five stages, one human decision.
Mission Control splits finance automation into the part a model is good at — reading and drafting — and the part a person should own: deciding what actually happens.
Inbox
A connected Gmail mailbox receives an invoice or request. Mission Control opens a case with the email and its attachments.
Drafted actions
Codex matches the case to one of your workflows and drafts the payload for every step.
Approval
A reviewer checks each drafted action against the source email, then approves or rejects the case.
Execution
Approved steps run in order with the approver's own Google and Slack access.
Audit
The decision, the approved payload and each step's result are recorded on the case.
1. Inbox
You connect the Gmail mailboxes that receive finance mail — an accounts-payable address, an office inbox, your own. Mission Control watches them through Gmail’s push notifications. When a message arrives, it opens a case in the reviewer inbox with the original email, sender and attachments attached.
2. Drafted actions
Workflows are written by your team, in plain language: what kind of email this is, and what should happen next. A typical one says: when a supplier invoice for the Ljubljana office arrives, post it to the finance channel, upload the PDF to the invoices folder, and add a row to the invoice register.
Codex — the AI model running inside Mission Control — reads the case, picks the matching workflow and drafts the exact payload for every step: the Slack channel and message text, the Drive folder and file name, the spreadsheet and row values, the reply’s recipients and body. It reads through the connections of the mailbox owner. It drafts; it cannot execute anything.
3. Approval
The reviewer sees each case with its drafted actions listed next to the source email. They check the payloads — is that the right amount, the right folder, the right channel — and make one decision for the case.
Approve, and the exact payloads shown are queued for execution. Reject, and nothing runs. There is no “auto-approve after a while” and no background path that skips the reviewer.
4. Execution
Approved steps run in order using the approver’s own connections. The Slack message is posted by them. The file is uploaded to a Drive folder they can access. The row is appended to a sheet they can edit. If the approver doesn’t have access to something, the step fails instead of quietly using broader credentials.
Payment execution is switched off. Mission Control can file an invoice and tell people about it; it does not pay it.
5. Audit
Each decision is recorded on the case: who approved or rejected it, when, the payload that was approved, and what each step returned. When someone asks next quarter why a file is in that folder, the answer is on the case.
See it run on your own workflow.
Bring one email you handle every week. We'll show you Mission Control drafting it, and you approving it.