25 drafts. One human gate.
The model drafts, a person approves or edits, nothing leaves without a click. That is the human-in-the-loop pattern for any customer-facing generation.
Demo only — no messages are sent.
Acme Logistics
Sarah Chen
—
Nimbus Health
Daniel Park
—
Vector Retail
Jess Morales
—
Helix Studios
Marcus Webb
—
Lumen Foods
Carmen Reyes
—
Orbit Legal
Andrés Fuentes
—
Quartz Labs
Priya Nair
—
Sienna Talent
Tomás Guerrero
—
Pinetree Capital
Beatriz Alonso
—
Mosaic Travel
Isabel Vega
—
Cobalt Robotics
Zach Holden
—
Fern Education
Lucía Mendoza
—
Kite Mobility
Dani Torres
—
Briar Insurance
Thomas Gallagher
—
Solstice Wellness
Marta Ibáñez
—
Tundra Imports
Edward Nash
—
Glacier Hosting
Sam Rivers
—
Cinder Press
Pau Oliveras
—
Ember Realty
Claire Bouchard
—
Driftwood Hotels
Jake Saunders
—
Vesper Audio
Sofía Rueda
—
Loop Couriers
Alex Kim
—
Marsh & Co Bakery
Rosa Marín
—
Atlas Tutoring
Michael Osei
—
Northwind Energy
Rachel Thornton
—
The workflow, and how much of it is built here.
Solid steps run in this sandbox. Dashed steps are what a real implementation adds. Select any step to read what it does.
- 01Accounts
- 02Draft
- 03Review
- 04Send
25 accounts
Built in this demoA fixture of 25 accounts with the fields any CRM exposes: last contact, preferred language and a context line.
In detail
- →Generates 25 personalized outbound drafts in seconds — one per account, with full personalization off each account's last contact, language and context line.
- →Switch between 4 outbound intents (collections, re-engagement, product-update, referral) and the entire batch re-personalizes instantly.
- →Inline review for every draft — read the system + user prompt used to generate it, edit the copy, then approve before it would ship.
- →Bilingual (ES / EN) — each draft respects the account's preferred language, no translation step.
- →100 drafts (25 accounts × 4 intents) pre-generated with claude-sonnet-4-5 and shipped as static JSON — no API at runtime.
- →Per-intent system prompt + per-account user prompt assembled from the same fields any real CRM would expose.
- →Staggered timeouts simulate streaming so the UX matches a real batch run; status transitions (pending → generating → ready → approved) are pure local state.
- →Fully client-side. No backend, no keys, no network calls — safe to deploy as a static portfolio page.
- →Live CRM integration (HubSpot, Salesforce, Attio) for account state, owner, last-touch and reply tracking — not a static fixture.
- →Real Claude API calls per batch with prompt caching on the system prompt, plus rate-limit / retry / cost telemetry per run.
- →Send layer (SendGrid, Postmark, or native Gmail/Outlook) with per-account throttling and unsubscribe + suppression lists.
- →Approval workflow + audit log — who approved which draft, when, and which version actually shipped.
- →Per-intent eval set so prompt edits don't silently regress reply rate or tone for a segment.
- →Compliance guardrails — CAN-SPAM / LFPDPPP footer, opt-out handling, and a deliverability dashboard.
The pattern transfers cleanly to any high-volume operator workflow — renewals, dunning, NPS follow-up, partner onboarding. The work is in the intent library and the eval set, not the runtime.