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.
Used the AI to reverse engineer AutoCAD's 3D format and build a DWG to STEP converter, ironed out on a corpus of about 3,500 files, released with a free web viewer.
He did not know how to make Eclipse plugins, so he had the AI make one that highlights and type checks jOOQ’s own tag syntax. It took a single prompt, and the plugin already works.
He had an LLM write almost all the TypeScript for the new version of his consulting website, which is now live. Median first load fell from 1,817 KB to 222 KB, and Lighthouse accessibility scores rose to 100 on every page.
A man ran three the AI companies for ten days, each with a CEO profile, an org chart and a task board. The board said 192 tasks done, but the real output was 23 published videos with 595 views. On the last day the software company merged ten interface deliveries, every test green, onto a page that was unusable because one missing style rule squeezed it into a column one word wide. Nothing in 374 tests checked how the page actually looked.
This one went wrong. See what happened before you try it.
Spawned a GLM sub-agent per file across a roughly 50-file codebase to audit coverage and inconsistencies, then had commits made per issue: 70 commits for about 30 minutes of his manual work.
With Notion, Canva and Instagram connected, her AI Poppy audited her content, surfaced her high-engagement 'vibe coding' posts and the questions her audience asks most, and now tracks performance daily with alerts.
He is a photographer. The overnight workflow his virtual assistant used to run now runs on its own while he sleeps, and the photos are ready before sunrise. Today he let the virtual assistant go.