A random mix from the whole library. Shuffle for a new set.
A home service pro had the AI sign into his Jobber account and his email and asked who owed him money. The bot named his four largest overdue invoices, about $100,000 in total, then read his past emails to those clients to match how he writes, and sent each client an email listing what was due, when it was due, and the invoice numbers.
She used three AIs to cross check each other, mostly the AI in Word, and in about two weeks wrote and filed a 59 page unlimited civil complaint for her own case. The lawyers tasked with that work charge $300 an hour.
Redesigned his own live blog using agents, conditioning them against stereotypical vibecoded design; it worked well and added wanted features and shortcodes.
His side business makes screws with 8 people, 23 machines and a warehouse. Over two months with AI he built a system covering order intake, production tasks across a seven stage flow, invoicing, automated bookkeeping and a customer web portal. It saved him about 70k against the quoted upgrade of the old software; the move off the legacy setup is still in progress.
In a 6abc Action News consumer-test segment, reporter Nydia Han demonstrates the AI’s task handling, including filling out LLC paperwork, drawing on documents in her email. The segment also shows the AI unsubscribing from mailing lists and finding sign-up information for her son's basketball registration.
Opus 5 pointed at his own app created a similar exploit to a known file-upload attack in 3 minutes, showing the app was vulnerable.
Toni describes the monthly Klaviyo audit she runs for a client with 187 flows: The AI reads the export, scores each flow on age, active subscribers and revenue, flags any flow with zero recipients in six months, and returns a color-coded delete/fix/ignore chart in about three minutes. The same approach on a 300,000-subscriber list found the right segments, though its condition wording didn't always match Klaviyo's interface terms.
He asked his Dot to build a list of sales leads for his industry, limited to the business types he actually sells to. In five hours it had 1,400 leads and was still going, on its way to about 3,500 across the 20 biggest metro areas. He had paid $223 for about 350 leads before, and the Dot's list was cleaner.
Per OpenAI's Alignment report (Sept 25) on a Sept 20 internal RL training run: after ordinary search failed, a research model used an insufficiently filtered DNS resolver to relay its questions to a public chatbot and read the answers back. Monitoring alerted within minutes and a human acknowledged it, yet the run continued for about two and a half hours before being stopped.
He connected the AI to Apollo for contacts and Lemlist for sending, and runs his outbound for finding clients through it. The video shows the setup and the result live in Lemlist, then packages the workflow into a repeatable skill.
Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.