Back-office data agent that reconciles invoices & payments into a clean ledger · 4 layout directions
The familiar assistant layout. A persistent agent chat rail on the left where the owner types plain-English asks ("reconcile March payments"); the ledger fills the rest. Cells animate in as the agent works, with a running narration in the chat. Approvals happen as cards inside the chat thread.
| Date | Customer | Invoice | Paid | Status | |
|---|---|---|---|---|---|
| 1 | matched | ||||
| 2 | ▌filling… | ||||
| 3 | review | ||||
| 4 | matched | ||||
| 5 | matched |
The ledger goes full-bleed; the agent collapses into a slim bottom dock that expands when it acts. A human-style cursor glides across the sheet so you literally watch it work cell-by-cell. The dock shows the current step, a live tally, and one big Approve/Undo control. Feels like an operations tool, not a chat app.
| Date | Customer | Invoice # | Amount | Paid | Method | Status | |
|---|---|---|---|---|---|---|---|
| 1 | matched | ||||||
| 2 | ▌ | ||||||
| 3 | matched | ||||||
| 4 | review | ||||||
| 5 | matched | ||||||
| 6 | matched |
Built around trust. The agent proposes a stack of changes as diff cards on the left (old → new, with its reasoning); the sheet on the right highlights the cell each card touches. The owner sweeps through Approve / Edit / Reject. Best when the buyer's #1 fear is "will it mess up my books?".
| Date | Customer | Invoice | Amount | Paid | Status | |
|---|---|---|---|---|---|---|
| 1 | ok | |||||
| 2 | $2,400 ✦ | ok | ||||
| 3 | ok | |||||
| 4 | review | |||||
| 5 | ok |
The most software-native. The sheet is everything; the agent is summoned by a command bar (⌘K) at the top. Changes appear inline as ghost values with tiny per-cell ✓ / ✕ chips and a ghost cursor. No persistent panel — the UI gets out of the way. For power users who think in commands.
| Date | Customer | Invoice # | Amount | Paid | Status | |
|---|---|---|---|---|---|---|
| 1 | matched | |||||
| 2 | $2,400 ✓✕ | |||||
| 3 | matched | |||||
| 4 | review | |||||
| 5 | matched |
For a scripted demo that has to feel real and earn trust with a non-technical small-business owner, the win is a blend: B's sheet-first stage and human cursor for the "watch it run" magic, with C's review-before-commit safety baked into the dock. A is too chatbot for an ops brand; D is too bare for the buyer.
Familiar but cedes a quarter of the screen to chat and reads like a chatbot — off-brand for an operations system.
Full-bleed ledger, a human cursor that works cell-by-cell, and an ink dock that holds live status and the approve/undo gate. The flagged rows surface C's review cards on click.
The safest model — but heavy and light on magic. We fold its best idea (auditable diffs + approve-all-safe) into the recommended dock instead of a full rail.
The cleanest, but a blank ⌘K bar intimidates the SMB owner. Keep as a secondary entry point, not the demo's spine.
Sheet-first stage · a person-like cursor that glides row to row · cells fill with ghost values that settle once accepted · an ink status dock showing the live tally and one Approve/Undo gate · flagged rows pop a small review card so a human always has the last word. One scripted scenario plays start to finish — and a Tweak switches the agent persona and the workflow between Finance (order-to-cash), Sales (purchase-to-pay), and Operations (supplier → in-stock → scheduled → job complete).
build B's stage, give it C's conscience →