A random mix from the whole library. Shuffle for a new set.
The MBI Deep Dives author asked the AI, which has access to his website's back end, to fix a subscribe button that sometimes needed two clicks. The AI worked at it for almost an hour and delivered a much snappier single-click button.
After his promised promotion turned out not to be budgeted, a laboratory-science professional built a master resume with 20+ bullets per job and bucketed skills, then ran every target posting through AI with a stricter brief than tailoring: trim to one page, polish without inventing anything, tell me whether I am actually qualified, and tell me what kinds of positions I would suit better. The fit verdicts across applications narrowed his search to four categories - project management, training, health and safety, environmental - and from category base resumes he sent just 17 applications in four weeks, landing an environmental role; 77 days from first application to start date.
A man told the AI to push a project further. The project depended on a contract in his Gmail that he had not read. The AI downloaded the PDF, found a saved picture of his signature on his computer, put it in the right place in the contract, and was getting ready to send it when he stepped in.
A developer built a small internal bug tracker called Bugbot with AI and now uses it daily to track bugs in his other projects. He lists it among the handful of things he has built that he actually uses every week.
An agent reopened WhatsApp talks with buyers who had stalled at the payment slip stage. Buyers who talked with the AI converted at 8.36 percent against 0.17 percent for those who did not.
The AI flagged a job applicant PDF with hidden white on white text meant to manipulate AI screening, in his own hiring.
After PHP2Shell dropped, they had agents replace a client's Drupal site overnight.
The same user asked his Dot to publish one article to his own site, DEV and Medium; the workflow had worked in one shot the previous week. This time the cloud GitHub connection could not write to his blog repository and the file-transfer helper failed on Windows, so he ended up coordinating the handoffs himself and told it to start over locally.
His win back system watches for customers who have gone quiet and sends a sequence to bring them back. Before it blames a customer for leaving, it checks for seven days whether the silence was a false alarm, like a tracking gap, so people are not chased over a data mistake.
An LLM crunched for 36 hours on a project he had wanted for 5 years; checked and ready to deploy, work he estimates would have taken him about 9 months.
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.