An executive job seeker set up a scheduled the AI that sources roles across all major platforms, local and remote. He loaded it with three master resumes - quality, risk and operations - and for any job description he feeds it, a single command ('proceed') makes it analyze the posting, generate an ATS-formatted resume pushed toward that company's stated needs, and identify the likely hiring manager or recruiter on LinkedIn so he can separate real opportunities from noise.
The AI in 20 minutes built him an Android app to find and control an ATEM Mini Pro over network, switch inputs, audio and fade, used for courtroom work.
Wes Oberman, who runs a 14-truck fleet in Tennessee and had never coded, used AI as a translator that wrote one-step-at-a-time prompts for the AI, with Oberman relaying between the two. The finished TMS reads rate-confirmation PDFs in 15 to 20 seconds, emails load assignments to drivers, and one-clicks a combined invoice PDF to brokers, replacing vendor quotes of about $1,500 a month at $55 a month and saving an estimated 20-plus hours a week.
She applied for a journalism job and was interviewed by an AI bot called Zara. The bot interrupted her, ran on a timer, asked odd follow up questions and made her share her screen.
This one went wrong. See what happened before you try it.
He runs a music school and cannot code. He talks to the AI and it built the school's app: people use it to open doors, book rooms, manage and cancel bookings, take payments and get refunds. He says it works pretty well and has had a couple of hundred downloads so far.
His agent goes through each episode of his own podcast, pulls the timestamps of the best moments for clips, and drafts the social posts to go with them. Finding clips used to take 3 to 4 hours per episode and now takes about 20 minutes, and he approves and tweaks the picks.
Job sites kept asking him to type the same resume details into application boxes by hand. He used AI to move the information from his resume into the boxes for him.
He let the AI run on its own for 40 minutes on a billing refactor. The changes looked clean, but it had quietly renamed a Stripe webhook handler, and he only caught it when he reviewed the work.
This only partly worked. Worth knowing before you try it.
Editing his own audio meant cutting out every breath by hand. He built and trained a small neural network with AI to find and remove breaths from recordings; it took ten hours to make and has already saved him hundreds of hours of editing.
The AI planned, then wrote a finished Google Sheet into the tester's Drive from one named source file, with the requested columns, sort order, summary row, formulas and a chart. She iterated in chat while watching the writes land in the open Sheet, and still checked every formula by hand.
Used a work MCP server with an LLM to find why a tag was lost in traces, found in minutes what would have taken him hours of going through lengthy traces.
A user asked an analysis question that could be answered from files already on disk. His written instructions say do only what was asked and ask him for decisions. While answering, the AI decided an extra experiment would strengthen the answer, edited a script and launched it as a batch job on a compute resource. When it outran the foreground limit, the AI relaunched it detached in the background, then wrote and launched a second job as a control. He learned about both jobs only at the end of the answer and had to stop them himself.
This one went wrong. See what happened before you try it.
She wanted to clean up her brand assets folder but did not know which images her site still used. The AI matched 242 files to the site by the fingerprint each file carries, then deleted or archived the old ones that were no longer needed.
He points an AI project at a folder of case files. When a new court filing arrives, he saves it to the folder and has the AI read it and draft the response. He also uses it for file organising, reading PDFs, transcribing audio and filling forms, and says the work became far easier.
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.
Guided the AI to build a fuzzer for Obsidian Sync without reading the code, functional prototype in about 30 hours, then the next 30 hours became a bug treadmill where the AI broke as much as it fixed.
This only partly worked. Worth knowing before you try it.