A page recipe is a reusable idea for how a site communicates value. Use one to shape the story, then let your Design Kit control how the result looks and feels.
8 recipes
Is the blocker risk, scale, cost or governance? Capability is not in doubt; consequence is. These sequences put the counterweight next to the promise instead of three scrolls later.
Make a concrete promise, follow it with dated, unit-labelled scale facts, then tie each fact to the surface that produces it.
Lead with the speed or capability, put the controls that bound it immediately after, then hand over the implementation detail.
State the job, show product evidence, add one quantified customer result, then offer the step that matches the visitor's stage.
Use recognizable customers to establish relevance, then immediately show a product or outcome detail so the logos are never the whole argument.
Name one outcome, then split the page into two honestly different paths: start it yourself, or bring in a team.
Put the value and the terms in the same view: what it costs, what is included, and what the visitor is committing to.
Move the reassurance out of the trust page and put it next to the search box, the listing and the buy button.
Discovery, identity, reassurance and transaction in one loop, closed by a reason to come back.