A legal librarian at a law firm had to check ten references for a Belgian lawyer working on warranty of liabilities cases. Three references had errors, one of them serious, and the AI Pro with skills and Google AI Overviews found the right reference in a badly protected PDF on revue-banque.fr where another tool pointed to the wrong one, and one more error was fixed using the next year's index of decisions.
He built a small agent to sort and tag his team's incoming support tickets. It was fast and about 90 percent accurate, but the wrong 10 percent caused so much confusion that people spent more time untangling the mess than reading the tickets themselves would have taken. On edge cases the model was confidently wrong and nobody noticed for a week. They scrapped it after a month and went back to tagging by hand.
This one went wrong. See what happened before you try it.
Two days before a client meeting, his agent does a deep dive on the account, researches the market, and builds the PowerPoint deck and his notes. He walks in with the deck already made.
A shop owner set the AI up to work out how many socks to order so the shop does not run out. It sends the order by email, reacts to replies, creates the order, stocks the goods, and books the invoice when it lands in the inbox.
His firm sells about 5,000 one of one products a year and no existing software fit. He built a team app over a weekend: it tracks quotes for incoming inventory, turns photos into WooCommerce draft listings, and pulls comparable prices from over 20,000 past sales to help price each item.
Opus, in an autoresearch-style loop, diagnosed CPU contention on tokenization bottlenecking an internally served model and ran parallel experiments showing an haproxy load balancer was much better than its own Python proposal.
This only partly worked. Worth knowing before you try it.
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.
A solo developer built a women's clothing brand's production WooCommerce store with AI writing most of the code: a custom block theme matched to the client's React prototype, real-time CommerceML sync with their 1C ERP (including patching a stock parser that silently dropped nested per-warehouse counts and cleaning up roughly 1,000 orphaned variations), and zero dollars in platform licenses. Two client revision rounds of about thirty items each cleared in days, and the whole build took weeks instead of months.
He connected the AI to his Shopify stores for Headphones.com and BioCandy and asked it real questions about Headphones.com. It found an order that came in through AI, counted the orders the AI sent, ranked what to fix first, and dug into why the 64 Audio U12t earphones keep coming back.