This page is built from the blueprint it teaches.
Anatomy
Seven parts, in this order, for a reason
The anatomy of a landing page that earns the email it asks for. Turn the skeleton on above and this page will label its own sections, because a blueprint that could not annotate its own page would not be worth following.
12 pages · 7 parts · free
The whole anatomy · no email required
All seven parts, named
Given away whole, because part two of the blueprint says to. The PDF carries the worked example for each, the failure mode, and the order argument in full.
The promise
One sentence naming what the reader gets and who it is for. If a stranger cannot repeat it after one read, nothing below it will be read.
The proof-of-standard
Something complete and immediately usable, before any ask. It demonstrates the quality of what is gated rather than describing it.
The honest cost
What following the advice actually takes. This is the section people cut, and cutting it is why their page converts worse.
The gate
One field, no friction, and the asset appears on the page. Anything more than an email is a tax you have not earned.
The thank-you step
The download, plus exactly one next step. Not a menu of them.
The closer
One product argument at the end. Per-section product panels are why pages do not get forwarded.
The reasonable questions
The objections you already know about, answered before they are asked, including the one you would rather avoid.
The honest part
A page built to this blueprint takes about a day
Four hours if you have the asset already written and know what your proof-of-standard is. Considerably longer if you do not, because part two is the one that cannot be faked: you have to actually give something away, and deciding what costs more than building the page around it.
Agent Craft’s own estimate, not a published statistic. The part people underestimate is not the build. It is that a page following this blueprint needs an asset worth gating, and most of the work is upstream of the page entirely.
Get the blueprint
Twelve pages, seven parts, one worked example each
- Each of the seven parts with a worked example and its characteristic failure
- The order argument: why proof has to precede the gate
- The wireframe, annotated, at three page lengths
- What to cut first when the page is too long
Get the playbook
Where should we send it?
Seven parts, in this order, for a reason. The anatomy of a landing page that earns the email it asks for, on a page that annotates itself with it.
One email with the download, and whatever you choose to receive after that. No sequence starts without you opting into it.
Agent Craft
One closer, at the end, exactly as part six says
There is no product panel between the sections above, because part six of our own blueprint says a page carrying them does not get forwarded. Agent Craft builds the asset that goes behind a page like this: a voice note becomes content across LinkedIn, X, TikTok and YouTube, and a personal brand CRM collects the people it brings in.
Start your free trial30-day free trial · no credit card required
Before you ask
Reasonable questions
Does the order of the parts matter?
Considerably. The proof-of-standard has to come before the gate, because it is what makes the gate reasonable. Pages that gate first and prove afterwards convert worse and produce lower-quality captures, which is the failure this blueprint exists to prevent.
How long should the page be?
As long as the proof takes and no longer. Length is not the variable people think it is: a short page with no proof-of-standard performs worse than a long one that gives something away. Cut the parts that describe, keep the parts that demonstrate.
Can I see the blueprint applied?
You are looking at it. Turn the skeleton on at the top of this page and every section labels which part it is. That is deliberate: a blueprint that could not annotate its own page would not be worth following.