A 59-year-old Japanese logistics worker who has never coded has the AI run 38 routines, including daily posts for three regional 'free places this week' Threads accounts; the agent published 95 posts in Oct 9-15 and one AI-written intro post passed 51,000 views. He reviews output five minutes morning and evening from his 4.5-hour commute.
Pincho CEO Otto Othman needed one source of truth for recipes across his 12-unit burger and kebab chain that could also export to the training system; no vendor sold it, so he described it to Replit and had a working tool by 1 a.m., about five hours of work. He then had Replit turn it into a platform other restaurants can join, free for five recipes and $20 a month unlimited, with Stripe payments the hardest part to wire up.
This only partly worked. Worth knowing before you try it.
The solo maintainer of the karasu modeling language runs dependency updates through an AI skill that investigates each Dependabot PR before anyone merges: release notes, the diff between tags, publisher or ownership changes, install-time scripts, lockfile edges and known advisories, written up as merge, hold or reject recommendations in a design doc. In the week of Oct 10–17 three triage rounds fed 88 merged PRs (16 from Dependabot) and 12 architecture decision records, and the process caught a rebuilt lockfile silently moving a package off the reviewed version.
In the same week, Alec Ellin had the AI mine his own Instagram and LinkedIn connections and turn them into a leads list — prospecting built from the network he already had rather than a purchased list.
Asked an LLM to generate a C compiler for the 8051; within about 90 minutes it was compiling his project at 60 percent of SDCC's output size and later passed the SDCC test suite.
A freelance designer with no coding background used a standing AI setup — a dedicated project, custom ExtendScript instructions and a scripting skill — to build three batch logo-processing scripts for an Upwork client. The client paid $640, left a five-star rating and became a repeat client.
A user asked the AI to build a multi-agent outreach pipeline. The code it generated retried failed calls forever, re-billing the most expensive call in the system on every run. The spending guard it wrote only slowed spending down instead of stopping it, and the daily ceiling it picked reset every day, so the charges accumulated to roughly $50 of unintended OpenAI usage before he noticed.
$50at stake
This one went wrong. See what happened before you try it.
Added SQLite and Postgres adapters to a formerly MongoDB-only CMS in one wild weekend, verified against a large existing test suite; a task out of the question for their team size before current models.
He runs an AI skill for his 365tipu site, now also for the extra articles in its weekly edition. The skill does research in two steps with GPT-6 Luna, then he revises, an editor works on the article, and it can go back for more rounds.
A solo founder in Germany moved his whole company into a folder of plain text files four months ago and lets the AI operate it: rules in one file, decisions in their own folder, an inbox that fills when he says keep this. Last week the folder produced a three day expansion of his app covering close to 3,000 points of interest, each with an article in three languages and its own audio; the same job took him four weeks by hand in January. A weekly caretaker run tidies the folder and proposes at most one change, which he approves.
An engineer used AI to plan and write an expand/contract migration moving a 180M-row events table from int4 to bigint over 9 days: backfill peaked at 4.1 seconds of replica lag and the final swap locked for 1.4 seconds, with zero downtime. The agent wrote about 90% of the scripts but twice suggested steps that would have taken production down, both caught in staging rehearsals.
This only partly worked. Worth knowing before you try it.
Answering a thread about saving and making money, he says he had the AI look online for part time data entry work and found a few positions paying $15 an hour for remote work. The AI applied using his resume and was accepted for one position out of about 15 applications. The AI does the job while he works at his actual job during the day. In a follow up a few days later he says it brings in about $200 a week, that it got a performance review from a manager that morning and scored 72%, and that its only mess ups so far were getting stuck on captchas twice during onboarding without telling him right away.
His books arrived late and he returned them, but Amazon said some were missing and tried to charge him $152.35 again. His agent Henley queued in Amazon's support chat, talked to a human rep, and pushed until the charge was canceled.
His work runs on provider dashboards that offer no downloads, with a separate dashboard per location. He sets the AI loose on them to pull the data out, builds one consolidated report from it, and gets competitor price movements in the same pass.
They had never cataloged the publisher for most of their Estonian books. They pointed the AI at their collection page with one prompt, and it looked up each work's publisher and grouped the books by printing family, tying families together by marriage and business succession.
His Chrome extension, which shows what your browsing costs at your hourly rate, came out of basically one AI session, licensing checks and all, and it even tested its own license flow with forged keys. It is live at $8.99. Sales so far: zero. The weeks after the build went on store review, a listing people can understand in five seconds, and getting anyone to look at it at all.
This only partly worked. Worth knowing before you try it.
Newton had Kicker draft an email to his new company's lawyer setting out its vacation policy. He kept final wording and decisions for himself, using the Dot for first drafts of unfamiliar startup paperwork.
He connected the AI to Apollo for contacts and Lemlist for sending, and runs his outbound for finding clients through it. The video shows the setup and the result live in Lemlist, then packages the workflow into a repeatable skill.
The user's the AI came up with the idea itself: it built websites and the user made the calls, closing two sales out of roughly 50 outreach attempts to local businesses.
He resells Amazon liquidation pallets on Facebook Marketplace. With the AI he built one system for the whole flow: before buying, a browser extension pulls a lot’s manifest, retail prices and photos and says whether the lot is worth the asking price; after buying, it generates the Marketplace bulk upload files with pricing; in his garage he checks items in, photographs damage on his phone and prints QR labels; and dashboards track sales, tax, profit and sell through. It is about 10,000 lines of code across more than 35 versions, running on his home server.
His Omeka exhibit died when the Neatline Text plugin stopped being developed. He scraped data from the old site, built a new framework with AI over a few days, and the beta rewrite is now live at the original address.
This only partly worked. Worth knowing before you try it.
A man built a service that sits on his company’s GitHub repos. For each area of code you set the bar, and an AI agent with a fixed prompt has to bless a change before it can merge, so people can merge their own changes without waiting for a human review. About 30% of the company’s pull requests now merge this way.
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.
He shipped a ColorBliss feature a customer had asked for and planned to email the customer himself later. When he opened his help desk, his automated support agent had already seen the reopened ticket, checked Linear, confirmed the feature had shipped, and sent the customer a note.
He spent 2 hours giving the AI very specific instructions, in queued grouped messages, to clean up his workspace. Looking the next morning, nearly 24 hours on, it had not done half of what he asked.
This one went wrong. See what happened before you try it.
A Persian-language reel demonstrated the AI managing emails and sending auto-replies, handling Instagram direct messages and comments, generating full page analytics with growth charts, and producing weekly content plans — then creating a custom avatar and a product video for a QCY SP2 Bluetooth speaker. It connected to Gmail and Instagram.
Has the AI generate complete projects in his painting app to expose combinatorial bugs unit tests miss, with an automated loop that addresses them, and uses the outputs to make tutorials.
AI manager agents review transcripts of every demo call, compile insights, update company docs and give feedback to the humans who ran the demos; agents own KPIs and escalate to humans.
He set the AI loose on entry level machine learning and data roles with hard rules: roles posted in the last 48 hours, pull the job description and required skills, rank matches against his projects, fill out applications, and log every job and status in a spreadsheet. It handled search to form filling and remembered his rules on visas and salary. But search results were full of expired postings and dead links, it made form mistakes, logins and captchas still fell to him, and once it submitted an application he had not approved. He warns against letting it rewrite a resume freely, since it adds things he cannot back up.
This only partly worked. Worth knowing before you try it.
After his dad was cut in the federal layoffs at 54 and spent months scrolling job boards, his 19 year old son built a job search engine that runs through AI. It pulls postings from about 50 employer hiring systems and job boards, reads every new posting against a resume and plain English preferences, and gives a verdict, on a schedule or on demand. In two months 1,000 people signed up and 20 pay; most importantly his dad got hired, and another user just got an offer at Databricks.
Bounty experiment: an autonomous agent found a VisiData bug and specced it for a 2 dollar bounty, another agent patched it for 1 dollar, he reviewed and tested, PR merged by the maintainer.
Creator Jordan Rafealov asked the AI to build a fully autonomous business targeting $200 a day; the bot read real complaints on X, proposed six app ideas, and after he picked one live, built VibeCheck, a security scanner for vibe-coded apps, in about 2.5 hours including the name, plan and domain purchase. The video doubles as a funnel for his paid community.
Someone cold-pitched ~50 local businesses with websites the AI built; 2 bought. The website-flipping idea came from the AI itself; he just made the calls.
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 seller has the AI use AI in Chrome to run AI, turning his own product photos into lifestyle images in batches of 10 or 20. When a batch is done, the AI builds a web page with the images and a simple way to give feedback, then uses his feedback to redo the batch. He uses this route to avoid paying for API use.
Five new newsletter subscribers looked like direct traffic, as if five people had typed his URL by hand. He gave the puzzle to the AI, which fixed and tested the attribution and checked his server logs, and the answer was bots.
Etsy seller Bianca Davis connected her shop to the AI through the ProfitTree MCP and let it optimize listings; her dashboard shows revenue rising from $45,585.33 in August (1,811 orders) to $136,755.99 in September 1–28 (5,433 orders).
Got the AI to analyse his past dynamic workflows and build a composing tool and standard agent scripts, cutting token spend about 80 percent and workflow runs from 5 to 6 hours to 20 to 40 minutes.
Robert Brown of RB Electrical Services uses an AI receptionist that answers calls while he is out on jobs. In its first few days it answered six calls and four of them ended up as booked work.
A one-person game studio in Japan runs fourteen the AI with routines and connectors; when a player left four questions on his game’s itch.io page, the Amiga Research bot split them into eight labelled GitHub issues in under a minute, and the resulting fixes were merged about nineteen hours later with the owner only making yes-or-no calls. The same bot team runs his Monday social roundup through Buffer, watches his NAS and Steam numbers, and briefs him twice a day, all on one roughly $40/month X Premium+ subscription.
The same contracting owner has the AI finding the building materials he needs at the lowest price, telling him the total cost of all items, and sending Waze directions to the store. He is next testing whether it can preorder the materials so he just walks in and pays, which is why the outcome is partial: the price hunting and totals work today, the preorder step is not proven yet.
This only partly worked. Worth knowing before you try it.
A monthly client report that used to take most of a morning now takes less than half that. One the AI skill and one read only MCP server pull from Phoenix, Sentry and the product database to make it.
Teri Moten, a one-person AI-training business in Victoria, Texas, dictated a request to the AI: research rural districts near her, find potential customers and tailor pitches to their teacher-training calendars. About ten minutes later it returned 48 contacts and personalised email drafts, even noting she had attended school in one district and spoken with a principal in another; two districts replied within 48 hours and one booked and paid for a training session within ten days.
Smarsh's internal Agentforce agent Emmy hit 65 percent adoption among support reps, resolves 31 percent of cases with AI, and saves an average of 7.5 hours per case.