Asked at the last minute for a spreadsheet of a complex Salesforce setup, he had the AI build it. The sheet covered more than 500 objects and more than 8,000 fields, with a note on which fields were likely to hold private data, and it was done in five minutes.
He needed his address history for a co-op application and had struggled to dig out leases from a decade or more back. The AI searched more than 20 years of his Gmail and built a spreadsheet listing his addresses back to 2006, with links to the emails behind each date and a flag on the dates that were only a guess.
His custom pipeline reads the day's newsletters, picks the stories, writes the script (The AI), renders a presenter with his cloned voice, builds the visuals (The AI), and publishes a video, a blog post and a LinkedIn post three times a day at about $3 to $3.50 an episode. Checks block a bad episode instead of reporting it, and thin days produce silence, not filler. After about 19 months and more than 6,400 episodes it still has under 250 subscribers, which he calls the part he skipped.
This only partly worked. Worth knowing before you try it.
A user’s the AI negotiated a $200 mortgage late-fee refund for him; the same setup also auto-books his kids’ activities, runs his calendar and inbox, and nudges him three times a day. The refund came from the bot arguing his case with the lender.
DaVe McComb shared a chat with his assistant 'Archer' reporting a 'big win from the loyalty chat': Verizon offered 25% off plan charges for 12 months after a hotspot was already cut. His bill fell from $194.74 to about $161/month.
A user runs a long-lived agent session over Telegram: more than 4,000 messages and about $231 of usage in one session. Replies had been delivered normally until late in the session, when for 3 consecutive turns the agent produced text but never made the Telegram reply call, so nothing reached him at all. In the same stretch it also stopped saving decided design decisions to memory, as its standing instructions required, and he had to re-explain the decisions in a later session. A manual service restart and a log review found the cause.
This one went wrong. See what happened before you try it.
Threw plain the AI at a git repo move with no skills or tools and finished in 20 minutes while multitasking, while a senior spent 6 to 8 weeks building the AI skills for the same job and moved only 5 repos.
Made an AI sysadmin bot with root SSH that runs hourly health checks, Monday 6am updates with rollback, firewall, nginx and site fixes he triggers from his phone.