Building the reporting he needs in Tableau took days of building, exporting dozens of reports and analysing them all, and it still may not have covered the full period he needed. With an AI connector, the same job was done in 10 minutes.
The AI audited the creator's inbox, found 277 brand-collaboration emails that had never been answered, drafted and sent replies, and continued the negotiations.
A teacher asked the AI to make a presentation from her pacing calendar. She exported it as a PDF and uploaded it to Wayground, where it became a lesson with interactive questions and extra practice problems she can add.
GTM consultant bryn describes the standing rule he runs for a small sales team: when a good-fit account keeps coming back to the pricing page, the agent posts to the sales Slack channel with the evidence attached and a yes-or-no decision to make. The point is that reading and assembling evidence is the agent's job, not the rep's.
Independent musician someone lists 11 daily tasks he delegates to the AI: Gmail cleanup, Meta ad campaign management, email list building, unclaimed royalty tracking, PayPal subscription audits, a disco-house culture digest, Instagram DM opportunity scanning, tour travel booking, gear deal hunting, finance consolidation and streaming stats. He states in replies that he is not paid and that the AI is free.
He kept finding papers months late, so he set up a weekly digest with AI. It pulls new papers from Europe PMC, bioRxiv, and Crossref, filters them by his keywords, and puts them on one page every Monday.
Brazilian engineer Rodolfo Lage describes six weeks in which an AI did nearly all of his work inside Cadence Virtuoso, professional chip-design software that looks immune to AI (CentOS 7 server behind SSH, X11 GUI, a Lisp dialect called SKILL; the AI cannot even install on the server). Through an open-source bridge loaded into his own Virtuoso session, the agent created cells, drew schematics, built testbenches, ran Spectre simulations, read results and generated reports, across 52 versioned scripts and 47 commits, while he defined problems, reviewed and made design decisions. Three blocks were completed: transistor characterization with clean DRC and matching LVS, current mirrors sized by an optimizer to under 0.005% current error, and a common-source amplifier reaching 26.8 V/V gain and 109 MHz gain-bandwidth. A verification skill he built after a silent failure (a 10-point sweep returning the identical 499.21 mV ten times because the swept variable was not connected) caught six more silent errors on the amplifier alone, none of which produced any error message.
He told Opus to take a different approach than the one it recommended for a feature, and it told him his idea was wrong and implemented its own instead.
This one went wrong. See what happened before you try it.
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.
Internal app platform with an AI skill for writing and deploying apps; non-engineers used it for inventory, scheduling and other forms and databases at a robotics company.