The build, on one page
800 past inquirers (current students and 2026-inactive past students excluded), split 50/50 at random inside HighLevel. Same offer, same code, same deadline on both paths — only the front door differs. Winner = unique checkout clicks ÷ contacts in path.
How it flows
Tag rdk-fall-test added to all 800 → WF1 random split 50/50
Path A · Control (~400)
M1 · Day 1The $20 way in
M2 · Day 3What happens on the mat
M3 · Day 8Straight answers
M4 · Nov 11Last reminder
Checkout copy ASame $99→$20, code FALL26
Path B · Quiz (~400)
Q1 · Day 1Sells the quiz click only
The quiz5 taps + contact step → profile result page with the full offer
R1 · on submitResult email, 1 of 3 profile versions
Q2 · Day 3 / Q3 · Day 6Non-takers only → then M3 + M4 same as control
Checkout copy BIdentical page, separate URL = route attribution
Buyer exit Webhook from checkout tags rdk-purchased + rdk-sale-a/b → goal step stops all remaining emails in both workflows. A buyer never gets another sales email.
Tags & fields (her table, as the build's contract)
| Item | Type | Used for |
|---|
rdk-fall-test | Tag | Starts the test; bulk-added to the 800 |
rdk-path-control / rdk-path-quiz | Tag | Which path — the test's key |
rdk-quiz-taken | Tag | Stops quiz reminders; counts completions |
rdk-energy / rdk-confidence / rdk-focus | Tag | Quiz result profile |
rdk-clicked-checkout | Tag (trigger links) | Picks the winner |
rdk-purchased, rdk-sale-a / rdk-sale-b | Tag (webhook) | Paid; which checkout page |
child_age, held_back_reason | Custom fields | Segmenting; R1's personalized P.S. |
The five workflows — paste-ready AI-builder prompts
Each prompt is written as a spec: trigger, actions in order, real values, and what not to do. Build the skeleton with the AI builder, then open every action and confirm the values took before publishing. Nothing publishes or enrolls until the seed test passes.
WF1 · Splitter — entry + random assignment
Create a workflow named "RDK Fall Test - Splitter". Trigger: tag "rdk-fall-test" added. Actions: a Split action, Random Split, 50/50, with branches named Control and Quiz. In the Control branch: add the tag "rdk-path-control", then add the contact to the workflow "RDK Fall Test - Control Sequence". In the Quiz branch: add the tag "rdk-path-quiz", then add the contact to the workflow "RDK Fall Test - Quiz Sequence". Do not send any email or SMS in this workflow.
WF2 · Control sequence — M1→M4 with buyer exit
Create a workflow named "RDK Fall Test - Control Sequence". Trigger: added by workflow. Actions in order: send email "RDK M1 - A $20 way in"; wait until [Day 3 date] at 9:00 AM; send email "RDK M2 - What happens on the mat"; wait until [Day 8 date] at 9:00 AM; send email "RDK M3 - Straight answers"; wait until November 11 at 9:00 AM; send email "RDK M4 - Last reminder". Set a workflow goal: when the tag "rdk-purchased" is added, the contact exits the workflow immediately. Do not send any SMS. Do not add any other tags.
WF3 · Quiz sequence — Q1 → reminders for non-takers → rejoin M3/M4
Create a workflow named "RDK Fall Test - Quiz Sequence". Trigger: added by workflow. Actions in order: send email "RDK Q1 - Quiz email"; wait until [Day 3 date] at 9:00 AM; If/Else: if the contact does NOT have the tag "rdk-quiz-taken", send email "RDK Q2 - Quiz reminder"; wait until [Day 6 date] at 9:00 AM; If/Else: if the contact still does NOT have the tag "rdk-quiz-taken", send email "RDK Q3 - Straight offer"; wait until [Day 8 date] at 9:00 AM; send email "RDK M3 - Straight answers (quiz version)"; wait until November 11 at 9:00 AM; send email "RDK M4 - Last reminder". Set a workflow goal: when the tag "rdk-purchased" is added, the contact exits immediately. Do not send any SMS.
WF4 · Quiz router — submit → tag profile → send matching R1
Create a workflow named "RDK Fall Test - Quiz Router". Trigger: Quiz Submitted, filtered to the quiz "What kind of martial artist is your child?". Actions: add the tag "rdk-quiz-taken"; then If/Else on the quiz score: score 0 to 39 → add tag "rdk-energy" and send email "RDK R1 - Energy Channeler"; score 40 to 79 → add tag "rdk-confidence" and send email "RDK R1 - Confidence Builder"; score 80 to 100 → add tag "rdk-focus" and send email "RDK R1 - Focus Builder". Do not send any SMS. (If score branching is not available in one workflow, build three Quiz Submitted triggers filtered by result tier instead.)
WF5 · Purchase tracker — checkout webhook → buyer tags → emails stop
Create a workflow named "RDK Fall Test - Purchase Tracker". Trigger: Inbound Webhook. On each event, find the contact by the buyer's email address, then add the tag "rdk-purchased", and add "rdk-sale-a" if the payload's page field is checkout-a or "rdk-sale-b" if it is checkout-b. Do not send any email or SMS to the buyer from this workflow.
Who closes what
✅ We take (mechanical)
- Quiz built & hosted — done, live on this site
- All 9 emails staged — done, see the emails page
- Trigger links for every claim button (click = the winning metric)
- Contact-tracked quiz prefill — no email in any URL
- 50/50 split, tags, custom fields, both webhooks
- Scoreboard: opens / clicks / quiz-takes / checkout clicks per path, and a results read at the Nov 12 close
🥋 Studio facts needed (the VERIFY list)
- Checkout link — the keystone; two copies, one per path
- Sender name + reply email + phone
- Classes per week (or unlimited) during the 20 days
- Class days/hours + length + instructor setup, per studio
- Call-back window after purchase; T-shirt timing
- Price after day 20 / after Nov 12; release-form delivery
- Parent quote with written permission (or we drop the line)
Before anything sends — the seed test
- Take the quiz once per Q3 answer; confirm each lands in the right tier, result section and R1 version
- Confirm quiz submissions attach to the existing contact (tracked link), never create duplicates
- Send every email from both workflows to ourselves; check merge fields, buttons, FALL26 at checkout
- Buy once on each checkout page with a test card or 100% code; confirm rdk-purchased + the right rdk-sale tag land and the sequences stop
- Confirm the list = 800, excludes current students, 2026-inactive past students, and prior buyers
- Both sequences registered in our sequence monitor before the first enrolment
Launch timing
The plan's Wednesday Oct 28 is buildable but leaves no room for the seed test. Recommended: lock the checkout link and sender identity now, seed-test Thursday, launch Friday Oct 30 or Monday Nov 2. Every email gap and the November 12 deadline hold either way — M4 stays on Wednesday Nov 11 regardless.