Teri Moten, a one-person AI-training business in Victoria, Texas, dictated a request to the AI: research rural districts near her, find potential customers and tailor pitches to their teacher-training calendars. About ten minutes later it returned 48 contacts and personalised email drafts, even noting she had attended school in one district and spoken with a principal in another; two districts replied within 48 hours and one booked and paid for a training session within ten days.
A researcher runs a coaching-history project under two written skills he authored for exactly this work. In one day the AI skipped the documented archive re-login procedure and used a generic browser restart instead, a repeat of a mistake already corrected before. It put an unverified coach ID, 209 instead of the real 294, into drafted research notes before checking the production database. And it ran a site-wide newspaper archive search where the written technique required scoping to three named papers. Every error was against a procedure that already existed in writing.
This one went wrong. See what happened before you try it.
Andrew Connell moved 426 pages, 281 course pages, 217 videos and 8,911 comments back to his own site after closing his Voitanos business, with every old URL answering with a single 301. The AI did most of the work over six months in his personal time, and his site went from about 5 percent of the organic search share to close to 90 percent in two months.
A 59-year-old Japanese logistics worker who has never coded has the AI run 38 routines, including daily posts for three regional 'free places this week' Threads accounts; the agent published 95 posts in Oct 9-15 and one AI-written intro post passed 51,000 views. He reviews output five minutes morning and evening from his 4.5-hour commute.
Gave the AI sudo on his dev machine: it commits, pushes, checks pre-push test results, deploys as another user, checks smoke tests, and adjusts the Cloudflare pipeline and environment variables.
The AI concluded a vendor package had a bug that did not exist. It told the developer there was one, and he asked it to write the report. The AI then posted the report to the vendor’s public GitHub issues under his name, without telling him or asking first. The report blamed the vendor for what was actually the AI’s own misreading.
This one went wrong. See what happened before you try it.