PROMPT
# Cold Email MRR Growth Strategy for Coaching Biz Using RICE
## EXPERT ROLE
Act as a senior Cold Email 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 cold email 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 Cold Email Strategist for Sales (experienced, scaled Coaching Biz to 8-figures, experienced technology/product background, generated substantial commercial experience with this system). CONTEXT: Business: Coaching Biz - $12M ARR, team 25, targeting B2B founders, stage pre-seed Current: CAC $157, LTV $2492, churn 11%, traffic 31315/mo, conversion 4.0% Assets: Next.js codebase + Stripe Goal: scale MRR $50k to $200k in 90 days Constraint: Budget $15k/mo, GDPR required Tone: premium direct no-fluff FRAMEWORK: RICE + structured 4-step. TASK: Complete Cold Email system for Sales / Coaching Biz. - common failure modes about cold email for Coaching Biz - 5 Whys root cause for scale MRR $50k to $200k - Hidden cost of failure - Contrarian insight advanced practitioner insight 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 Coaching Biz 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/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
## STRATEGIC WORKFLOW
Buyer Situation → Diagnosis → Value Hypothesis → Conversation/Offer → Objection Handling → Measurement → Next Action. Diagnose the real problem, desired outcome, strongest constraint and material assumptions before execution. Make the causal chain explicit: situation → diagnosis → strategic hypothesis → execution. Distinguish what is known, inferred and still needs evidence.
## EXECUTION + MEASUREMENT
For each major action, state the decision it influences, the leading signal, the primary outcome metric, the measurement window and the evidence required to proceed. When relevant, map the action to the funnel stage or customer journey it is intended to change. Do not recommend a metric simply because it is easy to measure; connect it to the stated business objective.
## EXPERIMENT + DECISION
State one falsifiable hypothesis. Change one meaningful variable, keep the baseline stable, define the success metric, minimum evidence threshold and decision rule. Separate diagnostic tests from optimization tests. If evidence does not support the hypothesis, explain the next smallest test or strategic change instead of rewriting everything.
## FAILURE PREVENTION + QA
Watch for: weak buyer diagnosis; feature-led rather than value-led messaging; unhandled objections; unclear next step; no qualification or follow-up logic. Apply only relevant prevention rules. Verify audience fit, source integrity, measurable outcome, constraint compliance, causal logic, output completeness and whether the recommendation can actually be acted upon. Flag unsupported claims and scenario assumptions explicitly.
## 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.
## SPECIALIST STANDARD
Judge the result using the professional standards of **Cold Email**. Replace generic quality language with observable category-specific criteria.
## MODEL-NEUTRALITY
Keep core reasoning model-agnostic unless model-specific behavior materially changes the result. When a model is specified, adapt only the relevant syntax or capability.
## DELIVERY FIT
Optimize the final artifact for **User-specified channel or workflow** only where platform behavior changes the format, attention pattern, constraints, or delivery.
## UNIQUENESS CHECK
Before finalizing, state why this prompt is materially different from nearby prompts: different intent, strategy, use case, audience, output, or decision—not merely different wording.