The Slide Factory review cites a Reddit user who ran a document review covering hundreds of PDFs on a Dot over an extended period, asking unrelated questions and starting other tasks meanwhile. The Dot reportedly kept the project's state, worked in parallel across its cloud computer and a connected Linux machine, and continued allowed work when one step needed approval.
A SimplePost user hit an error while the owner was on vacation with his family. The AI checked the logs, found the issue, fixed it, and drafted the explanation email in Gmail, and the owner reviewed and approved each step.
For a few weeks he has had the AI take over his cursor, open Clip Studio, and put the words on his comics. He still makes small fixes himself, and it saves him real time on the dull part of the work.
He has about nine apps in the App Store and Play Store, and he is quick to say they are not one prompt builds: most of them he has hand guided and polished for months or years. He has agents reading his RevenueCat data, Stripe, GA4 analytics and Sentry logs for him. Alongside the apps he is building LocaleShot, for making multilingual store screenshots, and InfluTo, for managing influencers and automatic payouts, and he plans to shape both into platforms other people can use.
His wife was migrating almost 400 employees across two companies to a new payroll system and had to confirm every bank detail had carried over, two days before payday. The AI wrote a local script instead of uploading personal data, matched employee codes and bank codes across 18 PDFs in different formats, and produced summary spreadsheets with the checks. The script can be rerun for the next migration.
Family-law trainer Stephen Smith built four working tools with AI, one conversation each: a settlement schedule that shows a client how much of an $8,000,000 award is actually spendable and when, a two-sided case chronology with exhibit links, a parenting-time calculator that counts overnights and percentages, and a case-path timeline clients get at the first meeting. The examples use training data, and he warns that the AI wrote the math, so every number must be checked before a client relies on it.
A solo event staffing agency owner runs his back office on the AI: email, vendor messages, pricing, his applicant database and calendar. It is a big reason he can operate at this size, but the agent states things it never checked: it told him a vendor had gone silent when she had answered that morning, said an email was staged when no draft existed, and called his suppliers brand partner candidates, a mix up that cost him two days of planning around an opportunity that was not real. His fix is a state file where every fact is tagged confirmed, stated, assumed or open; errors fell from several a week to a few a month.
This only partly worked. Worth knowing before you try it.
A three-person flipping operation runs on a custom app steered through AI over MCP: it identifies what is actually inside vaguely described government surplus lots by hunting service tags in the auction's spreadsheets and model numbers in its photos, values each lot against sold comps, and overlays a buy/watch/pass call with a max bid on GovDeals as they browse. It also ranks repairs by ROI, turns SD-card photos into listing pages that a human approves, and prints a pack-in sheet with QR ads for their other listings when something sells.
He set up the AI cron jobs that run weekly SEO and analytics checks on all of his sites and apps. He says the checks are working well and keep him consistent.
AI help unblocked his language compiler at codegen, produced a faster and better code generator than he could, and made the type checker about 5 times faster.
He asked the AI to make a marketing video for his app, Astro Editor. It read the website and repo, rebuilt the app's look as a web page, captured 3,600 frames into an MP4 and generated the soundtrack in code.
In a long-running verification project, the model recommended buying a reference textbook, about $60 to $100, to fill a gap. The project record already contained a finding, written two weeks earlier, that the book could not answer the question that mattered. The model had even restated that disqualifying fact two paragraphs earlier in the same document before recommending the purchase anyway. It was one of four times in a single session that the model asserted or recommended without checking the record sitting in its own working folder. The user had already spent $100 that day on reference material.
This one went wrong. See what happened before you try it.
A consulting-practice owner had 166 AI agents across seven workflows read his real system files and build a 4.5-minute animated walkthrough of his twelve-department operation on October 15, finishing in 4 hours 21 minutes. Fact-check agents traced every on-screen claim to a source file and made 19 fixes before the video was published the same day.
He fed a career vault tool 21 resumes from the last 10 years plus weekly journal entries about projects, wins and goals. Every morning the AI pulls jobs that match his profile, tailors his resume per posting from that real history, generates the PDF, and fills out the whole application, then stops and waits for his review before anything goes out. Review takes him about 30 seconds per application, against 4 to 6 minutes each when he did it with AI. The post also promotes his own paid tool, so it is marked promotional.
Let Fable work overnight on llama.cpp, producing 19 patches and up to 10x speedup for multi-user long-context use, then ran that code for 3 weeks with no crash and built a 5-agent system on it.
The AI rebuilt his website, his point of sale, and his online storefront. He no longer pays Shopify $40 a month, his site works better, and payments run through Square.
Last week his Dot published his article to his own site, DEV and Medium in one go. This week the same job failed at several steps, the cloud connection could not write to his blog repo and the file transfer to his laptop failed, so he had to step in again and again and told it to start over on his own computer.
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 spent about an hour getting an LLM to work out the fillable admin PDF he had been sent, then auto fill four copies from his Markdown notes. It took longer than filling them in by hand, but he would rather do it this way.
He asked his AI to edit an entire video and it did the work, from picking the takes to lowering the music in the quiet parts. The video is the third in his series about building his toolstack with an agent.
After the cancellation mess, Curtis wrote a one-page scorecard for the role (mission, five measurable first-year outcomes, six competencies), pasted it into the prompt and had the AI map each candidate's track record to each outcome with evidence from the résumé. With a human making every cut and applications closed before booking, the process ended in a Director of Ecommerce hire who has already optimized the company's Amazon listings and helped launch a product — and a declined candidate was later hired as a TikTok consultant.
The AI wrote a complete, well-structured HTML landing page from the tester's brief and her own site as a style reference, and its HTML was her favourite of four agents tested. But Spark could not open the page in an interactive preview, so every visual check cost an export and a context switch, stretching a fifteen-minute job to about an hour.
This only partly worked. Worth knowing before you try it.
A coffee roasting company owner used to download the raw order list every day and clean it up in a spreadsheet by hand. The AI wrote scripts that prepare the data, so he wakes to the raw orders ready and gets the finished work table with one click. It also speaks a notice to his staff when a top priority order comes in.
The AI audited the creator's inbox, found 277 brand-collaboration emails that had never been answered, drafted and sent replies, and continued the negotiations.
A lecturer at KU Leuven had AI agents build RaftViz, an interactive tool that lets his students step through the Raft consensus algorithm next to the exact lecture note lines behind each step. He wrote none of the roughly 6,000 lines himself, the tool is published for anyone to use, and building it exposed a real bug in the lecture notes.
He asked the AI to set up a new series of 1 to 1 meetings with his direct reports. The AI created sixteen calendar invites, all to the same team member.
This one went wrong. See what happened before you try it.
His company paid $180 a month for five seats on SmartSuite, the tool holding their documents and HR files. He built a replacement with AI that fits their exact needs, can grow to thousands of users, and will cost less than $30 a month to run.
He updated kim-olsen.com with AI in under an hour of editing, work he says used to need a developer and a budget. The AI also edited the launch video, made the subtitles, and did all the visual and sound effects.