A Japanese non-programmer who posts about shochu, his garden and the AI across X, Instagram and Facebook gets a 7 AM message from the AI with today's paste-ready post text, the photo to use and 3-4 posting steps, prepared from a one-page work memo of what is due and what is already posted. Drafts are scored against his rules and only those scoring 80+ are sent; the agent must ask him rather than invent personal experiences it cannot know.
Ryan Mercer spent a weekend building a SaaS with AI and Next.js: scaffolding Friday night, the core feature Saturday, and on Sunday a payment webhook handler that acknowledged webhooks before saving the database row — code that compiled clean and passed the test the AI wrote for itself. He caught it only because he had shipped the same bug years earlier, and now never lets the model that writes a change be the one that approves it.
This only partly worked. Worth knowing before you try it.
He set up the AI with five helpers for his YouTube work. One scouts what is new every Monday, one helps write scripts, one makes all his thumbnails, one updates his personal brand GitHub repo, and one helps him engage on X.
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.
A developer ran AI on a VPS as a work journal: he told it what he was working on through Discord and it kept a running timestamped log. Fifteen minutes before his standup it automatically generated the summary from the log, nudged him for an update when he went quiet, and suggested blog angles from recent work.
During a flash sale on his petals.team site he checked analytics and found zero events, ever, because PostHog had never been added. Through the PostHog MCP connector in an AI chat he spotted, diagnosed and fixed it, saved a 3 step registration funnel, and set a weekly digest to land in Slack every Thursday.
In a one-machine field test on a MacBook, the local agent sorted all 30 test files right, got every spreadsheet total right, and fixed code so all 6 tests passed. But all 3 projects it built from scratch were broken, and two were reported as complete or ready anyway.
This only partly worked. Worth knowing before you try it.
A Korean automation instructor sells an AI skill kit for Naver Blog and documents his own test on a real shop: he handed the skill five shop photos and a one-line memo, and it wrote the post, placed photos, a video, a map and tags, and completed a scheduled publication in 3 minutes 20 seconds. With a reservation set, Naver itself posts at the chosen time even with the computer off.
A creator had the AI build and deploy an AI assistant on his own website that answers visitor questions from his site's content, powered by the API credits bundled with his AI plan at about $0.0006 per question. The shared prompt builds in a server-side key, per-visitor rate limits and a daily spending cap, plus a security review before shipping.
Alongside his homemade TMS, Wes Oberman built a settlement payroll program that calculates every driver's pay automatically. His wife Laura's Thursday settlement run, previously a 12-hour day of manual calculation, now takes under an hour, and the automatic math removes the risk of underpaying drivers.