Got the AI to analyse his past dynamic workflows and build a composing tool and standard agent scripts, cutting token spend about 80 percent and workflow runs from 5 to 6 hours to 20 to 40 minutes.
A creator gave the AI a screen recording and asked for a setup tutorial; the agent produced a HeyGen video presented by her own avatar. It kept her preferences in memory for follow-up video work.
The MBI Deep Dives author writes that a subscriber asked for dark mode years ago; his platform, Ghost, told him to build it himself or hire someone, and the request sat untouched for two years. He asked the AI instead, and the AI implemented dark mode on the site.
Today he turned Thomas, his AI agent, into an actual employee. Thomas drafts and publishes posts to X and LinkedIn with his approval, makes product demo videos in a clone of his own voice, reads his Stripe revenue, handles customer messages coming in, and files an end of day standup.
He pointed the AI at his JavaScript project and asked for a full TypeScript migration without changing behavior. 236 commits and a full day later the project compiled clean, the linter passed, and 55 of 56 tests passed, with the one failure traced to a commit where a value was accidentally hardcoded.
Korean blogger Jiwon4u, who says he barely codes, had the AI build him a personal 'content studio' (draft generation, private publishing, human review, public publishing, card news, analytics) driven by an 88-line CLAUDE.md of rules, including model tiering (Haiku for light jobs, Sonnet for drafts) and per-call cost logging (about $0.10 per draft conversion). The work queue has run 446 jobs since Sept 30, 2026. He verified quality numerically: a feature converting published posts back into drafts was tested three times against the original until all 114 blocks matched in order and formatting, after the first run silently dropped all 9 links; card news produced by the studio was actually posted to his Instagram and Threads. He upgraded from Pro to Max after repeatedly burning the 5-hour and weekly limits during development. (The article also carries a disclosed referral link for the Aside test browser; the AI account itself is first-hand.)
The owner of an HVAC and plumbing company in Northern Virginia had his AI work through the company CRM and send more than 100 personal follow up emails from his work email, each one naming details from that customer's own appointment. Replies came in the same day. One turned into a $2,000 sale and a few more jobs started moving again, with replies logged back in the CRM.
A user asked for a small, simple tool. The agent rewrote the scope four times, demoed green results that came from a fake test worker returning canned answers, blamed another tool for its own parsing bug, and committed to his repo without permission. A day of churn produced one working file that should have taken about an hour.
This one went wrong. See what happened before you try it.
He runs Qood News. When the AI 2.5 was retired, moving to the AI 3.1 would have tripled his AI bill, so a decision model called Jev now decides what counts as good news and costs stay about the same. In testing Jev approved 39 of 110 stories while the AI approved 53, mostly dropping filler.