Landing Page Copy Variants
Generate landing-page copy variants tuned to each segment's real pain — the headline that names the legacy tool they run, not a generic value prop.
Demand Gen - Landing pages
Headlines that name the legacy tool they run — not a generic value prop
3
Copy variants
Pain-grounded
Segment runs 4+ observability tools.
Variant A names the sprawl directly.
Segment runs 4+ observability tools.
Variant A names the sprawl directly.
| Variant | Angle |
|---|---|
| A | Consolidate the 4-tool sprawl |
| B | Cut mean-time-to-resolve |
| C | One bill, not five |
Why it lands
A generic 'observability, simplified' headline converts nobody. 'Still running four observability tools? Your on-call team is not' names the segment's actual pain — and the data says that pain is real.
Overview
Produce landing-page copy variants (headline, subhead, three value bullets, CTA) tailored to a target segment's HG-observed pain — installed-stack signature and category intent — so each variant speaks to a real problem the segment has, ready for an A/B test.
Use cases
A/B test real angles, not guesses
Three copy variants each grounded in a different real pain beats three variations of the same generic headline. The test learns something either way.
Copy that converts because it's specific
Naming the segment's actual installed-tool sprawl in the headline lands harder than any abstract value prop — because the visitor recognizes their own problem.
View workflow prompt
# Landing Page Copy Variants
## Parameters
- `{{offer}}` *(required)* — The offer the landing page promotes. Example: `unified observability platform`
- `{{target_segment}}` *(required)* — The segment the page targets. Example: `US mid-market software, 200-2000 employees`
- `{{category}}` *(required)* — Category whose intent/stack informs the pain. Example: `observability`
## Purpose
Write landing-page copy variants for {{offer}} aimed at {{target_segment}}, grounding each headline in the segment's real {{category}} pain (the legacy tools they run, the gap they research) so the A/B test compares real angles, not generic ones.
## Process
1. **Profile the pain** — `company_technographic` + `search_companies` to find the segment's common installed stack (e.g., 4+ overlapping observability tools) and `intent_category` for what they research.
2. **Derive 3 angles** — translate the top pains into three distinct value angles (consolidation, speed, cost).
3. **Write variants** — for each angle: headline (names the pain), subhead, three proof-oriented bullets, CTA.
4. **Keep it human** — apply humanizer discipline so copy doesn't read like AI filler.
5. **Test plan** — recommend which two variants to A/B test first based on pain strength.
## Output Format
Markdown with:
- `# Landing Page Copy Variants — {{offer}}`
- `## Segment Pain Profile` (cited)
- `## Variant A / B / C` (headline + subhead + 3 bullets + CTA each)
- `## A/B Test Recommendation`
- `## Citations`
## Quality Checklist
- Each variant's headline names a real segment pain, not a generic benefit
- Pain profile cites `company_technographic`/`intent_category`
- Copy reads human (humanizer applied)
- Test recommendation is grounded in pain strength