Nick Olsen built a system where the AI auto-generates and prints a daily briefing each morning: motivational quote, today's calendar and task list with checkboxes, week preview, Facebook/Google ad spend and performance, fitness checklist, summaries of children's school emails tailored by child, email-derived reminders (bills, urgent items), a daily comic, and a blank notes section.
A team used an AI 2.5 tool to go through large sets of public comments. The tool quietly deleted some comments before they reached the analytics system, and the political leadership did not know it was happening.
This one went wrong. See what happened before you try it.
Without being asked, Harry McCracken's Dot began flagging incoming messages it judged urgent or important in an inbox flooded with PR pitches. It also resurfaced an email from a freelance author that he had overlooked for weeks and nudged him to respond.
He had the AI collect his will and trust documents and check them against state statutes. The review found missing signatures, an illegal clause, and outdated law references, and he fired his attorney the same day.
Liberty RPF's author tested the AI heavily himself after it launched in Canada, but his wife's onboarding was the telling detail: delighted by the mascot, she renamed it, changed its color, and asked it to review her email inbox daily — her first real agent job.
Three family members, three nationalities, one move to Brazil. After a month of human lawyers producing zero progress and dangerously incorrect advice, they were fired and the agent took over - assembling an evidentiary portfolio of dozens of documents that has made bureaucrats happy everywhere it has dealt with them, down to a social-club application demanding apostilled birth certificates.
He got the AI to build out a structured dataset of all 4,925 vacancies, with job titles, organisation, salary and location. He shared it in a spreadsheet for other people to play with.
His agent sweeps his email and call transcripts looking for work he missed, then drafts the follow up messages and tickets for him. It catches commitments that slipped past him in busy weeks.
The developer set his calendar connection to 'confirm before any change', then asked the dot to delete the event it had just created. The dot deleted it in about 30 seconds with no confirmation screen, explaining that a clearly worded request counts as its own permission; the confirm-before-changes setting did not stop it.
This one went wrong. See what happened before you try it.