A Builder.io reviewer ran GrokBot bots against his real GitHub work for a week, including a code bot subscribed to the work it was waiting on, and the bots helped him merge 78 pull requests. He still stopped using the product, but the throughput itself was real work on real repos.
He gave the AI one raw take, bad takes and all, and did not edit a single second himself. The AI did the color grade, the titles, and captions on every word.
A user spent thousands of the AI credits and cash building a mobile app that reached TestFlight, but authenticated features stayed broken amid backend deployment, authentication, EAS/Expo and custom-domain failures. Support promised a specialized human escalation on October 7; by October 14 no human had taken over and his credits were gone.
This one went wrong. See what happened before you try it.
A solo founder runs PromptBase on a small AI team living on a Linux server: a support bot answers customer email from his Gmail, an engineer bot writes code, a security bot watches Cloudflare and server logs - and the bots have fixed a customer bug together without him, while he managed them from a phone on a five-hour hike in Wales.
Since July 2026 a Japanese creator has run a political clip channel with a pipeline the AI built: it watches source channels, fetches new videos, transcribes them locally, picks highlights from voice peaks and wording, fixes subtitle typos and names, makes thumbnails and titles, exports long videos and Shorts, uploads them unlisted, then collects view and retention data to feed the next round. In 3.5 months it shipped 319 videos for about 1.05 million total views and 1,080 subscribers, though the median long video reached only 268 views; he publishes the failures too, including the agent claiming 'fixed' when it was not.
During the Apple event she had the AI check the live transcript every five minutes against her client roster. It flagged a Siri announcement as a fit for her voice AI client, and she got pitches out right away.
He is not a developer; he is a management trainee at a company made up of five entities. Every quarter, full financials go out to the management team: a batch of at least 25 PDFs from their SAGE accounting software, several of them over 20 pages long. He spent weeks reviewing test files and batches and debugging formatting mistakes to build his own converter, after finding that the AI models themselves could not do the job faithfully on larger documents: they would combine rows and categories or produce totals that added up but were not identical. The AI itself told him the task would need a hard coded deterministic app. His converter can now batch format the whole set at once, with the bolding, blank rows, sum lines and column sizing he is picky about.
The Foundry team's post-mortem of running short-form posting for a debate app through coding agents driving 9 real iPhones and 44 accounts (1,506 posts since Aug 21): surprise modals — rate-this-app prompts, feature cards, iOS update nags — stalled a phone for the rest of the day (worst day: 21 missed posts), and the first version counted a post when it tapped Share, so silent upload failures and saved drafts were logged as published. Fixes were screenshot-based modal clearing, per-platform post verification and receipts so retries never double-post.
This only partly worked. Worth knowing before you try it.
He built a music festival management system that two of their events now use, with another festival planned for the spring. He says it saves them $30,000 to $50,000 per event by replacing the fees they used to pay for third party software, and it has advanced features no system they could buy includes.
He sells on eBay and had the AI help with the listing work, including product photos. That week was his best on eBay in five years, and he credits the bot's help.