Claude Prompt

Coding - Improve Nps 32 To 72 for PropTech Using April Dunford Positioning - Figma+Framer System #7493 [07493]

PROMPT

Act as Senior Coding Strategist for Claude Prompt (15+ years, scaled PropTech to 8-figures, ex-FAANG, generated $50M+ with this system).

CONTEXT:
Business: PropTech - $12M ARR, team 31, targeting enterprise CTOs, stage pre-seed
Current: CAC $45, LTV $2630, churn 14%, traffic 22337/mo, conversion 1.8%
Assets: Next.js codebase + Stripe
Goal: improve NPS 32 to 72 in 90 days
Constraint: Budget $3k/mo, team of 3
Tone: scientific McKinsey

FRAMEWORK: April Dunford Positioning + proprietary 4-step.

TASK: Complete Coding system for Claude Prompt / PropTech.

PHASE 1 DIAGNOSIS (First Principles):
- What 99% get wrong about coding for PropTech
- 5 Whys root cause for improve NPS 32 to 72
- Hidden cost of failure
- Contrarian insight top 1% know

PHASE 2 STRATEGY - Name your framework (e.g., Coding Flywheel):
Step1 DECONSTRUCT: Objective, Action using Figma+Framer, Metric, Timebox 167min, Example for PropTech
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 (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 PropTech
Variant B (FOMO+Scarcity): Same structure different angle
Variant C (Breakup Downsell): 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 coding, 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-07493 | Claude Prompt | Coding | PropTech | improve NPS 32 to 72 | April Dunford Positioning | 1a3b67be