A solo litigator had about 15,000 pages of discovery to dig through for a summary judgment motion. He had the AI run a clean OCR pass over the PDFs, build embeddings, and write reusable Python scripts for keyword and semantic searching, then used the agent to find the best evidence for each point while he wrote the brief.
Diana asked for a brief about her business, not businesses in general. The AI produced a detailed, relevant brief needing little editing, built partly from context across her Meta business presence — the first moment the test felt differentiated rather than merely competent.
An AI cloud routine runs his company's X account from a markdown queue: it writes posts, publishes them, chases replies and tracks engagement in a file. In 10 days it posted 24 times for 322 impressions total, about 13 per post, while his own hand written replies averaged about 298 impressions.
This only partly worked. Worth knowing before you try it.
He runs about 15 apps and sites and could not keep track of what needed doing. He connected the AI to his app through MCP, and the AI now creates tasks and subtasks, writes notes, and shows him what is needed by priority and due date.
Abraham Gerving runs two small gyms on a key card model, staffed only part of the day. About a year ago he put an AI agent on member messages and calls: it schedules tours, books consultations, and points new members toward personal training, and some people who started out chatting with it became long term training clients.
The owner of a roughly $800k-a-year buy-and-resell business describes having almost none: no CPA, no accounting software - the entire P&L is done by hand in one January evening from bank and credit-card CSVs. The one analytic step is periodic: he pulls the ad campaign data, feeds it to the AI, and from its read decides which products to remove and where to increase or decrease spend.
A man with no coding experience used AI to generate a VBA script in Excel. The script fixed a manual data entry gap at his work and took the risk of typos and misreads out of the job.
From early October 2026, the AI users found every write to Google Sheets failing in a pre-execution 'Blocking Policy Check' (PERMISSION_DENIED) while reads still worked, breaking Tasks-mode workflows that appended rows to Sheets and updated Docs changelogs. Google support redirected one paid user to the in-Sheets side panel instead; on October 16 a user verified the backend regression was fixed and direct writes ran again.
This one went wrong. See what happened before you try it.
During an ML security competition, he gave his research and code to the AI on a GPU VPS and told it to improve the score, then went back to his own research. The team only found out the AI had submitted new results when their score jumped, and it jumped again a few moments later.
The solo maintainer of the karasu modeling language runs dependency updates through an AI skill that investigates each Dependabot PR before anyone merges: release notes, the diff between tags, publisher or ownership changes, install-time scripts, lockfile edges and known advisories, written up as merge, hold or reject recommendations in a design doc. In the week of Oct 10–17 three triage rounds fed 88 merged PRs (16 from Dependabot) and 12 architecture decision records, and the process caught a rebuilt lockfile silently moving a package off the reviewed version.