The next change, ranked by what it is worth.
Seven agents read the same export and queue what they find, largest recoverable amount first. Each one arrives with the rows it was computed from and two buttons; nothing touches your store, your prices or your ad accounts until you approve it.
- Ranked by monthly recoverable amount, not by recency
- Approve one and it lands in the impact ledger with the figure it claimed
- Next month, check the ledger against what actually happened

- Ranked by monthly recoverable amount, not by recency
- Approve one and it lands in the impact ledger with the figure it claimed
- Next month, check the ledger against what actually happened
What people ask before they trust this number.
Does anything run automatically?
No. Every recommendation waits for a click, and dismissing is a first-class answer. Execution stays off until the ledger shows the hit rate has earned it.
How is the queue ordered?
By monthly recoverable amount, largest first — not by recency, and not by how confident a model feels. A $7.3K discount leak outranks a $200 pricing note whichever one was found this morning.
What stops it recommending the same thing twice?
An approved move lands in the impact ledger with the figure it claimed and is measured against what happened over the next 7 and 30 days. A dismissed move is recorded too, and the playbook stops proposing what you never take.
What else the same export computes.
Run it on your own export.
Fourteen days, no card. Upload a file and the figures above compute on your rows.
BizFalcon AI