Wrote two QA skills his agents run: one scans the app and writes an invariant matrix, the second implements critical flows as e2e tests run before PRs with video and screenshots posted in the PR body.
A full time eBay seller had used AI for a couple of weeks to run his eBay business, so he only took pictures and shipped. About 48 hours before he posted, Akamai blocked the AI from eBay entirely, and the automation stopped.
This one went wrong. See what happened before you try it.
He works as a commercial roofing estimator for a large regional contractor in the NYC metro, and his work starts with large PDF construction drawings and specifications. Over eight months he built a system he calls Estimator-OS. Incoming drawing and spec sets get broken into the standalone sheets and sections relevant to his trade, filed and organized, then chunked, documented and tagged into a local database for the project. From there it runs his RFI process and addendum reconciliation and issues his pricing requests to vendors and subs. Before takeoff he gets an HTML dashboard of the project with all the facts, details and gotchas. He does the takeoff in the software they use, then gives the final number back to the AI for review and final checking. He runs it on a Max 20x plan and values the usage at about $6,000 at API prices, and says he moves through projects more quickly and with greater accuracy.
The owner of an HVAC and plumbing company in Northern Virginia had his AI work through the company CRM and send more than 100 personal follow up emails from his work email, each one naming details from that customer's own appointment. Replies came in the same day. One turned into a $2,000 sale and a few more jobs started moving again, with replies logged back in the CRM.
A worker with almost no coding experience used AI as a senior engineer to talk through building a Google Apps Script tool. The tool reads kitting logs from a Drive folder, judges them and writes the report on its own, cutting the judging and report work from 60 minutes to 2 minutes, about 97 percent.
Diana gave the AI Fable 5.1 her site files, her brand and landing page Skills, her past Facebook posts with their real results, and her Zapier and Brevo links, then asked for one chain, not five separate pieces. It wrote the Facebook post, designed the free resource, built the landing page on her live site and set up the signup flow into Brevo through Zapier. The page is live. She made one fix to the page layout. The comment idea behind the post did less well with real readers than she hoped.
This only partly worked. Worth knowing before you try it.
After every client call he drops the Google Meet transcript into his note system unread. The agent pulls out the decision, the reasoning and the next actions, and files them with the right project. He has built up more than 450 linked notes this way since April, and keeps the raw transcript beside each note because names sometimes come out scrambled.
Reporting Anthropic's September 23 engineering post, this analysis describes the AI running a two-week performance sprint from a Slack channel: 150-plus threads, benchmarks built for each bottleneck, and more than 3,000 merged changes with no customer-facing incident. Time to a typeable page at the 75th percentile fell from 3.1 seconds to 0.55, with a human approving every pull request.
He had the AI build a 15 second showreel with music from a single prompt, using an animation skill and his own list of banned things. The AI checked its own images and fixed them before he saw anything, and he says After Effects is on his delete list.