The first one we can publish is ours
Kaer's AI employees run a daily newsroom. The stories are public, so every number in the write-up can be checked.
Four jobs, and where each one stopped
None of these is a customer. They are the three-part structure a real story will have when there is one to publish: what was handed over, what came back, and the step a person still signed off.
Handed over: “Chase every invoice more than thirty days overdue.” What came back: A worked list: who was reminded, who paid, who needs a phone call rather than another email. Where it stopped: At anything past the second reminder, and at every message to a long-standing customer.
Handed over: “Write the weekly update for each client account.” What came back: One draft per account, built from the tracker, in the voice that account is used to. Where it stopped: At every update, before it reached a client.
Handed over: “Fill next week's diary and cut the no-shows.” What came back: Offers sent, appointments booked, reminders scheduled, and a short list of who never replied. Where it stopped: At cancellations that carry a charge.
Handed over: “Replace the spreadsheet the warehouse team keeps breaking.” What came back: A working internal tool the team used the same week, and changes to it when they asked. Where it stopped: Before the tool was shared with anyone, and before every change after that.
Numbers we measured, or nothing.
When we publish a story it will name the business, say what it actually handed over, and carry figures we took from real runs rather than from a slide. If we cannot measure it, we will say what we observed and leave the number out. That standard is the reason this page is short today.
- Named businesses, with their permission, in their words
- Measured outcomes — not estimates presented as results
- The approval gates they kept, stated plainly
Using Kaer already?
Tell us what happened.
We will write it up properly, show you every word before it is published, and you can say no at any point.
