System Blueprints
Leonardo's notebooks: flying machines and inventions centuries ahead of their time.
Build plans for funnels and automations, ready to copy.
Read a blueprint like a builder
Each blueprint below is a complete system: the pages a visitor moves through, the automations that fire behind them, and the one number that tells you whether it works. Build them in the order listed, one at a time. A finished simple system beats a half-built clever one.
Every blueprint uses the same notation: Page is something a visitor sees, Trigger is the event that starts an automation, Action is what the system does, Tag is the label it writes on the contact.
Blueprint 1: the lead magnet system
For: building a list from cold traffic. Watch: cost per lead and the share of new leads who open the first email.
| # | Piece | What it does |
|---|---|---|
| 1 | Page: opt-in | One promise, one form (name and email), no navigation |
| 2 | Trigger: form submitted | Starts the system |
| 3 | Action: tag + deliver | Tag "lead-[magnet]", send the delivery email within one minute |
| 4 | Page: thank you | Tells them to check their inbox, offers one next step (a low-priced offer or a call) |
| 5 | Action: start welcome sequence | Five emails over ten days, ending with an offer |
| 6 | Trigger: buys or books | Removes them from the welcome sequence, tags "customer" or "booked" |
Blueprint 2: the booked call system
For: selling a higher-priced offer on a call. Watch: show-up rate and the share of calls that are qualified.
| # | Piece | What it does |
|---|---|---|
| 1 | Page: video or sales page | Explains the problem, the method and who it is for |
| 2 | Page: application | Four to six questions that sort fit from no fit |
| 3 | Action: route by answers | Qualified go to the calendar; others go to a low-priced offer or a nurture list |
| 4 | Page: calendar | Shows open times for the next few days only |
| 5 | Page: confirmation | Short video or text: what to prepare, what happens on the call |
| 6 | Action: reminders | Email at booking, email and text the day before, text one hour before |
| 7 | Trigger: no-show | Same-day message with a rebooking link; tag "no-show" |
| 8 | Trigger: call outcome logged | Won: onboarding starts. Lost: follow-up sequence. Undecided: task for a follow-up call |
Blueprint 3: the buyer ladder
For: turning low-priced buyers into higher-value customers. Watch: average order value and the share of buyers who take the next step.
| # | Piece | What it does |
|---|---|---|
| 1 | Page: sales page | Sells an entry offer that solves one narrow problem |
| 2 | Page: checkout with order bump | One tick-box add-on that makes the entry offer faster or easier |
| 3 | Page: one-click upsell | The natural next step after the entry offer |
| 4 | Page: downsell | A smaller version of the upsell, shown only if they decline |
| 5 | Action: access and receipt | Grants access, sends login, tags each item bought |
| 6 | Action: use sequence | Emails that help them get the first result from what they bought |
| 7 | Trigger: first result reached | Invites them to the core offer |
Blueprint 4: the live training system
For: teaching and selling in one event. Watch: registration to attendance rate, and sales per attendee.
| # | Piece | What it does |
|---|---|---|
| 1 | Page: registration | Title, date, three things they will learn, form |
| 2 | Page: confirmation | Add to calendar link, one reason to show up live |
| 3 | Action: reminder sequence | Emails at registration, day before, morning of, one hour and at start |
| 4 | Trigger: attended or missed | Attended: offer sequence. Missed: replay sequence with a deadline |
| 5 | Page: offer | Order page shown at the end of the training and in follow-up emails |
| 6 | Action: close sequence | Three to five emails until the offer closes, then removed |
Automation build sheet
Write each automation here before building it. If you cannot fill a row, you are not ready to build it.
| Name | Trigger | Conditions | Actions | Tags written | Exit rule |
|---|---|---|---|---|---|
Naming rules
Consistent names are what make a system readable six months later.
| Thing | Pattern | Example |
|---|---|---|
| Tag | stage-detail | lead-pricing-guide, booked-discovery, customer-core |
| Automation | [blueprint] / [step] / [action] | Booked call / no-show / rebook |
| Link tracking | source, medium, campaign | source=meta, medium=paid, campaign=pricing-guide-oct |
| Page | offer-page type | pricing-guide-optin, pricing-guide-thanks |
Launch test
- Run the whole path yourself with a test email, start to finish, on a phone.
- Every form writes the right tag and starts the right automation.
- Every automation has an exit rule, so nobody gets a sales email after they bought.
- Reminders arrive in the contact's time zone.
- Every link carries tracking parameters, and a test purchase shows up with its source.
- Someone owns each manual step, and it is written down who.
Want this built for you instead of by you?
Return to the vault