01 / Shape the input
Start with the thing people already understand.
A story row can carry context without turning into a wall of copy.
- One claim per row
- Media remains a replaceable slot
landing recipe
A proof-led SaaS page that moves from value proposition to trust, product stories, ecosystem fit, and a clear close.
Theme contract
Variance / motion / density
Composition sequence
01 · hero · required
Source-reviewed hero block
A split value proposition with one real media boundary and a clear first-viewport action.
02 · social-proof
A proof rail beside a meaningful claim
03 · feature · required
Alternate the media side and keep every row anchored to a concrete feature claim.
01 / Shape the input
A story row can carry context without turning into a wall of copy.
02 / Show the result
Use the second row to explain the change the workflow creates.
04 · integration
Give the first connection more space, then let the rest become scannable.
Build
Connect the source that already owns the workflow.
Automate
Move useful changes into the next system.
Store
Keep context attached to the operation.
Extend
Leave room for the team’s own tools.
05 · testimonial
The best page sections give the reader a next move, not another thing to decode.
06 · pricing · required
Use pricing as its own role; do not ask the CTA or FAQ to carry the same job.
07 · faq
The FAQ stays distinct from pricing and the closing CTA.
08 · cta · required
Closing action
A closing CTA should complete the narrative instead of repeating the hero.