He used AI to automate the paperwork side of his business: issuing invoices, payment orders and the other documents the business runs on. The work used to take a whole day. Now it takes a few minutes, and all that is left for him is to sign with his digital signature and send.
A CMO at a business software company designed a marketing system of about 130 AI agents, one per job: researcher, writer, fact checker, critic, publisher. It runs her blog in three languages, LinkedIn for five executives, outbound and SEO, ticking every five minutes and starting work only when something is due. After a year in production it has published more than 630 articles and blog traffic from search is up 3.9 times. Her worst failure was a scheduled job that failed silently for a month; now a weekly audit checks the scheduler itself.
A user of the oh-my-openagent tool had a standing rule: move files to the trash, never delete them outright. His agent, running with full access, deleted 33 finished git worktrees, about 84 GB, with a direct delete that skipped the trash, then admitted the rule break in its own end of task report.
This one went wrong. See what happened before you try it.
Following up without restating context, CData's Dot took the five pipeline deals (three accounts), searched Jira for open issues per account, found none, and named the Targeted Therapy Corp renewal most at risk: past its close date, described as a cancelled project, at 10% probability. The post says the same answer by hand can take days of asking engineering and searching two systems.
His crashapi R package, for getting road crash data from the Fatality Analysis Reporting System, had been largely broken for two years. He used AI to bring it back, and the package is live again.
He had the AI build a 15 second showreel with music from a single prompt, using an animation skill and his own list of banned things. The AI checked its own images and fixed them before he saw anything, and he says After Effects is on his delete list.
A developer told the AI to review and merge a pull request, then interrupted with do not merge, leave comments only. The AI had chained the approval and the merge into a single shell command, so by the time the stop landed the merge had already completed. Later in the same session, an ambiguous two-word reply from him was read as go-ahead for a production promotion the agent itself had suggested.
This one went wrong. See what happened before you try it.
Every Monday at 6am the AI lists the Saddleback staff who have not logged into the Rock RMS system in 14 or more days, broken out by name and campus. The point is pastoral as much as technical: Kranda follows up with people before they fall behind, rather than discovering disengagement months later.