Before / After · Case Study
A Miami business family runs two connected companies — a cinematic video-production house and an AI phone-receptionist product — and both were squeezed into a single rented funnel page that made them look identical. Each brand now gets its own site with its own personality, but a customer captured by either one lands in the same shared customer list, so the family can cross-sell the way they already do in real life. Built and ready; it goes live the day their web addresses point over.
“Two family businesses, one customer pool — the monorepo makes that literal: two faces, one backend.”
At a glance
Design
The video-production site trades stock funnel sections for interactive 3D scenes that move as you explore — the site itself demonstrates the company's craft instead of describing it.
Theme & color
The two brands diverge completely on the surface — a dark, cinematic, motion-driven feel for the media house, a clean product-story look for the AI receptionist — while sharing everything underneath.
Email templates are written once in a shared package and used by both brands, so the family maintains one set of messages instead of two drifting copies.
Customer notifications
Text-message opt-in rides the same proven consent system used across our other builds, so the family owns its audience with clean, legally recorded consent from the first signup.
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.
Both businesses lived behind a single LeadConnector/GoHighLevel funnel page — a template that flattened a cinematic video-production house and a Voice-AI receptionist product into the same stock sections. Neither brand's actual strength was visible, and the two companies had no shared data layer at all: two customer pools that should have been one.
The businesses cross-sell naturally — a media client is an automations prospect — so the right shape is a shared backend with completely divergent brand surfaces. Related brands deserve shared data, not shared branding. That shape is a single code workspace: two applications on top, common building blocks underneath.
One workspace holds two applications over four shared packages: a common data layer on a managed database, shared email templates, and shared config and interface primitives — each written once and consumed by both brands. The media app carries real-time 3D marketing surfaces that perform like a reel; the automations app tells the product story for the Voice-AI receptionist. A lead captured by either brand is queryable next to a customer of the other.
Consumer text-message opt-in routes into our central multi-brand consent store — the same infrastructure the rest of the portfolio rides — so both brands get TCPA-clean consent records from day one without standing up their own messaging stack.
The build is complete and ready to ship. The legacy GoHighLevel funnel still answers on the family's public domain — that's what the before-captures show — and the new sites go live the day the domains cut over to our hosting platform.
Architecture
What changed, with evidence
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.