Diana asked for a brief about her business, not businesses in general. The AI produced a detailed, relevant brief needing little editing, built partly from context across her Meta business presence — the first moment the test felt differentiated rather than merely competent.
Diana asked her dot Sparky to turn a real meeting record into decisions, owners, dates and a follow up message, and told it not to invent commitments and not to send anything yet. It invented nothing, but the follow up came back as plain chat text, and she had to ask twice before it made a send ready draft. When she told it to send, it sent at once.
This only partly worked. Worth knowing before you try it.
She keeps the current state of her projects in Notion and works in an AI app. In a live test she opens a fresh chat, has the AI read the Notion page for the video she is making, pick up where she left off, and update the page without duplicating what is already there.
His Gmail Promotions tab held 7,102 promo emails built up over years of online shopping. He asked the AI to clear them. It asked him to confirm before doing anything destructive, moved all 7,102 to Trash in one go, then ran a follow-up check to verify zero promos were left outside Trash. The whole job took about a minute of his time, and trashed mail stays recoverable for 30 days.
He gave the AI 45 podcast files, each about an hour and a half long. The AI found where the music ended and the talk started, split the files there, matched the singers by voice, and built a small HTML checker for the matches it was not sure about.
An equipment store's EZContact agent handled a Facebook-ad buyer's questions, guided the product choice, and received the buyer's payment receipt inside the chat, as narrated by the store owner to the vendor. The owner then shipped the equipment himself; the agent never confirmed the money itself.
Someone cold-pitched ~50 local businesses with websites the AI built; 2 bought. The website-flipping idea came from the AI itself; he just made the calls.
After about three months building code on the AI, the reviewer found the code corrupt while charges kept hitting and credits were deducted even as he complained to support bots. After he confirmed he was moving away and his account was in credit, the AI still took cash from his account. Roughly 200 support emails produced no fix.
This one went wrong. See what happened before you try it.
He shipped a ColorBliss feature a customer had asked for and planned to email the customer himself later. When he opened his help desk, his automated support agent had already seen the reopened ticket, checked Linear, confirmed the feature had shipped, and sent the customer a note.
Built with AI Python tooling that indexes a slow data corpus and converts it to Parquet queryable with DuckDB, dramatically improving turnaround on one-off analysis tasks.