One Database Won't Fix Your Fragmented Stack

When a small landscaping practice bolts WhatsApp, a meeting assistant, and a CRM onto its existing backend, the instinct is to consolidate everything into one database. That instinct is wrong. This episode unpacks the distinction between a system of record and a source of truth, then walks through a concrete build order — WhatsApp Business Platform first, transcription second, CRM third — showing why every field needs exactly one declared owner and why copies are fine as long as you know who decides. Along the way: the new per-phone-number billing rules, the twenty-four-hour customer service window, why templates are copy that costs money and requires permission, and how to turn meeting transcripts into structured data instead of a folder of dead files. Key sources: • Meta, updated 2026-07-01 — https://developers.facebook.com/docs/whatsapp/pricing/updates-to-pricing/ • Meta, conversation-based pricing (deprecated) — https://developers.facebook.com/docs/whatsapp/pricing/ • Meta opt-in requirements — https://developers.facebook.com/docs/whatsapp/overview/getting-opt-in/ Episode 5908 — myweirdprompts.com/n/5908 (permanent short link: myweirdprompts.com/884398)