Copy template
Landing page hero clarity checklist
Audit whether a SaaS landing page hero explains the user, pain, outcome, mechanism, and CTA within five seconds.
Example
“For indie SaaS founders rewriting a launch page: replace vague AI productivity copy with one user, one costly before state, one concrete outcome, and one proof artifact above the fold.”
Copy structure
- Name the exact buyer or workflow before the feature list.
- State the painful before state in words the visitor already uses.
- Describe the desired after state as an observable outcome.
- Add one mechanism or proof artifact that explains why the promise is believable.
- Make the primary CTA match the visitor's readiness: preview, checklist, demo, or waitlist.
Reusable prompt
Audit the landing page hero for {product}. Score target user, painful before state, desired after state, proof mechanism, and CTA clarity from 1-5. Then rewrite the hero so a new visitor understands it in five seconds.
Commercialization notes
Buyer outcome
A founder can identify why a hero section feels vague and rewrite it into a clearer above-the-fold promise before paying for traffic.
Paid-pack fit
Strong fit for the landing-page hero pack because clarity audits create immediate rewrite tasks and paid-pack intent.
Implementation checklist
- Read the hero without the product name and confirm the target user is still obvious.
- Underline the before state, after state, mechanism, and CTA; rewrite anything missing.
- Run the final variant through a five-second test before shipping traffic.
Export format: Hero clarity scorecard plus rewritten above-the-fold variants
Related hooks
Paid-pack validation
Turn this swipe into a hero copy pack
Preview the $19 hero copy pack hypothesis for this swipe. Every click and signup helps separate real monetization intent from generic newsletter interest.
Keep the swipe file growing
Get weekly SaaS launch hooks
One email with fresh teardown notes, swipe-file patterns, and launch workflow examples for founders writing better landing pages, tweets, and Show HN posts.
No product spam. The first signal is whether founders want more reusable launch examples.