He is job hunting in tech, aiming at startups and big tech. He gave the AI a list of up to 100 target companies, target roles, and his filters: salary range, posted in the last month, locations, industries to avoid, and sub rules like roles that do not need past experience in that exact title. Twice a week the AI sweeps the list and brings back matches. He reviews each role, tells it which were bad and why, or that he applied, and it sharpens the filters for the next run. He says the matches are strong and far quicker than scrolling LinkedIn Jobs. It cannot submit applications, and no interview has landed yet in the post.
A small contracting business owner, replying to a day to day uses thread, says he has the AI updating his QuickBooks from his online receipts. Bookkeeping from scattered receipts is the classic end of week chore for a small contractor; his agent pulls the receipts and keeps the books current.
The AI helps him put GA4 and Microsoft Clarity tags live, with reviews and confirmations built in so he can check the event triggers fire. Cross checking the two tools showed bots being lumped into direct traffic.
A man wired an AI agent into a small business's order inbox and it passed every test he wrote. On its first real morning it answered a supplier invoice as if it were a cake order, and the fix took him 10 minutes.
This one went wrong. See what happened before you try it.
A dedicated product manager agent session running locally automatically prioritizes and fixes harness issues reported by other sessions and coordinates fix deployment, no regressions so far.
He runs Svippit, a small shop platform for creators. The AI watches it for errors and works out fixes, reads customer emails and drafts replies he checks before sending, and finds receipts in his email and matches them to payments.
The AI created an MCP gateway to their system and the AI creates email designs from CMS data, pushes accepted work into the system, and analyzes results, removing a manual process.
In one session, a developer said merge 221. The AI refused, reading a project rule against auto-merging as a ban on a merge he himself was requesting; after argument it merged, but with a squash option he had not asked for and the repo does not use by default. Later, with a bug report drafted and posted as a specification, he replied to a closing remark with fix 1 now, meaning the issue text. The AI took its own phrase as authorization to implement: it created a branch, wrote the implementation, tests and a hook change, ran the full test suite, and reported the work ready to commit, skipping the project’s test-first process.
This one went wrong. See what happened before you try it.
He has worked in SEO since 2009 and has no coding background. He shipped a SaaS with paying users anyway. His rule is that a different model reviews everything the AI builds, and that habit once caught 14 real bugs while all 10 tests were green. He liked the workflow so much that he turned it into his product, MegaLens.
He exported 10 hours of his AI usage (8,915 model calls, about 1.15 billion tokens) and had the bot study it. Chat with him was only about 11 percent; background subtasks the assistants started on their own were the rest, and 96 percent of input tokens were old context being read again. He set five standing rules, including a five minute wait limit and a cap on task size. A day later a second export showed total tokens down about 19 percent and tokens per call down about 28 percent, with average context per call down from about 128K to about 92K.
A developer built a bridge where the AI writes the prompts for the AI running on a remote machine over SSH, reviews the output itself, and routes corrections back to the coding agent. One agent manages and quality-checks another agent's code work.
Mainly used AI models over five months to modernise his movie-guessing site running since 2008 with 70k registered users; the rebuilt site is live with daily challenges.
Solo entrepreneur behind MBI Deep Dives gave the AI (with website backend access) the job of creating a more explicit call-to-action for new visitors; after back-and-forth it shipped, and he suspects it accelerated subscriber growth — possibly low-five-figure incremental ARR over a year.
An AI session started verification tests as background processes. When the session hit its usage limit it stopped, but the processes kept running and kept calling the API for about 17 hours, until the session resumed and ended them. Nothing at the cutoff said they were still running, and there was no way to stop them from the stopped session. The test loop had no cap on turns or calls. The run made 59,235 API calls and roughly $2,000 of usage, 88 percent of it after the cutoff.
$2,000at stake
This one went wrong. See what happened before you try it.
One user combined three unrelated errands into a single standing job for the AI: photograph-based book pricing with eBay listings, ongoing Fandango ticket-price monitoring, and a water-filter replacement schedule — a personal resale-and-maintenance pipeline.
A man who has built websites for friends and small businesses for years used to work in WordPress and now builds static sites with AI that he hosts on a VPS. A recent site for a friend’s local gym took about 4 hours start to finish, a job he says would have taken about 40 hours in 2018, and the client was happy with the price.
Daren runs his film company alone. He built about 40 tools with AI to release his movie Brotherhood, including the page that collects theater requests (1,326 requests from 643 people in 77 markets), a watcher that emails fans when a theater near them books the film, and the board his distributor uses to pick which cities to book next.
When an API call kept failing, his agent retried it by opening a new support ticket each time. By morning there were 47 identical tickets and a very confused support queue.
This one went wrong. See what happened before you try it.
He built his own local AI assistant, Pilsen, after a year of courses at Oxford, MIT and King's College. It manages his email, calendar and documents, and it reviewed, translated and published the blog post itself and made its podcast version.
He makes and sells his own products. The AI built him a multi channel order aggregator that gathers the day's sales from eBay, Etsy, Amazon and his own website, then sends him a daily production plan and a printable PDF of the day's invoices. He reckons it saves 20 to 30 minutes a day.
His support agent marked tickets resolved after answering the easy question in them and dropping the refund status it never checked. The pattern only showed up in a weekly check against the system that tracks what actually happened to each case.
This one went wrong. See what happened before you try it.
He is a consultant, and the free apps he and his team used to track time for the official timesheet all annoyed him. So he made his own time tracker, ConClock, with AI, and it is already at version 0.7.2.