Watch Nova clear the AP inbox — inside your real tools.
This is one real morning run of the pinned recipe invoice.exceptions · v3, and it starts where your team lives: Dana asks in Slack, Nova answers there too. In between, Nova works the systems in the big window (the shared Gmail inbox, NetSuite, the contract store) while the channel stays docked in the corner, filling in as she reports. At the one judgment call the windows swap back: Slack takes the stage, Nova goes idle. Nothing here is a mock-up of Nova — the systems are the mock-up; the workflow is real.
The AP inbox, cleared before coffee.
Every clean invoice queued for payment. The one mismatch went to a person — with the exact line, the clause it breaks, and a drafted reply. This is one recipe; the same engine runs reconciliations, policy approvals, access reviews — and incident response.
About this demo. The Gmail, NetSuite, Google Drive and Slack screens above are faithful recreations of the real products' web UIs, and the companies and numbers are fictional. What is real is the shape of the work: the systems touched, the order, the match, the gate. Each step under the window is tagged the way the pinned recipe treats it: fixed where the route is known, judgment kept where it's needed, and a person on every write that leaves the building.
That was one recipe. Your team runs dozens.
Nova deploys in about a week. The first step is a short call to map your stack and confirm access. From there the agent is working on real cases within days.
Every write still waits for a person. Nova runs on your own network, on hardware you control.