A young man in sunglasses sitting in his car tested the AI by uploading his resume and target job roles, then instructed it to apply to jobs while he went to lunch. Screen recordings showed multiple browser tasks running and a notification confirming an application submitted to 'ioTech Solutions.' The AI asked for information once for the first application, then reused it — resulting in 50 applications submitted while he was idle.
A man was spending 90 minutes a day on email. An AI agent was set up to read, sort and draft replies to every routine message. He now approves the drafts in 8 minutes, saving 82 minutes a day.
Ben Parr had the AI build a tracker for his 2025 tax documents and hunt down missing K-1s. The agent organized the paperwork and chased the missing forms.
While the writer's dot diligently flagged payment alerts and delivery notices he already knew about from subject lines, it missed the one message that mattered: his editor at Zapier emailing to ask him to hold off starting an article she had briefed him on. Had he started the work, the missed flag would have wasted real effort.
This one went wrong. See what happened before you try it.
He asked the AI to screen his unread Instagram threads one morning. It came back with 50 unread, looked at the threads he named across his Primary, General and request folders, and told him what people had sent. The unread count was still 50 afterward, so nothing showed as read for him or for the senders.
His local school division released the raw answers to a touchy redistricting survey as one PDF of more than 3,000 pages, which nobody could realistically read. He used AI to write scripts that pulled the answers out and built a public web page where people can search the responses and filter them by keyword and by school.
Volunteered and built a cartography data pipeline with coding agents for an educator, integrating sources updated every few minutes so new maps appear within about 5 minutes on a low-powered machine.
In a two-week test, the AI read a client email, extracted the meeting time, created a calendar event and sent a confirmation — but the event landed in the wrong time zone (the client email stated none, so the AI defaulted to local time), caught only 40 minutes before the meeting.
This only partly worked. Worth knowing before you try it.
He had the AI work out how the When2Meet scheduling site works and turn it into a skill. Now the AI can read his calendar and fill in the When2Meet availability grid by itself.