Design

Design Systems - Re-Engage 10K Cold Leads for Fitness AI

PROMPT

# Design Systems - Re-Engage 10K Cold Leads for Fitness AI

## EXPERT ROLE
Act as a senior Design Systems specialist. Solve the exact task. Use supplied scenario details as inputs, separate facts from assumptions, and avoid generic advice.

## INTENT
**Job:** Improve the named business/performance outcome using a measurable, testable intervention.
**Audience:** Professionals or practitioners using AI for design systems tasks.
**Context:** Primary professional application
**Success:** define 2–4 observable criteria tied to the requested outcome.

## WORKING BRIEF
Treat this as the authoritative source brief. Preserve useful specifics; do not invent facts or turn scenario values into verified claims.

> Act as Senior Design Systems Strategist for Design (experienced, scaled Fitness AI to 8-figures, experienced technology/product background, generated substantial commercial experience with this system). CONTEXT: Business: Fitness AI - $500k ARR, team 22, targeting enterprise CTOs, stage pre-seed Current: CAC $214, LTV $2808, churn 11%, traffic 9943/mo, conversion 1.4% Assets: 50k IG 100 UGC videos Goal: re-engage 10k cold leads in 90 days Constraint: Budget $8k/mo, team of 3 Tone: friendly expert FRAMEWORK: Hormozi Value Equation + structured 4-step. TASK: Complete Design Systems system for Design / Fitness AI. - common failure modes about design systems for Fitness AI - 5 Whys root cause for re-engage 10k cold leads - Hidden cost of failure - Contrarian insight advanced practitioner insight Variant A (Origin Story): Subject/headline 10 options with hypothesis, preview 3, body 250 words with {{FirstName}} tags PS PPS, visual brief, CTA, send logic delay trigger segment. Include placeholder [BRAND][AUDIENCE][DATA] + filled example for Fitness AI Variant B (FOMO+Scarcity): Same structure different angle Variant C (Referral Ask): Same structure third angle Each variant must be fundamentally different not reworded OUTPUT: Markdown H2/H3 tables copy blocks ready for Notion/Google Docs/Notion+Make, both placeholder and filled side by side No generic advice, every sentence actionable, specific numbers, decision tree If [condition] then A else B, no buzzwords without definition

## DESIGN WORKFLOW
Design Brief β†’ Audience β†’ Visual/Interaction Strategy β†’ Production β†’ Constraints β†’ Variants β†’ QA β†’ Handoff. Convert the brief into concrete design decisions for hierarchy, form, interaction or visual treatment as appropriate. Do not confuse style with strategy.

## CONSTRAINTS + FAILURE PREVENTION
Respect supplied brand, technical, accessibility, production and platform constraints. Watch for: strategy confused with style; category-inappropriate production choices; weak hierarchy; poor constraint handling; insufficient QA.

## VARIANTS + QA
Use controlled variants only when they test a meaningful design variable. Verify hierarchy, category fit, constraints, platform/application fit and professional usability.

## OUTPUT CONTRACT
Return a specific, immediately usable result. Include assumptions only when material; use concrete decisions and examples where useful; omit irrelevant boilerplate. Do not merely restate this prompt.

## SPECIALIST STANDARD
Judge the result using the professional standards of **Design Systems**. Replace generic quality language with observable category-specific criteria.

## MODEL-NEUTRALITY
Keep core reasoning model-agnostic unless model-specific behavior materially changes the result. When a model is specified, adapt only the relevant syntax or capability.

## DELIVERY FIT
Optimize the final artifact for **Primary professional application** only where platform behavior changes the format, attention pattern, constraints, or delivery.

## UNIQUENESS CHECK
Before finalizing, state why this prompt is materially different from nearby prompts: different intent, strategy, use case, audience, output, or decisionβ€”not merely different wording.