Before / After · Case Study
A Miami business family runs two connected companies: Anonymous Media, a cinematic video-production house, and AM Automations, a Voice-AI receptionist product. Their current presence is a LeadConnector/GoHighLevel funnel page. The rebuild is a pnpm monorepo with two Next.js 15 apps sharing one backend — @repo/db (Drizzle/Neon), @repo/email, and shared config/UI packages — so a customer captured by either brand lands in the same data layer. The media side carries React Three Fiber 3D marketing surfaces; the automations side sells the Voice-AI receptionist; and consumer SMS opt-in is wired to the central og_life store. Built and ready; deployment to the family's domains is the pending step.
“Two family businesses, one customer pool — the monorepo makes that literal: two faces, one backend.”
Receipts — measured
The story
01 · Problem
A cinematic video-production company and a Voice-AI receptionist product shared a family, a customer pool — and a LeadConnector funnel that flattened both into the same template. Neither brand's actual strength was visible.
02 · Insight
The businesses cross-sell naturally (a media client is an automations prospect), so the data layer should be one thing while the brand surfaces diverge completely. A monorepo with workspace packages is exactly that shape.
03 · Build
pnpm workspace with two Next.js 15 apps over @repo/db (Drizzle/Neon), @repo/email, shared config and UI. R3F/three.js marketing surfaces on the media side; product storytelling for the Voice-AI receptionist on the automations side; og_life SMS opt-in wired for both.
04 · Pending
The legacy GoHighLevel site still answers at anonymousmediallc.com — that's what the before-captures show. After-captures and the afterUrl land here the day the monorepo deploys to the real domains and DNS cuts over.
Architecture
What changed
Each claim ships with concrete evidence — env vars, table names, cadence chips. No marketing fluff.
The media app trades the funnel template for cinematic 3D: React Three Fiber scenes and motion-driven marketing surfaces that demonstrate the company's craft instead of describing it. A production house's site is its first reel — this one finally performs like it.
Both apps consume @repo/db (Drizzle/Neon) and @repo/email from the shared workspace — a lead captured by the video brand is queryable next to an automations customer, and email templates, config, and UI primitives are written once. The family's two businesses stop being data silos.
SMS opt-in routes to the central og_life store — the same multi-brand consent infrastructure the rest of the portfolio rides — so the family owns its audience with TCPA-clean consent rows from day one, without standing up its own SMS stack.