The Mechanism-Led Page

State the outcome and plant the name of the mechanism in the same breath, before you explain it.

• The headline is the outcome; the subhead is the named method that produces it
• The name is used as if it already means something — that curiosity is what buys you the next scroll
• One primary action, clearly subordinate to the reading; the real ask comes after the mechanism

Buy the reading time the mechanism needs. Recognizable names tell a sceptical visitor this framework is worth ten minutes.

• Directly under the hero: it has to land before the argument starts, not after
• Names this visitor reads as peers, or as companies with the same problem
• Kept to a strip — this is permission to continue, not a proof section

Confirm the pain in two beats and move on. This reader already lives with it; what they don't have is an explanation.

• Short enough to feel like recognition rather than a lecture: a few sentences, not a section
• Uses their words, ideally lifted verbatim from sales calls or support tickets
• Ends by pointing at the real question — not 'this hurts' but 'why does this keep happening'

Explain the way of thinking that makes the problem solvable, and give it a name the reader can carry into their next meeting.

• Explains why the usual approach fails — not that it fails, but the reason it can't work
• Simple enough to redraw on a whiteboard; if it needs the diagram from your deck, it isn't a mechanism yet
• It's a claim about how the world works, so it should be useful even to someone who never buys from you

Bring the abstraction down to earth: what the mechanism actually looks like in this reader's first week.

• Follows the mechanism's own logic, so the steps prove the model instead of sitting beside it
• Concrete about effort and time; a framework that sounds heavy to adopt dies here
• Three or four steps — enough to be real, few enough to feel achievable

Let a customer describe the mechanism working, in their words rather than yours.

• The quote is about the change in approach, not about the software being pleasant to use
• Ideally from someone who was sceptical of the framework first; converted sceptics are the strongest witnesses here
• Named and specific, so it reads as a report rather than a blurb

Say out loud what the reader is already thinking: that this is another framework invented to sell software.

• Names the objection in their own blunt words before answering it
• Answers with something checkable — results, a case, published methodology, an honest limit
• Includes at least one thing the mechanism doesn't solve; a framework with no boundaries reads as a sales device

Clear the practical questions now blocking a decision the reader has otherwise made.

• Questions come from real conversations, not from what's convenient to answer
• Answers directly, including where the answer is 'no' or 'not yet'
• Nothing here re-explains the mechanism; if it needs restating, the mechanism section failed

Close in the vocabulary the page just taught them, so acting is the obvious next line of the argument.

• Uses the mechanism's name: they should feel they're adopting an approach, not buying a tool
• Paired with the strongest risk reversal you can honestly offer
• One action, sized to how much they've decided — a first step, not a commitment

Close out without reopening the doors the page deliberately kept shut.

• Carries the diligence essentials: who you are, how to reach you, terms and privacy
• Links to the thinking — writing, docs, methodology — since that's what this reader wants next
• Doesn't reintroduce every product page the nav intentionally left out