Consumer apps · Chat platform

Project Atrium — eight-creator network for a consumer chat platform.

Engagement: 2025 Q1 → ongoing
Brand confidential · engagement detail available under NDA
Brief

A consumer chat platform needed organic distribution at the cost basis of automation, not paid acquisition. The brief: stand up a network of branded AI creators who could populate, warm, and operate platform-native accounts — while routing genuine demand back to the product’s primary URL.

SectorConsumer apps · chat / social
Stage at startLive product, paid-acquisition heavy, organic surface underbuilt.
Channels in scopeInstagram, YouTube Shorts, TikTok, X / Reddit lurk-and-comment.
ConstraintsPlatform anti-bot regimes, follow-action limits, daily post caps, IP-rotation requirements.
Build

01 · Persona network

Eight branded AI creators with distinct content lanes mapped to user-segment archetypes. Each persona has a consistent face, voice, posting style, and bio funnel.

Bios push every visitor to the brand’s primary URL through a single tap, not a creator-link tree.

02 · Device farm + warmup

Physical device farm running platform-native warmup loops. Bimodal scroll cadences, organic follow sweeps, hashtag rotation, per-account proxy isolation.

Per-serial locks and brand-aware dispatch so accounts on shared devices never collide.

03 · Content + distribution

Daily short-form output through the standard pipeline (script → voice → video → upload). Cohort fan-out across platforms with a min-age guard to avoid stampedes.

Performance feedback flows back into prompt and template selection weekly.

Result
8
branded AI creators in production
3+
platforms operated daily
100%
warmup automation — no manual handsetting
0
in-house creators or agency-of-record
24/7
orchestration via cron + dashboard ops surface
N+1
creators added per onboarding sprint — system scales horizontally
Operational notes

Beyond content, this engagement included the infrastructure most agencies don’t build: per-account proxy management, captcha auto-solve, OAuth token rotation across multiple GCP clients, multi-tenant Supabase as system of record, and a unified dashboard for caption review, render reset, and visual approval. The point is that “AI creator content” in production is not a generation problem — it is an operations problem, and the operations layer is what we own.

Stack
Anthropic ClaudeElevenLabsSeedanceFluxFastAPISupabaseDokkuPlaywrightAppiumAndroid device farmIPRoyal proxiesCapSolverYouTube Data APIInstagram Graph
Discuss a similar engagement →

If you’re running paid-acquisition heavy and want an organic surface that compounds, this engagement template is repeatable.