
Sign up to save your podcasts
Or


When AI stalls after the pilot, the instinct is to blame the tool. CPA-turned-AI-builder Alyssa Clarcq has a blunter diagnosis: if your process isn’t documented, AI can’t follow it, just like an intern you never properly trained.
Host Jess Lampe of Launch Consulting talks with Alyssa about her path from Big Four external audit to vibe-coding an “AI-native company” with no programming background, guided largely by software developers in her TikTok comments. She explains how her system works: a second brain holding all her context, a central task tracker, specialized “desks” for finance, marketing, and content, and agent loops for prep, review, and QA. She also covers why governance and guardrails matter when AI can hallucinate on a regular basis.
They get into the realities: calculating a net savings of about 10 hours a week, building a “babysitter” chat to manage parallel agents, the surprising cognitive load of constant decision-making, and rising token costs that have her weighing local models. Alyssa closes with advice for organizations: treat AI adoption as upskilling rather than replacement, invest in real training, and start with your internal audit team, the people who already understand your processes end to end.
Follow Alyssa Clarcq at:
https://www.tiktok.com/@alyssa.with.ai
https://www.linkedin.com/in/alyssa-clarcq-cpa
https://alyssaclarcq.com
https://www.skool.com/ai-office-hours-with-alyssa-4640/about
Everyone was promised that AI would hand back their time — so why does it feel like you're babysitting four terminals, clicking "yes, allow this" one prompt at a time, and re-reading long specs just to check whether the model did what you asked?
In this episode of Why Isn't This AI Thing Working, Jess Lampe talks with Jim and Alysha Rosser, co-founders of Entry Studios and the team behind Grove. Their take on why AI stalls after the pilot: it's a trust problem. Agents skip instructions, invent their own commands, and declare victory before the work is done — quietly shifting the cognitive load onto whoever reviews the output next.
Grove is their answer, and it started as a tool they built to solve their own frustration. Jim and Alysha make the case for wrapping AI in old-school determinism: task lists with hard proof requirements, permission "boundaries" that redirect an agent instead of just blocking it, and executive summaries that show the receipts on every session. The result is a two-person team that queues work overnight and walks into roughly ten reviewable PRs each morning — about 900 merged since July. Along the way: cognitive load, "making determinism cool again," designing upfront, and why living in the chat window all day means you're doing it wrong.
In this episode of Why Isn't This AI Thing Working?, host Jess Lampe sits down with Alex Kozlowski, Director of Software Engineering at Launch Consulting, to cut through the jargon and explain how AI systems actually work.
Alex and Jess demystify the vocabulary everyone uses but few define: what a large language model really is, why LLMs are probabilistic (and why that makes hallucinations inevitable), and what separates an LLM from an "agent" and an emerging "harness" like Claude. Using plain-language analogies, they explain how tool-calling loops create the emergent behavior people find so impressive — and where these systems predictably go wrong.
They also tackle adoption reality: why teams with strong DORA metrics get the biggest gains, and why most AI proofs-of-concept never reach production.
In this episode:
In this episode:
In this episode:
In this episode:
In this episode:
Learn more about It Writes Itself at itwritesitself.ai.
See Mike's magic at hellomagicmike.com.
From the publisher's feed