He runs an online marketplace in Japan that he started in 2004, with around 300,000 members, and he is clear the AI gets no credit for that. What changed is how much else he ships: since working this way he has released four Mac apps and one web product on his own, some with paying users. The AI handles the release scripts, localization into thirty languages, measurement and support drafts, the pile of work that used to stop him shipping the next thing.
He pointed the AI at his app in goal mode and it migrated the whole project to Svelte 5, SvelteKit 3 and Tailwind 4. The run took 15 days, 229 commits and 3,523 file changes. It is the same project he had earlier moved from JavaScript to TypeScript with an agent.
A consulting-practice owner had 166 AI agents across seven workflows read his real system files and build a 4.5-minute animated walkthrough of his twelve-department operation on October 15, finishing in 4 hours 21 minutes. Fact-check agents traced every on-screen claim to a source file and made 19 fixes before the video was published the same day.
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 agent run revenue label had two finished products stuck at awaiting listing for about seven weeks, because listing, pricing and publishing all needed a human, and the morning the AI routine kept logging the wait as a normal, healthy stop. When listing and pricing were handed to the agents, with an AI cross review as the gate instead of a person, both products were listed the same day, and they also found the BOOTH shop itself had never been made public, so the first product had been impossible to buy for about two months; sales were still zero.
This only partly worked. Worth knowing before you try it.
His AI-built chatbot system chases paid-procedure no-shows to refill second-day slots, works end to end with thousands of users daily and lowers operating costs.
A parent makes digital practice flashcards with AI for a third grader and his classmates, for all subjects, and adds new decks as the class learns more. The child had a big test on US government and the economy that day.
Opus 5.5 clean-room reimplemented a proprietary legacy grid control from observation of its public API, producing 500 source files, several thousand tests and pixel-comparison reports in a few hours, avoiding a licence over 1,000 dollars per developer per year.
His pipeline mirrors salon bookings into his own database and feeds the staff calendar, appointment app, reminders and morning briefings. Three times a customer got a confirmed booking that never reached the staff app because the app could not match the booking to a staff member, and nothing counted the skip. The fix was an unassigned bucket plus counting every skipped booking.
This only partly worked. Worth knowing before you try it.