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.
His company Feature Upvote already does regular pen tests and monthly backup restore checks. He pointed the AI at their source code for a security review, and it found some serious problems.
A developer says he now just tells his AI to find the bugs overnight and fix them by morning. The AI works on its own computer, cloning the repo and installing the toolchain, and his Puppeteer script clicks approve so pull requests are waiting for his review.
At the same accounting firm, staff batch upload client bills and the agent reads each one, decides whether it belongs in payables, receivables, or the cash book, and posts it into AutoCount after a person reviews and amends the lines. The firm has run the setup in production for three months.
He carries a small voice recorder. When he records a thought, the audio goes to his agent Rick as a message, and Rick carries out whatever the note asks, which he says beats the reminder apps and note widgets he tried before.
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.
A local LLM helped him build a sub-1500-line memory-safe baremetal Rust init system with a test suite in about a week, work that would have taken months by hand.
He asked the AI to make a PDF text searchable because his employer pays for full the AI but not the paid Adobe with OCR. After 10 minutes of processing it gave him a new PDF with the same number of pages, all completely blank and with no hidden text.
This one went wrong. See what happened before you try it.
Set up the Figma MCP with AI to match web pages exactly to Figma designs across about 40 pages, where feeding screenshots had done poorly, and it did what he needed.
He used Glyphhanger to cut a font down from 36KB to 16KB, keeping only Latin and dropping the variable axis. Then he let the AI try, and it redrew the glyphs and got the font down to 6KB.
Creator Alex Finn recounts on a podcast episode that he gave an AI access to his business inbox and told it to answer and negotiate with legitimate companies. Within about four hours it had researched market rates and closed its first sponsorship deal, worth $10,000.
Founder Divya Gugnani shows screen recordings of the AI connected to her Instagram: it audited her account (reporting 38% of Reels working and 22% of Carousels not) and drafted replies to 47 new DMs. The same demo shows Gmail reply drafts held for her approval and a school permission slip auto-completed from email.
A user asked the AI to create a new sprint on a shared GitHub Projects board. The AI replaced the board's whole sprint list with only the new one, deleting 12 completed sprints and the sprint history of about 450 items, and the safety filter then blocked the call that would have put them back.
This one went wrong. See what happened before you try it.
He and the AI analysed 144 of his CoWork sessions and 14,640 turns, found a turn past turn 141 costs 2.1x an early turn, and stopped batching sessions as a result.
The Life Force Design owner named her AI 'Flow' and gave it a real creative-business job (Etsy shop LifeforceDesign): over ~48 hours it helped organize ideas, plan content, create working systems, review decisions and prepare material for publication — intention to execution to review to publication.
An electrical engineer in Germany built his own CRM, invoicing, protocol generation and warehouse tool with AI over more than 120 rounds of changes, for under €100. He says the same build would have cost six figures a decade ago, plus €5,000 to €8,000 a year to use, and the tool now runs the way he wants on his own computer.
An engineer had just had the AI reapply local, uncommitted code changes. Separately, a GitHub Actions run he had triggered against production was mid-flight, in the middle of creating a replication subscription on a live Postgres server. He said undo the work it just started, meaning the local edits. The AI read it as the production run and cancelled it mid-statement, leaving whatever partial state the kill created. The local edits were not touched until he clarified.
This one went wrong. See what happened before you try it.
A scheduled the AI task runs at noon every day, reads his Nagios and BuildBot status, and messages a colleague only the items that look suspect, skipping young unknown states and anything already acknowledged. It has run since May, and once skipped four days when his laptop was closed, which he only noticed 26 days later.