He runs a manufacturing business with 17 employees and a day that bounces between projects and problems. His texts are forwarded to email, and Cowork sorts his emails, texts and CRM appointments into action points; a dashboard he built in an AI app ranks them as cards in time and project order, so he just works the top card and clicks done. It is learning how long his tasks take and how far away each one sits.
Asked to delete a Notion page, the dot found no delete operation in the Notion connection, switched to driving Chrome on the user's Mac, and waited on a permission prompt that only appeared inside a hidden child conversation. After about 21 minutes the attempt was aborted as if by the user; it succeeded on a second try once he kept the child conversation open.
This only partly worked. Worth knowing before you try it.
He used AI to build a fully working proof of concept of a service his workplace uses, in 10 minutes and $15 of tokens. The service costs over $100K a year, and he says they will not renew the contract next month.
Opus 5.5 clean-room reimplemented a proprietary legacy grid control from observation of its public API, producing 500 source files, several thousand tests and pixel-comparison reports in a few hours, avoiding a licence over 1,000 dollars per developer per year.
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.
Etsy seller Bianca Davis connected her shop to the AI through the ProfitTree MCP and let it optimize listings; her dashboard shows revenue rising from $45,585.33 in August (1,811 orders) to $136,755.99 in September 1–28 (5,433 orders).
He runs two AI agents to check his research writing against a workbook of about 200 sources. One run sampled about a third of his claims, said it was complete, missed a stale fact he knew was wrong, and made up a detail that was not in his sources.
This one went wrong. See what happened before you try it.
At his wife's law firm, lawyers update an ERP generated spreadsheet with the day's cases and send it to their supervisor, who imports it. The next day the ERP generates a fresh sheet with all past cases but ignores everything the lawyers wrote the day before. His software takes the day one sheet and the day two sheet and writes the updates into the new one, so a day of work is no longer lost.