Wendell Yu describes promoting the AI to an AI CEO role: it coordinates the AI and the AI, assigns tasks to them automatically, and saves him tokens. It is the second of five first-hand the AI cases in his video.
He is a photographer. The overnight workflow his virtual assistant used to run now runs on its own while he sleeps, and the photos are ready before sunrise. Today he let the virtual assistant go.
The AI compiles his travel highlight videos on his own computer using scripts and tools. It even built him a small clip review app so he can pick which photos to include, and it puts all the scenes in order by itself.
He needed a foreign language voiceover on a video presentation at work. He spent several hours with AI building a process he could trust, then rendered each paragraph as speech and built it into a new audio track for the video.
A developer's build task staged a folder with a symlink to /Applications and cleared it on each rebuild. The delete followed the link and removed every app he had installed by hand, five rebuilds in a row, with no trip to the Trash.
This one went wrong. See what happened before you try it.
He used to pay a designer $1,000 for app store screenshots, and they took two weeks. Now he makes them himself with AI in under two minutes, keeping the same style on every screen and leaving his real app screens untouched.
A developer new to making videos drops raw files into a folder and the AI, connected to DaVinci Resolve through an MCP server, builds complete edited YouTube videos: transcribing, picking cuts, graphics and music, using a setup it built up over his last three videos. His latest video took 57 minutes, with AI showing him take options to pick from.
A Korean creator set up the AI to find possible clients on its own. Every Monday at 7 in the morning it does the research, finds each contact person's job title and work email, and puts the results in a Google Sheets spreadsheet.
Australian tiling business The Grout Guy built a photo-analyzing Agentforce agent that cut quote turnaround from days to minutes, one of Salesforce's 2026 Customer Success Award winners.
During a migration, a written plan in the session said nothing in the legacy repo gets touched. The plan was re-shown in full mid-session. When the user later asked for a follow-up change, the AI searched the folder it had been working in most recently, which was that repo, found a file that looked right, and edited it there. The user caught it, and the edit was reverted and redone in the correct repo.
This one went wrong. See what happened before you try it.