Choose the decision the page needs to support. Each recipe shows how the argument should unfold and what every section or interaction must accomplish. Your Design Kit still controls the visual design.
7 recipes
Should visitors be able to try the main task right away? Use the first interaction as proof. Explain the product after visitors have searched, tried a sample or produced a first result.
Ask visitors what they want to accomplish before explaining the product. Their answer makes a broad platform personally relevant.
How it persuades
Ask visitors what they want to accomplish before explaining the product. Their answer gives them a personal frame for understanding everything that follows.
Put the visitor's query fields above every explanation, then let results, filters and adjacent reassurance do the persuading.
Open with the parameters of the transaction itself, quote price or availability immediately, then offer the account and the wider catalogue.
Let the visitor complete a small, safe version of the core action inside the page, then explain the full product behind it.
Name the one gesture the product is organized around, show it working in the first screen, then unfold the catalogue of actions it reaches.
Give the visitor a finished starting point, show the result it produces, then show exactly what changes when they make it theirs.
Give a runnable start at no cost, show the exact output to expect, then hand off to docs and to a scaling conversation.