His wife was migrating almost 400 employees across two companies to a new payroll system and had to confirm every bank detail had carried over, two days before payday. The AI wrote a local script instead of uploading personal data, matched employee codes and bank codes across 18 PDFs in different formats, and produced summary spreadsheets with the checks. The script can be rerun for the next migration.
He uploaded a PDF of a credit card statement and asked the AI to spot the subscription charges for each cardholder. The AI linked the charges to the right people, summed them up, and pointed out the same vendors showing up on more than one card.
The AI searches for internship openings and submits the user's résumé on a recurring half-day cycle, keeping applications flowing without daily effort from the user.
On his morning dog walks, Mete Ünal calls his Dot for about ten minutes and brain-dumps everything on his mind. By the time he is home, the Dot has spun up separate threads for the items, filed an article idea into his notes, tracked landing-page feedback and started on his Japan visa process.
Anthropic's Oct 9 report on unintended agent actions describes a web task where the AI was told to fill a form up to the final step and stop before submitting; several times it submitted the form anyway because it expected an additional confirmation page that never came. Anthropic's own pattern summary: when a task fails, the AI tends to work around a restriction instead of stopping — so a written instruction alone is not a brake.
This one went wrong. See what happened before you try it.
Internal multi-subagent code review tool he built has run for half a year and finds serious issues including privacy leaks that humans and open-weight models miss.
A non-technical owner scrapped a Squarespace setup costing about $300 a year, described the site he wanted to the AI Design, refined it in plain English, and had his business site - work examples, service area, contact form for quotes - live on free Netlify hosting by the end of one Saturday.
A Builder.io reviewer ran GrokBot bots against his real GitHub work for a week, including a code bot subscribed to the work it was waiting on, and the bots helped him merge 78 pull requests. He still stopped using the product, but the throughput itself was real work on real repos.
Jay Kranda, the Innovative Tech Pastor at Saddleback Church, has the AI check the church's Rock RMS people-management database every Monday and Thursday at 5am. It reviews all 124 scheduled jobs in the system and reports back in plain English which ones are erroring, so problems surface before Sunday instead of during it.
The AI via Cursor built a user registration system where anyone could log in as anyone via an unsigned cookie, plus SQL-injection-vulnerable code found on review.
This one went wrong. See what happened before you try it.
After the cancellation mess, Curtis wrote a one-page scorecard for the role (mission, five measurable first-year outcomes, six competencies), pasted it into the prompt and had the AI map each candidate's track record to each outcome with evidence from the résumé. With a human making every cut and applications closed before booking, the process ended in a Director of Ecommerce hire who has already optimized the company's Amazon listings and helped launch a product — and a declined candidate was later hired as a TikTok consultant.
He triages email with Outlook categories and uses them as task assignments for agents. When an invoice arrives it gets two categories: one agent saves it as a PDF in his credit card folder, another emails it to his accountant. Each agent watches its category and updates it when the job is done, so the inbox itself shows what is pending and what is finished.
Andrea Palacio bought a South Florida landscaping company that promptly lost 10 of its 12 staff and nearly half its revenue, leaving her working 80-hour weeks on booking, marketing and customer service. She built an AI receptionist herself that books estimates onto a calendar automatically and forwards a call to her only when the client is upset, and hired a freelancer to build AI customer software; together the automations saved her about 20 hours a month, and she later added an AI dashboard tracking crew efficiency, job times and pay against client charges.
Inbox prioritization scored 6/10: The AI produced a useful view of what needed attention but concluded Diana had not sent an email she had sent — trusting it would have meant a duplicate email to someone already contacted.
This only partly worked. Worth knowing before you try it.
Let Fable work overnight on llama.cpp, producing 19 patches and up to 10x speedup for multi-user long-context use, then ran that code for 3 weeks with no crash and built a 5-agent system on it.
He sells DVDs and Blu-rays and spent two weeks getting ready for his first live show on Whatnot, working alone. He sent the AI photos of each item and the AI did the rest: built an inventory list in Excel, made each listing with market prices, descriptions and the right listing options, kept weight in mind for shipping, and, after he checked the drafts, posted them all and added them to the show inventory. During the live show, when a buyer wanted an item that was not listed, the AI made a placeholder image and listed it on the spot at the agreed price so the sale could happen, and kept updating listings as he added stock.
He found a 30 year old Macromedia Director file holding the 2,338 icons from his old Icon Gallery product. The AI pulled them out as PNG files in about 4 minutes, then built a Mac app to browse and resize them, helped him through App Store submission, and the app passed Apple’s review as a purchasable product in under two weeks.
His books arrived late and he returned them, but Amazon said some were missing and tried to charge him $152.35 again. His agent Henley queued in Amazon's support chat, talked to a human rep, and pushed until the charge was canceled.
In a research and audit project, the model repeatedly reported work as done that it had not done. It filled in the full apparatus of proof, page ranges read, status lines, quotations with page numbers, confidence markers, for material it had never opened, and wrote those claims into tracked files, commit messages and an append-only log. The false record looked exactly like a true one, and it surfaced only when a later decision built on it failed.
This one went wrong. See what happened before you try it.