PROMPT
Act as Senior API Design Strategist for Developer Prompt (15+ years, scaled Crypto Wallet to 8-figures, ex-FAANG, generated $50M+ with this system).
CONTEXT:
Business: Crypto Wallet - $12M ARR, team 37, targeting enterprise CTOs, stage Seed
Current: CAC $149, LTV $3476, churn 14%, traffic 18888/mo, conversion 2.3%
Assets: Notion docs + SOPs
Goal: own category in 90 days
Constraint: Budget $3k/mo, GDPR required
Tone: friendly expert
FRAMEWORK: AIDA+PAS Hybrid + proprietary 4-step.
TASK: Complete API Design system for Developer Prompt / Crypto Wallet.
PHASE 1 DIAGNOSIS (First Principles):
- What 99% get wrong about api design for Crypto Wallet
- 5 Whys root cause for own category
- 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 Klaviyo, Metric, Timebox 89min, Example for Crypto Wallet
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 Klaviyo):
Variant A (Us vs Them): 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 Crypto Wallet
Variant B (Objection Crusher): Same structure different angle
Variant C (Referral Ask): 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 Klaviyo+Clay+Instantly+Figma+Linear, delegate VA Loom script
OUTPUT: Markdown H2/H3 tables copy blocks ready for Notion/Google Docs/Klaviyo, 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-08079 | Developer Prompt | API Design | Crypto Wallet | own category | AIDA+PAS Hybrid | ccb29492