Challenge and Transformation Campaign

A six-week challenge is the best acquisition tool a gym or studio has, and most of them are run as a heroic manual effort that nobody wants to repeat. The signup page gets built from scratch every time. The participant list lives in a spreadsheet. Reminders are posted to a group chat by whoever remembers. Before-and-after measurements get taken on day one and then half the cohort is never measured again, which quietly destroys the thing the whole campaign was supposed to produce. By the final week the owner is exhausted, the cohort has thinned out, and nobody has the data to say what actually happened.

Then the conversion step gets missed entirely. A challenge is a trial, and the entire commercial point is that some share of participants becomes members at the end of it. But that conversation has to happen in a narrow window. The last week, while the person is still in the room and still proud of what they did. Miss that window and the cohort disperses, each participant goes back to their own life, and the business is left with a one-off burst of revenue and a list of people it will never contact again. Worse, because last time was so chaotic, the business waits eight months before running another one.

The third failure is that nothing is reusable. The campaign is rebuilt from nothing each time, so it never gets better. There is no record of which channel the participants came from, which week people dropped out, or what the conversion rate was, so the next challenge repeats the same mistakes at the same cost. This build makes the challenge a template: one funnel, one cohort pipeline, one daily cadence, one results-day sequence and one conversion window, all of which can be cloned with new dates and run again next quarter in an afternoon.

Pipeline and stages

One pipeline, Challenge Cohort, cloned per intake so each cohort's numbers stay separate and comparable:

• Interest - Waitlist: registered before signups opened
• Registered - Unpaid: form submitted, payment not completed; the biggest recoverable leak in the whole campaign
• Paid - Not Onboarded: paid, baseline session not booked
• Onboarded: baseline measurements taken, kickoff attended
• Active - Week 1 through Active - Week 6: one stage per week, which is what makes the drop-off week visible
• At Risk - Inactive: no attendance or no check-in for 7 days
• Completed - Results Captured: finished with final measurements on file
• Completed - No Final Data: finished without final measurements; tracked separately because it is a process failure, not a participant failure
• Converted - Member: joined on an ongoing membership
• Not Converted: finished and declined; goes to the next-cohort nurture list
• Dropped Out: stopped before completion, with a reason

Funnel and pages

• Challenge landing page: what the challenge is, the dates, what is included, what is expected of a participant, and the FAQ that answers the three questions every inquiry asks. One signup form, one button.
• Checkout page: the signup form with payment on the same step wherever possible, because a separate payment step is where half the registrations die
• Confirmation page: confirms the dates, links the baseline booking calendar immediately, and tells the participant exactly what happens next
• Waitlist page: live between cohorts, so demand accumulates instead of being lost
• Cohort hub: a members-area page carrying the schedule, the weekly content, the leaderboard where the business runs one, and the rules; this is what keeps the cohort from living in a group chat

Calendars

• Baseline Session: 20 minutes in the three days before the start date, for measurements, photographs if the participant opts in, and the readiness form review
• Kickoff Event: a single group slot with a seat cap, used as the cohort's start line
• Mid-Point Check: 15 minutes in week 3, the most important retention appointment in the campaign
• Final Measurement: 20 minutes in the last three days, booked in week 5 rather than week 6, which is the only way to get final data from the whole cohort
• Next Steps Consult: 20 minutes, the conversion conversation; offered during week 5 and week 6 while the participant is still in it

Custom fields

• Cohort Name and Cohort Start Date, Cohort End Date: every automation in the build is date-driven off these, which is what makes the whole thing clonable
• Challenge Day Number: number, incremented daily, drives the content cadence
• Baseline Captured, Final Captured: yes/no, the two fields the results-day reporting depends on
• Participant Goal: free text in the participant's own words, used in every message that needs to feel personal
• Team Name: where the challenge runs in teams; a strong retention lever and worth the extra field
• Check-Ins Logged, Sessions Attended, Last Activity Date: the engagement trio
• Readiness Form Complete: yes/no, a hard gate before the first session
• Photo Consent: explicit yes/no with a separate Marketing Use Consent; these are two different permissions and must never be collapsed into one
• Referred By: contact reference, so the referral engine can be measured
• Conversion Offer Made: date, Conversion Outcome: dropdown, Membership Start Date
• Dropout Reason: dropdown with free text

Tags

• challenge-waitlist, challenge-registered, challenge-paid, challenge-active
• cohort-2026-q1 or similar per intake. The tag that makes cohort-over-cohort reporting possible
• challenge-inactive-7d, challenge-at-risk
• baseline-missing, final-missing: the two tags that drive the chase sequences
• challenge-completed, challenge-converted, challenge-not-converted, challenge-dropped
• photo-consent-yes, marketing-use-consent-yes: held as tags so no automation can ever reach a participant's images without the permission being explicitly present
• next-cohort-nurture

Forms and surveys

• Challenge Signup: name, mobile, email, what they want out of it, how they heard about it, referral name, and separate explicit consents for SMS and for photographs
• Readiness and Waiver: sent immediately on payment. The participant confirms they are in a position to take part and records anything they want the coaching team to know. It captures what the participant states; it does not assess or screen anyone. Completion gates the first session.
• Baseline Capture: completed by staff at the baseline session; whatever measures the business has chosen, recorded consistently so the final capture is comparable
• Weekly Check-In: four questions, under a minute, feeding Check-Ins Logged and the engagement view
• Mid-Point Review: what is working, what is not, what would make the remaining three weeks better
• Final Capture and Feedback: final measures plus the experience questions, and a separate, explicit ask about sharing their story publicly
• Dropout Exit: one question, sent when someone stops; the data is worth more than the awkwardness

BO's role and guardrails

• BO handles the entire pre-signup inquiry load. What the dates are, what is included, whether it suits a beginner, whether they need to be a member: from the FAQ content on the landing page.
• BO chases the abandoned checkout, books the baseline session, chases the readiness form, and books the final measurement. These four jobs are most of the campaign's administrative burden.
• BO answers logistics all the way through: session times, what to bring, where to park, how the leaderboard works.
• BO never quotes a figure for the challenge, a membership or an upgrade. It explains what is included and routes to the signup page, or to a call at bookings.appbo.io.
• BO gives no training, nutrition, injury or medical guidance and makes no claims about results. If a participant asks what they can expect to achieve, BO describes what the program involves and offers a conversation with a coach. It never states or implies an outcome.
• BO never shares or references another participant's results, measurements or photographs: not in a leaderboard message, not as encouragement, not in aggregate.
• Anything about discomfort, injury, illness or a condition stops the automated thread immediately, applies a suppression tag, and goes to the coaching lead with the message quoted in full.

Numbers and channels

• One provisioned local number for the campaign, used for the whole cohort so the entire challenge conversation lives in one thread per participant
• SMS for the daily and weekly cadence, which is the channel the challenge actually runs on
• Email for the longer weekly content, the mid-point review and the results-day summary
• A cohort group channel or members-area feed for the social side, with the daily prompt cross-posted there as well as sent individually
• Social planner scheduling the pre-launch, open, last-call and post-results posts across the business's channels, planned as one campaign rather than improvised daily
• Review requests routed to the business's chosen platforms in the week after results day, when goodwill is at its highest point of the year

1. The waitlist is already warm. Between cohorts the waitlist page stays live and collects names. Two weeks before signups open, the whole waitlist gets first access, which fills a meaningful share of the cohort before a single advert runs.
2. Signups open. The social planner publishes the pre-launch, open and last-call posts on the dates set when the cohort was created. The landing page carries the dates, what is included, what is expected, and the FAQ. BO handles inquiries from that FAQ without a human touching them.
3. Someone registers. Marcus submits the Challenge Signup form with his goal in his own words, how he heard about it, and separate SMS and photograph consents. The contact is created, tagged challenge-registered and cohort-2026-q1, and an opportunity opens at Registered - Unpaid.
4. Payment is recovered, not assumed. Marcus gets distracted at checkout. Twenty minutes later BO sends one SMS with the checkout link. He pays that evening. The opportunity moves to Paid - Not Onboarded, challenge-paid is applied, and the leak that costs most challenges a fifth of their cohort is closed.
5. Readiness and baseline, in that order. The Readiness and Waiver form goes out immediately with the Baseline Session booking link. Readiness Form Complete must read yes before the baseline session can take place; BO chases it at 24 and 72 hours.
6. Baseline is captured. At the 20-minute session a coach records the agreed measures through Baseline Capture, takes photographs only where Photo Consent is yes, and writes Baseline Captured = yes. Anyone still showing baseline-missing 48 hours before the start date gets a direct call, because a participant with no baseline has no results and the whole campaign loses a data point.
7. Kickoff sets the start line. The cohort attends one group kickoff. The opportunity moves to Onboarded, then to Active - Week 1, challenge-active is applied, and Challenge Day Number starts counting.
8. The daily cadence runs itself. Each morning the day's prompt goes out by SMS and to the cohort feed, matched to Challenge Day Number rather than to a calendar date, so the content is the same for every cohort and only the dates change.
9. Weekly check-ins and stage movement. Every week the short Weekly Check-In goes out, increments Check-Ins Logged, and the opportunity advances to the next Active - Week stage. That per-week stage is what later shows the owner exactly where the cohort thins out.
10. Inactivity is caught in week two. Marcus misses a week. Last Activity Date passes seven days, challenge-inactive-7d is applied, the opportunity moves to At Risk - Inactive, and a coach gets a task to call him, not a template, a call. He comes back.
11. Mid-point review in week three. The Mid-Point Review form and the 15-minute Mid-Point Check go out to everyone. This is where a participant who is quietly struggling says so, and where the remaining three weeks get adjusted.
12. The final measurement is booked in week five, not week six. This is the single most important sequencing decision in the build. Everybody books their Final Measurement slot while they are still fully engaged, which is the difference between a cohort with complete data and a cohort with half.
13. The conversion conversation happens before the end, not after. In week five, alongside the final-measurement booking, every participant is offered a Next Steps Consult. The invitation references their own stated goal and what they have done over five weeks. The offer is described, never priced in a message.
14. Results day. Final measures are captured, Final Captured = yes, and each participant receives their own before-and-after summary: their data only, nobody else's. The cohort event celebrates the group. Opportunities move to Completed - Results Captured, or to Completed - No Final Data where the capture did not happen, which is logged as a process failure to fix next time.
15. Conversion and the long tail. Participants who join move to Converted - Member with Membership Start Date set. Those who decline move to Not Converted, get next-cohort-nurture, and are contacted when the next waitlist opens rather than being lost. Review requests go out to everyone who completed, in the week when goodwill peaks.
16. The cohort is closed out and the template is improved. The owner gets one report: registrations by source, paid conversion, baseline and final capture rates, attendance by week, drop-off week, completion rate, membership conversion rate, and referrals generated. Then the whole pipeline, funnel and workflow set is cloned with new dates for the next intake.

1. Waitlist Capture and Early Access

Trigger: waitlist form submitted, or an inquiry arrives while signups are closed.

• Action 1, immediate: create the contact, apply challenge-waitlist, open an opportunity at Interest - Waitlist, record the source.
• Action 2, immediate: confirm. "You're on the list, {{first_name}}. The next {{challenge_name}} starts {{cohort_start_date}} and waitlist gets first pick of places. I'll message you the moment signups open. Nothing else in between." Then honor that: no drip, no nurture, no weekly emails. The promise of a quiet list is why the list converts.
• Action 3, scheduled: 14 days before signups open, send early access to the whole waitlist. "{{first_name}}, waitlist access to {{challenge_name}} is open for the next 72 hours before it goes public. {{challenge_page_link}}"
• Action 4, wait 48 hours: if not registered, one reminder with the remaining time in the exclusive window.
• Action 5, on public open: one further message to the non-registered remainder, then remove challenge-waitlist and hand to the standard campaign audience.
• Action 6, after the cohort fills: anyone still unregistered stays as a contact and is re-added to the waitlist for the following intake, with one message confirming it. A full cohort should never mean a lost contact.

Exit: registered, or rolled to the next cohort's waitlist, or STOP received.

2. Registration and Abandoned Checkout Recovery

This is the highest-return workflow in the build. In most challenges a significant share of registrations never complete payment, and almost none of them are ever contacted.

Trigger: Challenge Signup form submitted.

• Action 1, immediate: create or update the contact, write Participant Goal, Cohort Name, Referred By and the source. Apply challenge-registered and the cohort tag. Open the opportunity at Registered - Unpaid.
• Action 2, immediate: if payment completed on the same step, route straight to workflow 3 and stop here.
• Action 3, wait 20 minutes, no payment: SMS. "Hi {{first_name}}, BO from {{business_name}}, your place in {{challenge_name}} isn't held until checkout's done. Takes a minute and the link picks up where you left off: {{checkout_link}}"
• Action 4, wait 3 hours: email with subject "Your place in {{challenge_name}} isn't confirmed yet", restating the dates, what is included and the seat cap, with the same link.
• Action 5, wait 1 day: SMS offering a human. "Still want in, {{first_name}}? If something's in the way (a question, a date clash) reply here and I'll get it sorted. If the timing's wrong, no problem, just say."
• Action 6, wait 2 days: task for a coach to call. By this point a human conversation converts considerably better than a fourth message.
• Action 7, 72 hours before the start date: final SMS to anyone still unpaid, naming the real deadline. "{{first_name}}, last call: {{challenge_name}} starts {{cohort_start_date}} and baseline sessions are nearly full. {{checkout_link}}"
• Action 8, at the start date: move remaining unpaid registrations to Dropped Out with Dropout Reason = never paid, apply next-cohort-nurture, and remove them from the active cohort tag so they do not receive the daily cadence.

Exit: payment received, declined explicitly, start date passed, or STOP received.

3. Payment, Readiness Gate and Baseline Capture

Trigger: payment-succeeded event for a challenge product.

• Action 1, immediate: move to Paid - Not Onboarded, apply challenge-paid, write the consent tags from the signup form: photo-consent-yes and marketing-use-consent-yes applied only where each was separately and explicitly given. Apply baseline-missing.
• Action 2, immediate: send receipt, the Readiness and Waiver form and the Baseline Session booking link together. "You're in, {{first_name}}. {{challenge_name}} runs {{cohort_start_date}} to {{cohort_end_date}}. Two things before we start: this form, and your 20-minute baseline session. Book it here: {{baseline_link}}"
• Action 3, wait 24 hours: branch. No form, no booking: send both links again, one message. Form done, no booking: booking link only. Booking done, no form: form only, with a plain note that it must be complete before the first session.
• Action 4, wait 72 hours: if either is still outstanding, task a coach to call. Both are gates, so neither can be allowed to drift.
• Action 5, hard gate: if Readiness Form Complete is not yes at 24 hours before the baseline session, notify the coach so they collect it at the door rather than proceeding without it.
• Action 6, baseline reminders: 24 hours and 2 hours before, with what to bring and what the session involves, so nobody arrives surprised by the measurements.
• Action 7, on baseline completed: write Baseline Captured = yes, remove baseline-missing, move to Onboarded, and confirm the kickoff time.
• Action 8, 48 hours before the start date: for anyone still carrying baseline-missing, notify the owner by name and create an urgent call task. A participant who starts without a baseline cannot produce results, so this is treated as an operational failure and escalated, not messaged.

Exit: baseline captured and kickoff confirmed, or refunded and moved to Dropped Out.

4. Kickoff and Daily Cohort Cadence

Trigger: Cohort Start Date arrives.

Conditions: contact must carry challenge-paid and the cohort tag, with Readiness Form Complete = yes.

• Action 1, start date: move to Active - Week 1, apply challenge-active, set Challenge Day Number = 1, grant access to the cohort hub.
• Action 2, start date morning: SMS. "Day 1, {{first_name}}. You said you wanted {{participant_goal}}, that's what the next six weeks are for. Today's task and the full schedule are here: {{cohort_hub_link}}"
• Action 3, daily at the set morning hour: increment Challenge Day Number, send that day's prompt by SMS and post the same prompt to the cohort feed. Content is keyed to the day number, not the date, so the whole library is reusable across every future cohort without editing.
• Action 4, weekly on day 1 of each challenge week: email the longer weekly content. The focus, the sessions, the one thing to concentrate on.
• Action 5, suppression rules: skip the daily send for anyone carrying an active escalation or chase tag, anyone who has opted out of SMS (they get the cohort feed and email instead), and anyone moved to Dropped Out. Never allow the daily prompt and a chase message to land in the same morning.
• Action 6, team branch: where Team Name is set, the daily prompt includes the team's own standing or shared target rather than individual comparisons, and no individual's measurements or results are ever named.
• Action 7, final day: remove challenge-active, stop the daily cadence, and hand to workflow 8.

Exit: cohort end date, drop-out, or STOP received (which moves the cadence to email).

5. Weekly Check-In, Stage Progression and Inactivity Rescue

Trigger: scheduled weekly on the cohort's check-in day; plus a daily inactivity evaluation.

• Action 1, weekly: send the Weekly Check-In. "End of week {{challenge_week}}, {{first_name}}, four quick questions so {{coach_name}} knows how it's actually going: {{checkin_link}}"
• Action 2, on submission: increment Check-Ins Logged, write Last Activity Date, advance the opportunity to the next Active - Week stage, and surface the answers on the coach's cohort dashboard.
• Action 3, no submission after 24 hours: one reminder, then stop. The attendance signal matters more than the form, so this is not chased hard.
• Action 4, daily inactivity evaluation: if Last Activity Date (the later of the last attended session and the last check-in) is more than 4 days ago, send one SMS. "Haven't seen you in a few days, {{first_name}}. Week {{challenge_week}} is usually where it gets hard: completely normal. What would make this week easier?"
• Action 5, at 7 days inactive: apply challenge-inactive-7d and challenge-at-risk, move the opportunity to At Risk - Inactive, and create a same-day coach task to call, not message. One phone call in week two recovers more of a cohort than any sequence; this is the step most challenges skip.
• Action 6, at 14 days inactive with no coach contact logged: notify the owner. Send one message offering a graceful exit as well as a return, because a participant who feels trapped tells people about it. "{{first_name}}, no judgment either way. If this cohort isn't going to work out, tell me and I'll sort it. If you want back in, {{coach_name}} will help you pick it up from where you are."
• Action 7, on return: remove the at-risk tags, return the opportunity to the correct Active - Week stage for the current date, and notify the coach so the return is acknowledged in person.
• Action 8, on explicit drop-out: move to Dropped Out, send the one-question Dropout Exit form, write Dropout Reason, stop all cohort messaging, and apply next-cohort-nurture unless the reason indicates otherwise.

Exit: cohort ends, participant drops out, or STOP received.

6. Mid-Point Review and Course Correction

Trigger: start of challenge week 3.

• Action 1, immediate: send the Mid-Point Review form with the Mid-Point Check booking link. "Halfway, {{first_name}}. Three questions, then grab 15 minutes with {{coach_name}} to adjust the back half: {{midpoint_link}}"
• Action 2, wait 2 days: if no booking, one reminder naming the remaining slots.
• Action 3, wait 4 days: for anyone with neither a form nor a booking, a coach task to catch them at their next session in person. The mid-point conversation is the most important retention moment in the campaign and should not be allowed to be optional.
• Action 4, branch on review answers. Where the participant reports the schedule as the problem, BO offers alternative session times. Where they report the program as too hard or too easy, the answer goes to the coach as a priority note and the coach responds: BO makes no programming suggestion of any kind. Where they mention discomfort, pain, illness or any condition, the thread stops immediately, a suppression tag is applied, and the coaching lead is notified with the message quoted in full.
• Action 5, on mid-point attended: log it, write Last Activity Date, and send a short confirmation of whatever was agreed, in the coach's words rather than a template.
• Action 6, immediate for low engagement: where Sessions Attended is below the halfway expectation, mark the mid-point task as priority with the numbers attached, so the coach goes into the conversation knowing.

Exit: mid-point completed, or week 4 begins.

7. Week Five: Final Measurement Booking and Conversion Window

Two jobs run together here, and the sequencing (week five, not week six) is the single most important decision in the build.

Trigger: start of challenge week 5.

• Action 1, immediate: apply final-missing, and send the Final Measurement booking link. "{{first_name}}, week 5. Book your final measurement now while the slots are open. They're in the last three days and they do fill: {{final_measurement_link}}"
• Action 2, immediate, separately: offer the Next Steps Consult. "Separately: you've put five weeks into {{participant_goal}}. Worth 20 minutes with {{coach_name}} to talk about what happens after the challenge finishes. What to carry on with, what to change. No obligation, and it's easier to have now than after you've stopped coming in: {{next_steps_link}}" Write Conversion Offer Made = today. No figure appears in this or any other automated message.
• Action 3, wait 2 days: if the final measurement is unbooked, one reminder; at 4 days, a coach task to book it with them in person at a session.
• Action 4, wait 3 days: if no consult is booked, email from the coach referencing the participant's own check-in history (sessions attended, weeks completed, their stated goal) and the consult link again.
• Action 5, week 6, day 2: for anyone with no consult booked, a coach task to have the conversation face to face at a session. The in-person ask inside the final week converts better than every message in this workflow combined.
• Action 6, final measurement reminders: 24 hours and 2 hours before, with what to bring so the conditions match the baseline.
• Action 7, on final measurement completed: write Final Captured = yes, remove final-missing, and generate the participant's own before-and-after summary: their data only.
• Action 8, on consult attended: the coach records Conversion Outcome. Joined moves the opportunity to Converted - Member and writes Membership Start Date. Declined moves it to Not Converted and applies next-cohort-nurture. Undecided schedules one follow-up task for three days after results day and no further automated chase.

Exit: both booked and attended, or the cohort end date passes (which hands any final-missing participant to workflow 8 as Completed - No Final Data).

8. Results Day, Reviews, Non-Converted Nurture and Cohort Close-Out

Trigger: Cohort End Date arrives.

• Action 1, immediate: branch on Final Captured. Yes moves the opportunity to Completed - Results Captured; no moves it to Completed - No Final Data and adds the name to the owner's close-out report as a process failure to fix in the next cohort. Apply challenge-completed in both cases.
• Action 2, results day: send each participant their own summary. "{{first_name}}, six weeks done. Here's your own before and after, {{sessions_attended}} sessions, {{check_ins_logged}} check-ins. You came in wanting {{participant_goal}}." Their data and nobody else's. No comparison to other participants, no cohort averages, no claim about what the numbers mean.
• Action 3, wait 1 day: email the Final Capture and Feedback form, including the separate, explicit question about sharing their story or images publicly. A yes here, and only a yes here, applies marketing-use-consent-yes: completing the challenge is not consent to be marketed with.
• Action 4, wait 3 days: request a review, routed to the business's chosen platform. "If the last six weeks were worth it, {{first_name}}, a couple of lines would genuinely help other people decide: {{review_link}}" Send once. Suppress for anyone who dropped out or raised a complaint.
• Action 5, wait 3 days, non-converted branch: for Not Converted, one message that closes the loop properly and does not push. "No worries at all, {{first_name}}, you finished it, which is the part that counts. I'll let you know when the next one opens and otherwise leave you to it." Then stop; they sit on next-cohort-nurture until workflow 1 contacts them at the next waitlist opening.
• Action 6, converted branch, wait 7 days: hand Converted - Member contacts to the standard member onboarding, and set a review task at 90 and 180 days so challenge-sourced retention is measured rather than assumed.
• Action 7, referral branch: where Referred By is set, notify and thank the referrer per the business's referral program, and record the referral against the next cohort's source reporting.
• Action 8, wait 10 days: send the owner the close-out report. Registrations by source, registration-to-paid and recovery rates, baseline and final capture rates, attendance and check-in rate by week with the drop-off week identified, completion rate, drop-out reasons, conversion rate, referrals and reviews. Then create a task to clone the pipeline, funnel and workflow set with the next cohort's dates. The close-out report and the clone task are what turn this from a campaign into an asset.

Exit: cohort closed out, report delivered, next cohort cloned; participants exit to member onboarding, to next-cohort-nurture, or on STOP.

The challenge becomes a repeatable asset instead of an annual ordeal. The funnel, the pipeline, the daily cadence and the results-day sequence all exist as a template keyed to Cohort Start Date, so the next intake is a clone with new dates rather than a rebuild. That single change is usually what takes a business from one challenge a year to one a quarter, and the compounding effect of that on the member base is larger than any individual optimization inside the campaign.

The three recoverable leaks get closed. Abandoned checkouts are chased within the hour instead of never. Missing baselines are chased before the start date instead of discovered on results day. Final measurements are booked in week five instead of hoped for in week six. Each of those is a sequencing decision, not a marketing one, and together they decide whether the campaign produces usable results data at all.

The conversion step becomes a designed part of the campaign rather than an afterthought. Every participant is offered a next-steps conversation inside the window where it works, with their own goal and their own six weeks in front of them. The business stops treating the challenge as a revenue event and starts treating it as what it is. A member acquisition channel with a measurable conversion rate.

And consent stops being a liability. Photograph permission and marketing-use permission are separate, explicit and held as tags, so no automation can reach a participant's images without the permission being present. Each participant's results summary contains their data and nobody else's.

What to measure

• Registration-to-paid rate, and separately the recovery rate from the abandoned-checkout sequence; this is where the cheapest gains in the whole campaign sit
• Registrations by source, including the waitlist and referrals as distinct sources, so the next cohort's spend goes where it worked
• Baseline capture rate and final capture rate: the two process-quality numbers. A low final capture rate means the week-five booking step is not being enforced.
• Attendance and check-in rate by week, which identifies the drop-off week precisely. Almost every challenge has one, and it is almost always earlier than the owner thinks.
• Completion rate, and drop-out reasons coded from the exit form
• Challenge-to-membership conversion rate: the number that decides whether the campaign was worth running, tracked per cohort
• Converted-member retention at 90 and 180 days, because a conversion that churns in two months is not a conversion; this is the metric that tells you whether the challenge is attracting the right people
• Referrals generated per participant and how many of those convert into the next cohort
• Reviews collected in the two weeks after results day
• Next-cohort uptake from the non-converted list, which is pure recovered value from people the business previously lost

Prerequisites

• Fixed dates and a seat cap, decided before anything is built. Every automation in this build is driven off Cohort Start Date and Cohort End Date. Moving the dates after the sequences are live means re-timing every one of them.
• The measurement protocol, written down. Exactly which measures are taken, with what equipment, by whom, and in what conditions. If baseline and final are not captured the same way, the results are not comparable and the campaign's central output is worthless.
• Staff capacity for the baseline and final measurement sessions. Two 20-minute appointments per participant across two three-day windows is a real scheduling constraint. Work out whether the cap fits the capacity before setting the cap.
• The daily content, written in full before launch. Six weeks is roughly forty prompts. Writing them during the challenge is how challenges fail in week three. Write them once, keyed to Challenge Day Number, and they are reusable for every future cohort.
• A decided conversion offer and who is authorized to present it, so the week-five consult has something concrete behind it.
• A written waiver and participation agreement, reviewed by the business's own counsel, covering participation, measurement, photography and the limits of what the program is.
• A decision on teams and leaderboards. Both drive engagement; both require rules written in advance, and a leaderboard needs a clear policy on what is displayed to whom.

Integrations

• Stripe for challenge payments, with the payment-succeeded event wired to the onboarding workflow and the abandoned-checkout event wired to the recovery sequence. Both events are load-bearing in this build.
• Google Calendar two-way sync per coach behind the baseline, mid-point, final-measurement and consult calendars
• Meta and Google advertising pixels and conversion events on the landing, checkout and confirmation pages, so registration source is attributable rather than guessed
• The business's chosen review platform for the post-results review requests
• Social channels connected to the social planner for the scheduled campaign posts
• Zapier or Make where an existing gym-management or access system needs to grant and then revoke challenge-period access

Number provisioning and messaging compliance

• Provision the campaign number and complete A2P 10DLC brand and campaign registration well before launch. This build sends a high daily volume to a cohort over six weeks, which is exactly the traffic shape carriers scrutinize; unregistered traffic will be filtered and the campaign will fail silently. Allow for the registration review in the launch timeline.
• Take SMS consent on the signup form with its own unticked checkbox and wording that says plainly that the challenge includes daily messages for six weeks. A participant who did not expect daily SMS will opt out in week one.
• Honor STOP, UNSUBSCRIBE, CANCEL, END and QUIT. Build the opt-out so it moves the participant to email-only for the cadence and notifies the coach, rather than dropping a paying participant out of their own program.
• Enforce quiet hours, around 9pm to 8am in the participant's timezone. Daily prompts go at a fixed morning hour, which makes compliance easy by design; the inactivity and chase sequences are the ones to watch.
• Keep the daily cadence to one scheduled message per day plus event-driven messages, and suppress the daily prompt for anyone in an active chase or escalation sequence so they never receive three messages in one morning.

Data protection and consent

• Photographs are the highest-risk object in this build. Keep Photo Consent (may we take and store them) and Marketing Use Consent (may we publish them) as two separate, explicit permissions. Never infer one from the other, and never let a single checkbox cover both. Hold both as tags so every automation can gate on them.
• Make consent withdrawable at any time, with a defined process for removing images from storage and from anywhere already published, and make sure participants know that is available.
• Each participant's results summary must contain only their own data. Aggregate or comparative reporting stays internal unless every participant in it has given marketing-use consent.
• Measurements, photographs and readiness-form answers should be restricted to the coaching team and the owner by role permission, with a retention period set rather than held indefinitely after the cohort closes.
• Keep marketing claims honest. Describe what the program involves and what is measured. Do not state or imply typical or expected results, and never publish a participant's story, image or outcome without their specific written permission. Advertising standards in most jurisdictions treat fitness and body-composition claims and testimonials strictly.
• Depending on where the business operates, health-information rules, advertising and consumer-protection standards, image rights and general privacy law may all apply to this campaign. Confirm the waiver, the participation agreement, the consent wording, the retention schedule and any public use of results or images with the client's own counsel. This guide describes how to build the mechanism and is not legal advice.