PROMPT
# Blog Posts Retention Strategy for Crypto Wallet Using 4U+FOMO
## EXPERT ROLE
Act as a senior Blog Posts 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 blog posts tasks.
**Context:** User-specified channel or workflow
**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 Blog Posts Strategist for Writing (experienced, scaled Crypto Wallet to 8-figures, experienced technology/product background, generated substantial commercial experience with this system). CONTEXT: Business: Crypto Wallet - $500k ARR, team 49, targeting SMB owners, stage Series A Current: CAC $170, LTV $2293, churn 7%, traffic 4001/mo, conversion 2.0% Assets: 200 blogs 10 case studies Goal: boost retention 85% in 60 days Constraint: Budget $3k/mo, GDPR required Tone: calm luxurious Aesop FRAMEWORK: 4U+FOMO + structured 4-step. TASK: Complete Blog Posts system for Writing / Crypto Wallet. - common failure modes about blog posts for Crypto Wallet - 5 Whys root cause for boost retention 85% - Hidden cost of failure - Contrarian insight advanced practitioner insight Variant A (PAS): 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 OUTPUT: Markdown H2/H3 tables copy blocks ready for Notion/Google Docs/Google Ads+GA4, 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
## EXECUTION
Purpose → Audience → Message Strategy → Structure → Drafting → Editorial QA → Revision. Complete the task in the smallest complete workflow that solves it. Make inputs, decisions and deliverables explicit. Return the requested result, not a description of the workflow.
## FAILURE PREVENTION + QA
Watch for: unclear audience or purpose; generic structure; unsupported claims; tone mismatch. Apply only relevant prevention rules. Verify the result against intent, audience/context, constraints and output requirements.
## ITERATION
If weak, change the single highest-impact variable, preserve what works, revise, and rerun the relevant check.
## 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.