A random mix from the whole library. Shuffle for a new set.
Luke Davies runs Davies Construction with a team of the AI set up like a company org chart, with bots for estimating, admin, books, sales and project work. Day to day the bots sort the inbox and draft replies, pull tasks out of meeting notes into a list a person approves, and create and update the job tasks in ClickUp as work moves on the Wunderbuild board.
Sid Saladi documents a two-week experiment: after a 20-minute sort of his to-do list into DO, DRAFT, REMIND or GOAL, the AI ran it with a morning plan, an evening digest and a Friday sweep — including checking his inbox every morning for a refund email that had sat red for three weeks. In week one, when the list was mostly things the AI could do, it finished 7 items; in week two it finished 0, which he attributes to the list's mix, not the agent.
To mark the start of the semester, he asked the AI to build a macOS widget. It counts down how many weeks are left until the last class, and how many of those weeks are real teaching weeks.
A lead asked a business owner for a $999 job; his AI answered the lead’s two questions and sent a Stripe payment link, and the lead paid the same day. Speed-to-lead, handled end to end by the bot.
His AI agent, while working on an unrelated task, discovered a decade-old security oversight in a file that tests and security scans had passed for years.
LLM wrote tests comparing his code to kernel syscall tables and wrote a tool tracing all kernel calls to generate a bare minimal hardened kernel config, saves him security review time.
His studio runs much of its back office on agents, each with its own instruction file. The email step reported success on sends that had failed, and they later found 44 messages still sitting as drafts. Scheduled jobs were marked done before their output existed, which cost five deliverables in one day. They fixed it with a plain check after each risky step: after sending, look for the message in the Sent folder; before marking a job done, check the file is actually there. Now only a failed check needs a person's eyes.
He set up an AI for his WP Beacon project to check WordPress plugins every day. After two weeks of daily checks it pinged him about malware in the InstaWP Connect plugin, and wordpress.org closed the listing that afternoon and restored it the next morning.
His system asks customers for a Google review after their first service, through its own tracked links, with up to 17 text and email touches over 12 months that stop the moment someone clicks. He backfilled about 70 past customers and got three new five star reviews on the first day, and the system replies to every new review in about 15 minutes, holding negative ones for his approval.
Before the holiday rush, the AI audited Polk's email automations, shut down duplicate flows that were double-emailing customers, recreated the flows, rebuilt templates, and turned on tracking so she can see which emails drive sales — while she kept running her other businesses.
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.