Ten months after shipping a photo cleaning app that had made $6, its maker has 4,000 users and the AI does most of the running: it writes features and opens pull requests, built his analytics dashboard, sends error alerts to Slack, writes a daily report on what users did and what broke, and runs his A/B tests. He decides what to build and reviews the code.
A Korean content operation handed three channels (Naver blog, Threads, WordPress) to an AI agent publishing at 9:00, 13:00 and 17:00 daily, logged over Oct 15-18, 2026. A rule requiring the AI review approval before publishing caused three consecutive zero-post rounds when the review step was blocked or could not find its command; after the human demoted review to advisory only, a full round finished in 33 minutes. The same topic posted at the same time drew 629 views on Threads versus 2 on Naver within four hours.
This only partly worked. Worth knowing before you try it.
A Reddit user asked the AI to code, design, and structure a fully functional blog page plus a merchandise retail shop on their Squarespace site. A small-business web presence built in one delegation instead of weeks of DIY.
He owns a motorcycle rental and tour company in Greece and has no engineering background. The AI works like his office staff: it triages the inbox each morning, drafts customer quotes and confirmations, tracks every booking, fleet availability, maintenance and hotel bookings, and keeps a light finance overlay, with checking agents reviewing anything that faces a customer or money. A database it built replaced a dozen spreadsheets. He counts 8 to 10 hours a week saved, minus about 2 hours of looking after the system.
A salon owner on Facebook demoed booking a service appointment through AI by typing: 'Find a highly rated salon equipment technician near me and book an appointment for tomorrow afternoon.' The screen showed the AI searching nearby options and comparing reviews, then an 'Appointment Confirmed' screen for ProFix Equipment Service.
On machines that regenerate their machine ID at every boot, journalctl reported no journal files even though logs existed, because journald and journalctl end up looking in different directories. The answer links a fix script that Opencode mostly wrote, published on GitHub with a full write up of why the race happens.
Built with agents over about a year: a production billing system for his small telecom company, a multiplatform app, internal tools in use, and a coding agent harness now used by non-technical colleagues.
He runs product marketing at a SaaS company. The AI audited where old icons appear across 12 products, sites, decks and emails and produced a tracker of about 200 rows to assign out. It built the URL redirect map for a site restructure, runs a browser routine that pastes page text into a sheet, and writes quarterly status updates in 20 minutes instead of most of an afternoon.
He now uses AI for design work and for putting print plans together. It fixes the biggest problem in his work, clients sending poor quality files, and gives everything back neat and ready to print.