PROMPT
# Emails NPS Improvement Strategy for HR Tech ATS
## EXPERT ROLE
Act as a senior Emails 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 emails 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 Emails Strategist for Writing (experienced, scaled HR Tech ATS to 8-figures, experienced technology/product background, generated substantial commercial experience with this system). CONTEXT: Business: HR Tech ATS - $2M ARR, team 19, targeting SMB owners, stage pre-seed Current: CAC $37, LTV $929, churn 3%, traffic 22431/mo, conversion 1.5% Assets: Notion docs + SOPs Goal: improve NPS 32 to 72 in 90 days Constraint: Budget $15k/mo, no-code only Tone: calm luxurious Aesop FRAMEWORK: AIDA+PAS Hybrid + structured 4-step. TASK: Complete Emails system for Writing / HR Tech ATS. - common failure modes about emails for HR Tech ATS - 5 Whys root cause for improve NPS 32 to 72 - Hidden cost of failure - Contrarian insight advanced practitioner insight 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 HR Tech ATS Variant B (Social Proof Avalanche): Same structure different angle Variant C (Breakup Downsell): 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
## 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.