Appearance
How launch works
This section takes you from signing on to your first clean month of billing. It's built from real launches, so it covers the things that tend to trip gyms up, not just the happy path.
How to use it
- Work through the pages in order. Start anything marked lead time on day one.
- Most pages end with a checklist. Ticks are saved in your browser, so you can come back to it.
- The templates are ready to copy, edit and send.
The timeline
| When | Phase | What happens |
|---|---|---|
| Week -8 to -6 | Kick off | Pick your go-live date, give notice to your current supplier, start payment and app store paperwork |
| Week -6 to -3 | Build | Set up plans, classes, facilities, staff and payments in One Health. Trial import of your member data |
| Week -3 to -1 | Prepare | Sign off the trial import, train staff, start member comms |
| Launch week | Cut over | Freeze the old system, final import, switch billing, members sign in |
| Weeks +1 to +8 | Settle | Watch payments daily, chase members without a card, fine-tune plans |
What decides your go-live date
- Your current supplier's notice period. Commonly 30 to 90 days. Check your contract now.
- Moving members' payment details. A card data transfer between Stripe accounts can take 2 to 6 weeks.
- Your branded app, if you're having one. DUNS number and Apple enrolment can take 2+ weeks each.
Everything else fits around these.
The golden rules
Never let two systems bill the same week
Your old supplier's billing stops before One Health's starts. We'll agree a go-live billing date together, and anything due before it is treated as already collected by your old system.
Don't cancel your old system too early
Wait until your data export is confirmed in writing, and keep the old system read-only for at least 30 days after go-live.
Tell members early and often
The biggest source of launch-week admin is members who haven't signed in or added a card. The member comms plan covers this.