# Build a lead-magnet funnel in Systeme.io—and test the full delivery path

Documentation reviewed: 2026-11-01
Experience: documentation-backed, controlled teaching demonstrations; no company-result claim.

## Build
A two-page lead-magnet funnel, one delivery email and a five-case acceptance log.

## Inputs and source
- Audience/problem:
- Existing tool and reason for change:
- Consent/source permission:
- Destination or workflow version:

## Implementation
1. Define one promise and the smallest useful resource
   Expected output: A stranger can explain what the resource helps them do, and the file opens in a signed-out browser.
   Observed evidence: 

2. Create the two-page funnel
   Expected output: The funnel has exactly the two intended public steps and you recorded each preview/public URL.
   Observed evidence: 

3. Make the form match the promise
   Expected output: An empty or invalid email cannot pass; a valid owned test address follows the real submission path.
   Observed evidence: 

4. Make the thank-you page useful even before the email arrives
   Expected output: The resource link returns the actual current file in a clean browser and the message does not falsely report inbox delivery.
   Observed evidence: 

5. Connect the correct signup trigger to delivery
   Expected output: One owned-address signup appears against the correct funnel step and produces one intended delivery action, not two.
   Observed evidence: 

6. Run an acceptance test through the public page
   Expected output: You can reconcile successful form acceptance, the intended automation action and real recipient receipt as three separate observations.
   Observed evidence: 

7. Publish a small test and carry the output forward
   Expected output: The owner, current URLs, resource version and retest triggers are recorded in the downloadable acceptance log.
   Observed evidence: 


## Completion checks
- [ ] The promise names one audience and a useful output.
- [ ] An empty/invalid form cannot silently advance.
- [ ] A valid owned test creates the intended accepted contact.
- [ ] The thank-you resource opens without unintended permissions.
- [ ] The delivery email is actually received and its link works.
- [ ] Repeat-submission behavior is documented and unwanted duplicates are fixed.

## Failure test
- Input:
- Expected failure:
- Actual result:
- Fix and retest:

## Handoff
- Owner:
- Review trigger/date:
- Remaining uncertainty:
- Next Blueprint module:

## Fictional lead-magnet starter: Trial Enquiry Handoff Checklist
Audience: independent gym owner. Promise: assign a response owner and a next action; no membership guarantee.

1. Confirm the enquiry was actually accepted by your form/CRM. A button click is not acceptance.
2. Record its campaign/source in your approved customer system. Do not copy personal data into this public example.
3. Assign one named response owner and a permitted response channel.
4. Set the next-action date/time under your actual service policy.
5. Record the action and outcome: pending, contacted, appointment or not a fit. Do not guess at non-response.
6. Test the handoff using an owned test address, then remove test records from performance reporting.

Owner: ____  Last test: ____  Evidence location: ____  Review trigger: ____
Use your own privacy-approved system for identifiable customer records.