Here's exactly how I built it — and what surprised me. The problem is not running meetings. It's everything that happens after the call ends. Action items live in someone's head. Follow-ups never get sent. The same things get discussed next week. So I built a fix. Here's the stack: Step 1 — Join the call Used Recall.ai to bot-join meetings automatically. It records, transcribes in real time, and hands you clean text. No manual recording. No copy-pasting transcripts. Step 2 — Extract action items Fed the transcript to Claude with a structured prompt. Told it to extract: the action item, the owner, and the deadline. Returns clean JSON every time. No hallucinations on names if your transcript quality is good. Step 3 — Push to Slack Slack's API takes 20 lines of code. Action items go to a dedicated channel, tagged to the right person, immediately after the call ends. Step 4 — Auto follow-up Built a simple cron job. 24 hours before a deadline, it pings the owner in Slack. No manager needed. No nagging. Just a quiet reminder that actually works. Total build time: one weekend. Total cost to run: under $30/month. Lines of code: less than you think. This is what vibe coding looks like in 2026. You don't need a full engineering team to validate an idea. You need a sharp problem, the right APIs, and a weekend. What would you build if you knew it only took 2 days?