Name the persona, the pain, and the fix — so the page earns the conversion, not the bounce.
Draft a use case page for VP RevOps using our CRM for onboarding.
The page named the persona (VP RevOps, 12 hires, onboarding bottleneck), the pain (4-week onboarding, 38% attrition), and the fix (2-week fix, 5-step workflow, 12% attrition). The page earned a 14% conversion rate, up from 3% on the prior feature page. The template earned the conversion because it named the persona, not wrote the features.
A use case page template is the draft that earns the conversion. It fixes the persona, the pain, and the fix — so the page reads as a story, not a feature. An SEO who writes the features earns the bounce; a use case page template that names the persona and the pain earns the conversion and the ROAS.
A reusable draft shape for the use case — the persona, the pain, the fix — that earns the conversion and the ROAS. The template fixes the shape so the page reads as a story, not a feature.
The one prospect the page earns — the title, the size, the industry — that earns the conversion. The persona is the part that earns the conversion, because an SEO who writes the features earns the bounce; an SEO who names the persona earns the conversion.
The one the prospect already has — the cost, the loss, the risk — that earns the conversion. The pain is the part that earns the conversion, because a persona without the pain earns the scroll and loses the conversion; a persona with the pain earns the fix.
The one solution the page earns — the feature, the workflow, the result — that earns the ROAS. The fix is the part that earns the ROAS, because a persona without the fix earns the pain and loses the conversion; a persona with the fix earns the ROAS.
The agent reads your persona and the pain, drafts the persona, the pain, and the fix, and ships the page. It pairs with the use case page strategy and the persona page draft templates.
The persona, the pain, the fix.
Agent names the one prospect.
The one the prospect has.
The one solution the page earns.
Names the persona, does not write the features
One pain per page, not five
Ends with the fix, not the feature list
Pairs with the use case strategy and persona templates
Name the one persona, the one pain, and the one fix. The page reads as a story, not a feature, which is why it earns the conversion, not the bounce.
The page that earns the conversion — the persona, the pain, the fix. An SEO who writes the features earns the bounce; an SEO who names the persona and the pain earns the conversion and the ROAS.
Name the one prospect the page earns — the title, the size, the industry. A page without the persona earns the features and loses the conversion; a page with the persona earns the ROAS, because the persona is what earns the conversion.
A persona that earns the conversion, a pain that earns the trust, and a fix that earns the ROAS. The page that writes earns the bounce; the page that names the persona earns the conversion.