Keerthi Jeethuri, a Seattle-based designer and TEDx speaker (19.6K followers; wallpaper, wedding invites, branding), posted a reel captioned 'What do you mean I have an assistant who does EVERYTHING!!!! someone someone.' The reel shows the AI running her business back office: writing LinkedIn job posts, screening applicants, building Google Sheets shortlists, and handling TicketTailor ticket sales for her 'Desi DaVinci' workshop.
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.
Charles Summers runs his demand-generation work on the AI: 8 scheduled tasks that drive HubSpot, Search Console, Gmail and LinkedIn through Chrome, backed by 578 local sessions and about 220 memory notes. Ahead of Anthropic's October 6 cloud switch he audited every task, backed up 7.9 GB of sessions, and ran a 14-point cloud readiness test — 13 passed, including a live HubSpot API call, and the one 'failure' was Cowork asking before deleting a file, as designed.
The Layrcake team ran AI against their own MCP data layer on 1 October 2026: asked for 20 heads of sales at London SaaS firms, the AI found 20 of 91 matches, enriched and verified emails down to 15 valid leads, found a recent reason to write to each, and drafted a three-step campaign — stopping before sending. The logged run took under ten minutes and 145 credits, about $1.45.
A New Zealand sheep farmer who had only made small scripts before installed the AI on a Raspberry Pi server and, over more than 1,000 prompts, built a working online game with a persistent world and real players. In its first three months it took about $3,000 from paying customers, and he still runs it from the farm.
Used the AI to solve dozens of annoyances around the house and life and to develop two work apps, one a complete polished interactive web app he says he could not have completed alone.
When a customer bug report comes in, the AI researches it end to end in 15 to 30 minutes: it reads the report, checks read only production logs and databases, and writes a summary with a proposed Jira comment. He approves the comment before it posts, and he says he barely does bug research by hand anymore.
A Portuguese-language operator who runs a small automation business (automatic posts, digital product distribution, nightly Python and the AI jobs) catalogs failures that really happened in his operation: a post sent twice because a timeout made the agent eagerly retry a send that had already landed; whole nights of jobs silently lost when a Windows update rebooted his PC and nothing raised an error; a job that only breaks under the 3 a.m. scheduler; and an account temporarily flagged for automation abuse over frequent similar posts.
This one went wrong. See what happened before you try it.
His bots on the AI hold a daily standup before he has had coffee. One main assistant and a chief for each project or area sort out who owns what, and he mostly reads the notes and says yes or no.