Back to recipes

landing recipe

SaaS narrative landing

A proof-led SaaS page that moves from value proposition to trust, product stories, ecosystem fit, and a clear close.

Theme contract

light-dark

Variance / motion / density

variance
7/10
motion
2/10
density
4/10

Composition sequence

Role order the AI can adapt

Live source render · fixture content

Source-reviewed hero block

Make the next workflow obvious.

A split value proposition with one real media boundary and a clear first-viewport action.

Live source render · fixture content

A proof rail beside a meaningful claim

  • Source-readyreviewed
  • Data-awarestructured
  • Composablerole-based
  • Low motionreduced

03 · feature · required

Feature story stack

View contract
Live source render · fixture content

Tell the product story in a sequence

Alternate the media side and keep every row anchored to a concrete feature claim.

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

02 / Show the result

Make the outcome visible before the close.

Use the second row to explain the change the workflow creates.

  • Keep the hierarchy varied
  • Avoid a uniform gallery
Live source render · fixture content

The ecosystem is part of the product

Give the first connection more space, then let the rest become scannable.

Build

API surface

Connect the source that already owns the workflow.

Automate

Event stream

Move useful changes into the next system.

Store

Data layer

Keep context attached to the operation.

Extend

Runtime hooks

Leave room for the team’s own tools.

Live source render · fixture content

The best page sections give the reader a next move, not another thing to decode.

Jordan ParkProduct design lead · fixture attribution

06 · pricing · required

Pricing grid

View contract
Live source render · fixture content

A pricing choice with a visible next step

Use pricing as its own role; do not ask the CTA or FAQ to carry the same job.

Starter
For a focused first workflow.
$29/ month
  • One workspace
  • Core blocks
  • Guided setup
Growth
For teams building a system.
$79/ month
  • Shared catalog
  • Review states
  • Priority support
Scale
For a broader operating model.
$149/ month
  • Multiple teams
  • Custom contracts
  • Dedicated guidance
Live source render · fixture content

Answer the questions that block the next action

The FAQ stays distinct from pricing and the closing CTA.

A real screenshot, video, image, or live product preview with an accessible label.

Live source render · fixture content

Closing action

Give the page one clear way to continue.

A closing CTA should complete the narrative instead of repeating the hero.

  • One action
  • A concrete outcome
  • No duplicate hero copy