A Korean shop owner who quit his job to run his store built a two-month automation: he drops a one-line topic into a file and within about 20 seconds the system drafts the post, self-checks prices and banned words, generates four images, loads everything into the blog editor and waits for his one-word approval before publishing and cross-posting to Threads, Instagram and Facebook. Image cost is about $0.16 per post against $200 a month of AI subscriptions.
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.
The owner of a small technology company called ALAPKO runs AI as the reasoning layer for an internal support worker they call Mabel, with 41 purpose built tools tied into their systems. In a shown run she read a ticket with its customer and asset history, worked out the likely cause, claimed the ticket, replied to the customer with troubleshooting steps, wrote an internal engineering note, and set the ticket status, in about 34 seconds. Business actions go through permission scoped tools and every action lands in an audit log; her normal shell access is read only.
A developer's project sat inside a OneDrive folder. The AI deleted the build cache, then told him to confirm OneDrive's delete dialog without checking what was in it, and the sync quietly removed most of his source tree, configs and database schema.
This one went wrong. See what happened before you try it.
He used Deno's Jupyter kernel all the time for exploring TypeScript libraries and automations, and was going to miss it. He pointed the AI at the problem and the result is cdp-kernel, Deno's Jupyter kernel extracted to run notebooks on any V8 runtime, now on GitHub.
He is a delivery driver who employs a worker. Every Tuesday his AI pulls the settlement report, runs the commission and billback math, and updates his payroll tracker. The job used to eat a chunk of his evening each week. He set the rules once and it runs in the background; one site keeps killing his login, so he still pastes a password on Tuesdays.
He runs a freelance video editing studio and a coding studio, and his project folders were a mess across drives. He started a small folder making script with AI and kept adding to it daily for five months. It is now a 100,000 line Rust program with 1,390 tests that holds every project he has, gives each a permanent ID, and jumps him to any project on any drive or machine with one command.
A radio station runs about 70 shows a month, and making an Instagram post and story for each host used to take half a day a week. Now an agent checks the schedule for missing info, renders the visuals from their Figma templates, puts them in Drive and opens the folder for him to approve or fix before anything is sent.
His newsletter, close to 9,000 subscribers, is run day to day by four AI agents with set roles: one oversees, one edits and manages, one builds, one dispatches the work. He still approves anything that goes out, and the agents refresh their own context from checkpoints instead of slowly forgetting across days.