Everyone says fix your messaging

Your mission is to design a comprehensive Conversion Rate Optimization (CRO) plan that drives sustainable increases in MRR while maintaining or improving LTV and keeping CAC within target ranges. You will deliver a complete, actionable blueprint that can be handed to product, design, and analytics teams and translated into a concrete backlog of experiments.

---

Context and scope to assume unless user provides specifics:

- Target audience includes professional buyers in mid-market to enterprise segments, with typical ARR and ACV ranges that the team can customize later.

- Current funnel includes awareness, consideration, trial/checkout, activation, onboarding, expansion, and renewal. Key metrics to improve include trial-to-paid conversion, activation rate, onboarding completion, time-to-value, retention, and expansion/cxt-driven revenue.

- Data sources you can rely on: product analytics (e.g., Mixpanel/Amplitude), web analytics (GA4), CRM/CSM data, product telemetry, onboarding analytics, and revenue metrics (MRR, churn, LTV, CAC).

- Instrumentation gaps: identify what data you would need to collect to validate each hypothesis and specify if gaps must be filled before testing.

What to deliver (structured, concrete, and ready to act on):

- Executive CRO blueprint: a high-level plan that states the business objective, target uplift, and alignment with product/UX, pricing, and growth goals.

- Current state snapshot (with placeholders): baseline funnel metrics, current CVR by stage, current onboarding completion rate, current activation metrics, and current CAC/LTV. If real data is unavailable, mark as placeholders for the client to fill.

- Strategy and hypotheses: a prioritized set of testable hypotheses across funnel stages (acquisition, activation, onboarding, pricing/checkout, retention/expansion). For each hypothesis, include rationale, expected impact, and risk context.

- Experiment backlog: a prioritized backlog table that includes:

  - Hypothesis description

  - Target metric and expected uplift (with calculation method)

  - Estimated effort (design, dev, analytics)

  - Required data/instrumentation changes

  - Success criteria and statistical significance target

  - Potential edge cases or rollout considerations

  - Dependencies and risks

- Experiment design templates: for each test in the backlog, provide a ready-to-use template including:

  - Objective, problem statement, and design (A/B, multi-arm, or multivariate)

  - Control and treatment definitions (copy, layout, UI changes, pricing/checkout variants)

  - Sample size and statistical method (e.g., frequentist 95% CI or Bayesian approach) and minimum detectable effect

  - Duration, traffic allocation, stop criteria, and veto/escalation rules

  - Data collection plan: metrics to measure, attribution windows, and telemetry changes

  - Rollout plan and rollback criteria

- Measurement and analytics plan: specify how you will instrument, measure, and monitor results. Include:

  - KPI definitions (with units and calculation methods)

  - Dashboards or reports to be built (e.g., CRO backlog status, funnel metrics, activation metrics, onboarding completion)

  - Data quality checks, anomaly detection, and guardrails

  - Privacy/compliance considerations

- Activation and onboarding optimization: recommended changes to onboarding flows, in-app guidance, product tours, and activation signals to improve time-to-value and activation rate.

- Pricing, checkout, and monetization optimization: hypotheses and tests focused on pricing clarity, plan complexity, checkout friction, and payment options; include instrumentation needs.

- In-app messaging and communication optimization: targeted onboarding nudges, contextual messaging, and experiment design for in-app CTAs and guidance.

- Email and nurture optimization: flow ideas for post-signup emails, educational content, trial reminders, and renewal/expansion communications; include testing plan.

- Risks, mitigations, and governance: identify potential risks (pricing perception, feature conflicts, churn risk from changes) and how you will mitigate them; define governance for test approvals, data quality, and stakeholder alignment.

- Rollout plan and change management: steps to move from test to rollout, stakeholder sign-off, feature flag strategies, and phased deployment considerations.

- 90-day roadmap: concrete milestones, owners, and deliverables for weeks 1–12, with checkpoints and decision gates.

- Deliverables and assets: list of artifacts you will produce and in what format (e.g., documents, CSV/JSON backlogs, templates, copy drafts).

Best practices for high-quality responses (use these as the core criteria):

- Be specific and measurable: ground every hypothesis and forecast in explicit metrics, numeric targets, and defined success criteria. Include baseline assumptions and clear expected uplift ranges.

- Write like a human, with actionable detail: provide concrete steps, not vague guidance. Include example copy, UI copy variants, and concrete design suggestions where appropriate.

- Focus on high-ROI changes: prioritize experiments with the strongest expected impact relative to effort and risk; justify prioritization with a simple scoring framework (impact, effort, confidence, risk).

- Use rigorous experiment design: specify control/treatment, sample sizes, duration, stopping rules, and statistical methods. Include handling of multiple comparisons when you have many variants.

- Be data-driven and transparent about uncertainty: present confidence intervals, significance thresholds, and how to interpret results; flag when data is insufficient to decide.

- Avoid fluff and vanity metrics: do not propose tests that only improve metrics that don’t affect revenue or user value; tie tests to MRR, CAC, LTV, retention, or activation.

- Provide clear rollouts and rollback criteria: outline how to move from test to production, what constitutes a successful lift, and how to revert if a test underperforms or introduces risk.

- Align with product and UX constraints: ensure proposed changes are feasible within the current tech stack and product roadmap; flag any required product or design work.

- Be explicit about data requirements: list exactly what data you need to measure each hypothesis and what instrumentation changes are required.

- Include customization hooks: sections and placeholders that allow easy replacement of company-specific numbers, segments, pricing, funnel stages, and success metrics.

- Plan for compliance and privacy: ensure data collection and experimentation respect user privacy and regulatory requirements.

What to include in the response (output structure and formats you should produce):

- A CRO blueprint document with clearly labeled sections: Executive Summary, Current State (with placeholders), Strategy & Hypotheses, Experiment Backlog (table format), Experiment Design Templates, Measurement & Analytics Plan, Activation/Onboarding, Pricing & Checkout, In-app Messaging, Email/Nurture, Risks & Governance, Rollout Plan, 90-Day Roadmap.

- A prioritized Experiment Backlog table (CSV or simple table) including: Hypothesis, Target Metric, Expected Uplift, Effort, Data/Instrumentation Needed, Success Criteria, Start/End Dates, Owner.

- At least one fully fleshed-out Experiment Design Template (A/B or multi-arm) with all fields filled as an example, plus space to copy for additional tests.

- Copy or asset drafts where applicable: landing page variant copy snippets, onboarding messaging copy, and checkout/pricing page variant ideas.

- A Measurement Plan with KPI definitions, dashboards to build, and data quality checks.

- An onboarding and activation blueprint with step-by-step flow changes and success signals.

- A concise 90-day rollout plan with milestones and owners.

How to customize this prompt (easy to adapt):

- Replace placeholders in square brackets with your company data: [CompanyName], [TargetSegment], [ARR], [ACV], [CAC], [ChurnRate], [BaselineCVR], [ActivationRate], [TimeToValue].

- If you have specific data sources or tools, mention them (e.g., “Amplitude as analytics, Salesforce as CRM, Stripe for payments”) and tailor the measurement plan accordingly.

- Add or remove funnel stages to match your product: e.g., if you don’t have a free trial, replace “trial-to-paid” with your actual conversion steps.

- Adjust the risk tolerance and test cadence to fit your organizational constraints (e.g., smaller immediate tests for regulated markets, larger tests for high-velocity growth phases).

Output format guidelines for the AI:

- Return in plain, clear sections with headings and bullet lists. Use concise, actionable language. Do not rely on emojis or hashtags.

- Where numerical targets are provided, present both baseline figures (or placeholders) and the proposed uplift targets.

- If data is missing, explicitly flag gaps and propose reasonable placeholder ranges or data collection steps to close gaps.

Language and tone:

- Write in 🇺🇸 English (US). Maintain a professional, collaborative tone suitable for sharing with product, design, analytics, and executive stakeholders.

Note on data and accuracy:

- Do not hallucinate product details or numbers. If any piece of data is not provided, clearly mark it as missing and base all recommendations on standard CRO best practices with transparent placeholders. When data is available, ground recommendations in those numbers and show the calculation where relevant.