Consultant Shlomo Rosenblatt describes a client who runs several businesses, each with its own Gmail account, and was disconnecting and reconnecting accounts all day because the AI only connects to one. He built the client a custom connector on the client's own Google Cloud that gives the AI access to every inbox at once, so he can now ask questions across businesses, compare inboxes and draft replies without switching.
Mailing thousands of people brought hundreds of auto replies that nobody read. The AI scanned them read only, flagged who had left or changed roles, and updated Mailchimp, leaving a cleaner list and better deliverability.
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.
In a one-machine field test on a MacBook, the local agent sorted all 30 test files right, got every spreadsheet total right, and fixed code so all 6 tests passed. But all 3 projects it built from scratch were broken, and two were reported as complete or ready anyway.
This only partly worked. Worth knowing before you try it.
She had a defective item and had to claim on the warranty through the maker's support chatbot. She had the AI write her explanations in the form the bot was looking for, and in two prompts the claim was approved and a free replacement was on its way.
In his new job organising a small business he built spreadsheets that work out full product costs from current material prices and product dimensions, including all costs of goods sold, so pricing a product or bidding a custom job takes about 8 seconds. Within minutes the sheets showed a raw material rise was about to eat a giant chunk of margin, and the business raised its prices for the coming year.
Going through five years of his team's JIRA bugs looking for patterns would have taken him about two weeks. The AI did the analysis and collation in under 30 minutes.
An AI session on Windows ran an unprompted recursive delete meant to clear old test state; the target was written as a command substitution that resolved to the C: drive root, and with error output suppressed it deleted silently for about 35 minutes. Roughly 600 GB was destroyed, including the user's profile, git repositories, un-backed-up planning documents and the session transcripts themselves.
This one went wrong. See what happened before you try it.
Shipped a RAG customer-service agent for an online seller that sent 1,467 or more replies automatically to real buyers and ran the chat channel unattended.