Developer Prompt

API Design - Re-Engage 10K Cold Leads for Cybersecurity SaaS Using ACC - Figma+Framer System #8066 [08066]

PROMPT

Act as Senior API Design Strategist for Developer Prompt (15+ years, scaled Cybersecurity SaaS to 8-figures, ex-FAANG, generated $50M+ with this system).

CONTEXT:
Business: Cybersecurity SaaS - $2M ARR, team 30, targeting SMB owners, stage bootstrapped profitable
Current: CAC $165, LTV $3217, churn 3%, traffic 24999/mo, conversion 1.1%
Assets: 50k IG 100 UGC videos
Goal: re-engage 10k cold leads in 30 days
Constraint: Budget $3k/mo, GDPR required
Tone: premium direct no-fluff

FRAMEWORK: ACC + proprietary 4-step.

TASK: Complete API Design system for Developer Prompt / Cybersecurity SaaS.

PHASE 1 DIAGNOSIS (First Principles):
- What 99% get wrong about api design for Cybersecurity SaaS
- 5 Whys root cause for re-engage 10k cold leads
- Hidden cost of failure
- Contrarian insight top 1% know

PHASE 2 STRATEGY - Name your framework (e.g., API Design Flywheel):
Step1 DECONSTRUCT: Objective, Action using Figma+Framer, Metric, Timebox 123min, Example for Cybersecurity SaaS
Step2 DISTILL: Objective, Action template, Metric, Timebox, Example
Step3 DEPLOY: Objective, Action, Metric, Timebox, Example
Step4 DOMINATE: Scale after 7 days, leading indicator, iteration rule if metric < threshold

PHASE 3 EXECUTION PACK (3 Variants Ready-to-Paste into Figma+Framer):
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 Cybersecurity SaaS
Variant B (Objection Crusher): Same structure different angle
Variant C (Re-engagement): Same structure third angle
Each variant must be fundamentally different not reworded

PHASE 4 QA CHECKLIST (10-point): Specificity, No AI speak (delve/unlock/tapestry banned), One person one problem, Actionability 24h, Measurable leading/lagging, Differentiation moat, Constraint fit, Edge cases fallback, Legal GDPR, CEO test proud?

PHASE 5 NEXT 7 DAYS: Day1 2h audit enrich, Day2 3h build A, Day3 2h B+C tracking, Day4 1h QA 2 users, Day5 launch 10% segment, Day6 optimize winner kill loser, Day7 scale 100% SOP Loom

PHASE 6 PRO TIPS: 1% tweak 10x api design, failure mode avoid, tool stack saves 10h/week Figma+Framer+Clay+Instantly+Figma+Linear, delegate VA Loom script

OUTPUT: Markdown H2/H3 tables copy blocks ready for Notion/Google Docs/Figma+Framer, 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

Unique ID: PH-08066 | Developer Prompt | API Design | Cybersecurity SaaS | re-engage 10k cold leads | ACC | 5bba9440