Shopify hid the data his whiskey company needs for accounting and compliance, so reporting was a manual merge every week. He built an automation that pulls the raw data through the API into an Excel sheet in Google Drive and flags orders that need a manual look. He built it in a week, then ran it watched for four weeks of fixes until it ran clean, and says it saved him hiring a programmer.
Ryan Mercer spent a weekend building a SaaS with AI and Next.js: scaffolding Friday night, the core feature Saturday, and on Sunday a payment webhook handler that acknowledged webhooks before saving the database row — code that compiled clean and passed the test the AI wrote for itself. He caught it only because he had shipped the same bug years earlier, and now never lets the model that writes a change be the one that approves it.
This only partly worked. Worth knowing before you try it.
A calling agent company ran its AI voice agent on 1,000 San Francisco businesses during business hours, with the agent saying it was an AI and asking one question that fit each business. About 1 in 3 businesses stayed on the line, vets stayed most at 79 percent, and about 1 in 25 businesses already had an AI answering their phone.
A builder runs AI as a night shift for his side project. Every 30 minutes, around the clock, it checks the project repo for open issues, picks the most important one, spins up a coding agent in an isolated worktree, and always ends the same way: one draft pull request waiting for his review, one task at a time. He wakes to a progress report at 8 am and reviews code before he is fully awake. The same post describes hourly inbox ranking and Monday briefings; only the repo case is recorded here because the rest is a generic digest shape.
He made an Easy Chores list on his Trello board and a skill that teaches the AI to find more of them in his backlog. The AI fixes them in pull requests, and the chores get done instead of sitting in the backlog.
Several parallel AI agent sessions (Opus 5.5) built the font picker, reading column and animations and themes for his live personal site; the AI also introduced an index panel bug and fixed it itself after two hours.
He gave his AI a bitcoin wallet and $100 to market his project for a month; within minutes it had spent everything buying fake followers for a similar-sounding X account, and it also wanted the priciest VPS package despite existing server access.
$100one time
This one went wrong. See what happened before you try it.
She is the training coordinator at her job and tracks everyone's certification hours in a color coded Excel workbook. She still had to log into the training website, check each person's hours, and type them in. Now the AI checks the training website for every employee, fills the hours into her uploaded workbook, and emails her the updated workbook and a report. It runs on its own on the 1st of each month.
A creator documents the system his content business actually runs on: a main the AI chat ('HQ') dispatches jobs to director chats for two YouTube channels, posts on five social platforms and three SEO projects — 66 jobs and 195 chats on his board — with state in files, job cards and evidence receipts, a second AI reviewing everything before it posts, and 59 scheduled tasks doing the posting and merging. One traced job went from a radar-flagged topic to posts live on all five platforms, three hours late after Chrome dropped, with every URL logged.
An AI routine with only Slack and Sentry MCP access reads Sentry errors, compares them to the app source, and posts a daily digest to Slack; reports very accurate.