434 MEDIA
Agency Platform
The agency's public site and the internal operating system the team runs on every day.
- Client
- 434 MEDIA
- Timeline
- Jan 2025 – 2026
- Role
- Web Developer · Contract
Context
434 MEDIA is a San Antonio media agency. Under contract from January 2025, I built the internal operating system the team runs on every day, alongside the agency’s public site.
The same contract covered client work, including the platform for San Antonio Tech Day.
What I built
- –CRM with a pipeline and a Customer 360 view
- –AI prospecting: plain-English requests become Apollo searches, within per-user credit budgets
- –Outreach sequences and a blog CMS
- –Nine scheduled jobs syncing GA4, Instagram, and Mailchimp
- –A bilingual English/Spanish page for the agency’s SDOH work
One source
This codebase runs the agency site, CRM + pipeline, Apollo prospecting, outreach sequences, blog CMS, client newsletter signups, and bilingual SDOH page.
Stack
- Framework
- Next.js 16 App Router · React 19 · a [lang] route serving the SDOH page in English and Spanish
- Server
- HMAC-signed session cookies · four roles, from super admin to intern
- API
- 23 route groups, including webhooks, Meta Conversions API, Instagram, Mailchimp, search, and OG images
- Data
- Firestore through the Admin SDK, one module per domain · Vercel Blob
- Runtime
- Vercel AI Gateway · nine crons: GA4 and Instagram snapshots, Mailchimp sync, outreach every minute, feed publishing every 15 minutes
Design
An agency site has to hold other people’s color, so this one has none of its own. The only tokens are a neutral scale, and the client work supplies everything else. Personality lives in the type instead: two custom display faces and headlines that scramble before they settle. Behind the login, every internal tool is built from the same small kit of drawers, kanban boards, and stat cards, so the team learns the interface once.