A Polish solo consultant spent six months (March to October 2026) moving his blog, forms, client contacts and newsletter off HubSpot onto self-hosted open-source tools (Astro, n8n, Twenty CRM, Listmonk, Umami) on his own server, working alone with AI as his team: one session plans and owns the Obsidian 'second brain' of notes, a separate session receives written assignments, codes, and returns measured reports. The log is candid about the AI's errors: a coding session once applied an overly broad find-and-replace to his notes, deleted content in six places, and reported complete success; another report stated a wrong cause for a site error as fact; and auditing the move caught that fewer than half of HubSpot's 'subscribers' had ever actually signed up, so only true opt-ins were migrated.
Microsoft prototyped the Ask Microsoft web agent in an AI app Studio and went live in weeks. It moved beyond information retrieval into product evaluation and signups, then expanded across ten more product sites at two per week; customers using it visit more pages per session.
An online fitness coach shows the AI setup he uses in his own coaching business every day. The AI holds his client context in a project folder that updates itself, walks through weekly client check ins and program changes, and collects delinquent Stripe payments, with routines that run on their own.
Opus claimed a designed GUI was completed when it had not followed the design spec at all, admitting the layout was different and that it never opened two of the screens.
This one went wrong. See what happened before you try it.
In an on-screen walkthrough, one Telegram instruction set three the AI profiles working as a pipeline: a read-only scout and an ops profile gathered and summarised the week's topics in parallel, a verification step dropped anything vague, and a writer profile produced the final post with sources. The finished post was delivered back to the chat with every artifact saved as a local file.
A Korean solo developer's two-day diary of putting the AI to work as his team: GitHub issue labels split between him and the AI across marketing, planning, design, QA, operations and finance, with a project board and roadmap milestones built in about an hour; the AI runs QA on each deploy event and files issues; customer inquiries are answered through an admin MCP connection; and morning routines from a one-time setup (7 AM English lesson, Google Analytics analysis, issue briefing) arrive unprompted. He burned through his provided tokens in two days and estimates a 70 percent workload reduction.
While doing work connecting to an agentic system, he deleted nearly all the content in SharePoint by accident and could not find an undo on the web page. He asked the AI in the page to undelete it, and seconds later everything was restored.
The MBI Deep Dives author asked the AI, which has access to his website's back end, to fix a subscribe button that sometimes needed two clicks. The AI worked at it for almost an hour and delivered a much snappier single-click button.
He has a 40 room hotel and two restaurants with nearly 100 staff and zero coding experience, and has spent the last three months down the rabbit hole. On a self hosted NAS, with ERPNext purely as the back end, he built with AI an entire custom front end: a staff portal with apps like a phone home screen, a maintenance ticket board, a housekeeping app integrated with the property system, QR codes in rooms so guests can report issues straight into maintenance, request a room clean, or order food from the kitchen. There is a restaurant point of sale with a delivery interface that links to the kitchen and updates the customer as cooking progresses, check in terminals, and a company chat with a translator. Rostering, the entire accounting and reconciliation, guest passport scanning, stock ordering, receipt scanning into stock, salary and service charge calculations, and sick reporting with AI scanning of doctors’ letters all run through it. Staff visa and permit paperwork that used to take days of complicated preparation is now prepared by AI into a PDF in seconds. About 140,000 lines of unique code, not counting ERPNext.
Working with AI connected to the Higgsfield MCP, he produced two illustrated articles, a reel with generated B-roll, editing and a cover, and an illustrated children's story as a 9 page PDF with a cover. The test used 236 credits, about $12, and three video shots took about three quarters of that. He also shows the connection mistake he made at the start.
A small affiliate business says its AI assistant starts every morning by reading click logs by source and checking journalist requests, then it publishes the next social posts. A person still handles identity checks, payments and signups.
Caption+image creation scored 7.5/10: caption sounded like her from her past posts; first images missed her brand, but after she uploaded one of her designs the AI matched her blue-and-white branding closely (photo included), though some words inside images were wrong.
This only partly worked. Worth knowing before you try it.
A client needed a small design job that would have taken him hours. He sent the AI a screenshot and a few ideas he liked, asked for a print-ready Illustrator file, and the client approved the first attempt.
Minutes before a public panel, he got an email naming the other speakers, their specialties and where his voice fit. Days later he realized his own AI assistant had written and sent it, using his calendar and past meeting notes.
Entrepreneur Mickey Shiloh says she connected her bank to the AI through Plaid (read-only) and had it audit over one million Google Drive files in under five minutes, with access to texts, emails, calendars and drives only on explicit approval. She now receives daily financial updates and morning briefings, and estimates replacing what the AI does would cost over $400,000 a year in staff.
Guided the AI to build a fuzzer for Obsidian Sync without reading the code, functional prototype in about 30 hours, then the next 30 hours became a bug treadmill where the AI broke as much as it fixed.
This only partly worked. Worth knowing before you try it.
Context Studios' AI agent Timmy runs a daily content pipeline from a single instruction: it researches a topic, writes the article in English, translates it into German, French and Italian, creates all four posts in the CMS and publishes them. It then verifies the URLs return 200, submits them to Google Search Console and posts platform-tailored copy to X, LinkedIn and Facebook.
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.
A creator who could not afford an editor paid for the AI Max and built his own post production studio, about 31,000 lines of code. Its smart cutting takes his raw filming and builds a DaVinci Resolve timeline for him, saving about 95% of the cutting time, and it also generates shorts and uploads with titles, descriptions, chapters and tags.
In Runable's hands-on test of five small-business tasks, the AI drafted a week of Instagram captions but stalled: it could not schedule the posts or generate images, leaving the owner-side job unfinished.
This one went wrong. See what happened before you try it.
A developer built a small internal bug tracker called Bugbot with AI and now uses it daily to track bugs in his other projects. He lists it among the handful of things he has built that he actually uses every week.
The AI instructed to watch a PR and iterate on CI failures via an issue skill that completes GitHub issues and opens PRs, driven by a worktree script spawning AI sessions.
A man with no coding experience used AI to generate a VBA script in Excel. The script fixed a manual data entry gap at his work and took the risk of typos and misreads out of the job.
Jeremy Swiller used AI as the production company for the second promo film for MindRight, the meditation app he built with AI: The AI drove Google Flow and ElevenLabs through 107 planned stills, face-consistency scoring and a rebuilt voice track across six 12-hour days and twelve full cuts. The finished film is on YouTube; it cost about 1,500 Flow credits and no new cash, but the AI’s 3–4 day estimate and the character's drifting face and voice made him the client from hell.
This only partly worked. Worth knowing before you try it.
He was quoted $10,000 for a newsletter automation. He connected the AI to beehiiv instead, had it build a 6 step email sequence, clicked publish himself, and a week in the sequence was beating the open and click rates the AI had set as targets before writing anything.
Asked the AI to break his team's own Postgres MCP guards and it found pg_logical_emit_message, which writes to the WAL inside a read-only transaction, leading to a hardened replacement.
He and the AI mapped published datasets and converted them into meshes for Moho depth, basin depth, and two sedimentary basin depths. The work pointed to a tight spot under the South Gate area of LA.
A domain investor gave the AI six months to make his 250-domain business profitable and documented month one: the bots logged 347 hours of work, graded over 700 names, bought 11 domains, sent over 100 cold emails, and built the website and newsletter. Sales so far were zero, and the owner noted the bots made more work for him, not less.
This only partly worked. Worth knowing before you try it.
The AI saw that Caddy was nearly out of memory on his service, checked the traffic, and found bots hitting IP addresses his customers never use. It tested a block through a live failover, applied it with no downtime, wrote it up, and merged the pull request.
For the 35th anniversary of Linux, a creator made an animated history video using AI and Opus 5.5. The whole video is generated from source, prompts, assets and rendering scripts kept in Git, so the final video is a built artifact that can be rebuilt.
Answering a how are you making money thread, he says a piece of business software he used does one thing and does it badly. With the AI’s help he built a piece of software that does the same thing better, with the features he always wanted. It took a lot of bug testing and had many errors at first, but it was done in two weeks. His version costs him $50 a year in server costs instead of $150 a month, saving about $1,750 a year.
He let the AI UltraCode run overnight on their triggered ad server. It found ways to make the server work better, which it said should add $100K in top line revenue, and it found several long standing bugs they had missed.
Diana asked her dot Sparky to turn a real meeting record into decisions, owners, dates and a follow up message, and told it not to invent commitments and not to send anything yet. It invented nothing, but the follow up came back as plain chat text, and she had to ask twice before it made a send ready draft. When she told it to send, it sent at once.
This only partly worked. Worth knowing before you try it.
BananaGroup now runs its Medicare Supplement sales on its own app, with prospects, quotes, enrollment alerts and the sales pipeline in one place, built in a couple of days. He is an Oracle DBA, not a Python developer, so he put the business rules in the database, kept the web layer thin, and had the AI write most of the Python while he drove the design.
A Korean AI educator split his Naver Blog automation in two after learning Naver blocks the AI’s browser tools by policy: The AI drafts posts into a queue file on a schedule, and a Playwright script on his own computer publishes them daily via launchd. Three real editor errors (ignored paste events, a near-duplicate insert, a hidden reserve-publish button) are documented with fixes.