Generate multiple landing page message variants and score them against your ideal customer profile. Identify which value propositions, headlines, and CTAs resonate most with your target buyer.
You are a landing page messaging strategist. Your job is to generate and score landing page message variants for a B2B SaaS product.
My ideal customer profile (ICP):
- Role: {{icp_role}}
- Company size: {{company_size}}
- Primary pain point: {{primary_pain_point}}
- Secondary pain points: {{secondary_pain_points}}
- Key buying signal: {{buying_signal}}
- Decision criteria: {{decision_criteria}}
- Current solution/workaround: {{current_solution}}
My product:
- Name: {{product_name}}
- Core value prop: {{core_value_prop}}
- Key differentiator: {{key_differentiator}}
- Typical outcome/metric: {{outcome_metric}}
Current messaging (if any):
{{current_messaging}}
Task:
1. Generate 6 landing page message variants. Each variant should include:
- Headline (8–12 words)
- Subheading (12–18 words)
- Value prop statement (one sentence)
- Primary CTA copy
2. For each variant, score on a 1–10 scale:
- ICP Relevance: Does it speak directly to the ICP's pain or goal?
- Differentiation: Does it stand out from competitor messaging?
- Conversion Intent: Does it create urgency or curiosity?
- Clarity: Is the benefit immediately obvious?
3. Provide a brief rationale for each score.
4. Rank the variants. Recommend the top variant for A/B testing and explain why.
5. Flag any messaging risks or assumptions to validate.
Format as a table with columns: Variant | Headline | Subheading | Value Prop | CTA | ICP Relevance | Differentiation | Conversion Intent | Clarity | Total Score | Rationale.1. Fill in your ICP profile with specifics—avoid generic descriptions. 2. Describe your product's core value and differentiator clearly. 3. Run the prompt. 4. Review the scored variants and rationales. 5. Pick the top 1–2 variants for A/B testing on your landing page. 6. Use the 'risks' section to plan validation (user interviews, landing page tests). 7. Iterate: if a variant underperforms, adjust the ICP or product inputs and regenerate.
{
"icp_role": "VP of Sales",
"company_size": "100–500 employees",
"primary_pain_point": "Sales reps spend 6+ hours/week on manual data entry and CRM hygiene instead of selling",
"secondary_pain_points": "Forecast accuracy is poor; pipeline visibility is fragmented across tools",
"buying_signal": "Scaling sales team from 15 to 30+ reps",
"decision_criteria": "Ease of adoption, ROI proof, integration with existing Salesforce setup",
"current_solution": "Salesforce + manual processes, some Zapier automations",
"product_name": "DataSync",
"core_value_prop": "Automatically sync and enrich CRM data so sales teams spend time selling, not data entry",
"key_differentiator": "Only platform that auto-syncs Salesforce with email, calendar, and intent data in real-time",
"outcome_metric": "Sales reps save 5 hours/week; forecast accuracy improves 25%"
}| Variant | Headline | Subheading | Value Prop | CTA | ICP Relevance | Differentiation | Conversion Intent | Clarity | Total | Rationale |
|---------|----------|-----------|-----------|-----|---------------|-----------------|------------------|---------|-------|----------|
| 1 | Stop Manual CRM Work. Start Selling. | Your reps waste 6+ hours/week on data entry. DataSync automates it. | Automatically sync and enrich CRM data so your team focuses on revenue. | See 5 Hours Back | 9 | 7 | 8 | 9 | 33/40 | Directly names the pain (6+ hours), speaks to VP's core frustration. Clear outcome. |
| 2 | Your Salesforce Should Work for You | Real-time data sync + enrichment means your team stops chasing data and starts closing deals. | One platform to sync email, calendar, intent, and CRM—automatically. | Start Free Trial | 8 | 8 | 7 | 8 | 31/40 | Positions as enabler; mentions differentiator (real-time, multi-source). Slightly softer on urgency. |
| 3 | Forecast Accuracy Starts with Clean Data | 25% more accurate forecasts when your CRM is always in sync. | Auto-sync Salesforce with email, calendar, and intent signals. | Improve Forecast | 7 | 6 | 6 | 8 | 27/40 | Speaks to secondary pain (forecast). Metric-driven but less urgent than primary pain. |
| 4 | Scale Your Sales Team Without Scaling Admin | Hire 2x reps without hiring 2x ops. DataSync keeps your CRM clean automatically. | Real-time sync and enrichment so your team scales without friction. | See How | 8 | 7 | 7 | 7 | 29/40 | Resonates with scaling signal; slightly indirect on primary pain. |
| 5 | The CRM That Sells Itself | Your Salesforce data is always current. Your reps always know what to do next. | Automatic sync + AI-powered next-step recommendations. | Get Started | 6 | 8 | 8 | 6 | 28/40 | High differentiation and curiosity, but vague on ICP pain. Risk: overpromises. |
| 6 | 5 Hours Back Every Week | That's what your reps gain when DataSync automates CRM work. | Sync email, calendar, intent, and Salesforce in real-time. | Reclaim Time | 9 | 6 | 9 | 8 | 32/40 | Leads with quantified outcome (5 hours). High conversion intent. Lower differentiation. |
**Top Variant: #1 (Score 33/40)**
Headline: "Stop Manual CRM Work. Start Selling."
Why: Directly mirrors the ICP's pain (6+ hours/week on data entry) and positions the product as the solution. Action-oriented language ("Stop/Start") creates urgency. Subheading reinforces the metric and problem. CTA ("See 5 Hours Back") is outcome-focused and testable.
**Testing Recommendation:**
A/B test Variant #1 vs. Variant #6. #1 emphasizes pain relief; #6 emphasizes time gain. Both score high on ICP relevance and conversion intent. This will reveal whether your ICP responds more to problem-avoidance or benefit-seeking messaging.
**Risks to Validate:**
- Assumption: VP of Sales believes 6+ hours/week is the bottleneck. Validate in user interviews—it may be forecast accuracy or visibility instead.
- Assumption: "Automatically" is a credible claim. Ensure your product truly auto-syncs without manual setup; if onboarding is complex, soften language to "intelligently syncs."
- Assumption: Free trial is the right CTA. If your sales cycle requires a demo, test "Schedule Demo" instead.