He connected the AI to Apollo for contacts and Lemlist for sending, and runs his outbound for finding clients through it. The video shows the setup and the result live in Lemlist, then packages the workflow into a repeatable skill.
His team of AI agents, building a biotech-investor decision-support app, turns the agent chat history into a scripted ElevenLabs-voiced podcast episode after each unit of work so he can follow progress by listening; he caught the team planning a roughly $730 API test run instead of using his AI plan and stopped it.
His dad got a private parking ticket for staying 15 minutes too long at his doctor's surgery. The AI drafted the POPLA appeal, it cited the Equalities Act, and his dad saved £100.
An AI session started verification tests as background processes. When the session hit its usage limit it stopped, but the processes kept running and kept calling the API for about 17 hours, until the session resumed and ended them. Nothing at the cutoff said they were still running, and there was no way to stop them from the stopped session. The test loop had no cap on turns or calls. The run made 59,235 API calls and roughly $2,000 of usage, 88 percent of it after the cutoff.
$2,000at stake
This one went wrong. See what happened before you try it.
A man in Korea runs 17 AI bots for the back office of his distribution company. The bots get statements, customer emails and claim rows ready, then post each one in Slack so a person can approve or cancel it before anything goes out.
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.