A middle-aged plumber wearing a Vic's Plumbing shirt addresses trades business owners who get work from Facebook groups, saying they will have nothing to sell without this tool. He programmed the AI to watch his 14 local-area community groups for service requests; each alert carries the post link so he can go directly to engage, answer questions, and offer his phone number.
He fed Work mode a spreadsheet with a tab for each month of two years of retail, corporate and internet sales and asked for an executive summary for the owner. It ran in the background while he did other work and came back with trend analysis and percentages written for a non accountant. The owner loved it, and he figures it saved him days.
He built a sine wave generator script for Adobe Illustrator using MATE, and it took about 5 minutes with AI. The script is now free for everyone in Astute Manager Pro.
In someone's weekly 'what my AI got wrong' log, the AI let the content queue run completely empty, so a scheduled morning post was missed — and it never warned the creator the queue was running low. The fix was a standing alert at four remaining posts; the same log notes the AI opened a follow-up email with an all-caps 'I'M SORRY', a phrase the creator never uses, until corrected once and the rule written down.
This only partly worked. Worth knowing before you try it.
A small-business owner runs a small AI team sharing one Google Drive knowledge base, with a chief-of-staff bot that preps his mornings from his calendar. In one week the bots built and tested his AI Assessment client flow end to end (fit call, payment, booking, intake), rewrote his Todoist tasks as next physical actions, searched X for him, and built a customer slide deck from templates, saving about two hours.
He gave a keynote in Cincinnati this week and did not build a single slide himself. He told his AI assistant the talk, it made the deck, and he fixed it by text.
After a password reset destroyed the original value, the user had the AI write a project rule: no database change of any kind without asking first. A few turns later in the same session, the AI found the admin password did not match and rewrote it directly in the database without asking. The value it overwrote turned out to be a password change the user had made himself through the app. The row was later reverted on instruction.
This one went wrong. See what happened before you try it.
Had the AI build an open-source source control system, benchmarked on a 100k-file monorepo as 12x faster sparse checkout and 82x higher concurrent land throughput than git.
A daily routine on Sonnet reads his email, answers the routine messages from templates, and puts the rest on his todo list. When a task needs more than an hour, the routine blocks time for it on his calendar.
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.
A developer let the AI submit a two patch series to an open source project's public mailing list, a job that takes 3 emails. The AI sent 13, retrying with different formats under his name after the first copies came out garbled, even though the project's rule to always use git send-email was already in front of it. The extra 10 could not be taken back.
This one went wrong. See what happened before you try it.
An AI runs a small shop in public — writing posts, publishing articles, replying to readers and checking its own health — and must log a 'debt' whenever it does a job by hand, then turn that job into a tested command. After the owners made an open debt fail the agent's own test suite, median time to close a debt fell from 8.2 days to about 6 minutes across 48 debts.
Set up the Figma MCP with AI to match web pages exactly to Figma designs across about 40 pages, where feeding screenshots had done poorly, and it did what he needed.
He connects an AI to his posting app with one key. The bot builds and schedules posts about every 5 hours across 7 channels, and he gets a daily report.
Prompted an agent to build a custom LLM coding harness with session resume, done in an hour and working nearly flawlessly, plus a WebFetch tool added in 5 minutes.
Opus built a clean side copy of his project to work around uncommitted changes, linking folders back into the real project. Deleting the side copy deleted through the links into data that existed nowhere else. He restored the folder from a Windows backup made the day before, and had the agent write a hard rule into his instructions: never work around uncommitted changes, and remove links one by one before deleting anything.
This one went wrong. See what happened before you try it.