Go-live checklist
Before a pilot tenant goes live, every required check below must pass on real data or be acknowledged by an operator. Recommended checks are not required but should be considered.
The same list is computed live for each tenant on the Pilot readiness page in the SaaS admin.
Business
- Business details complete (required)
Tenant has a timezone and currency set. - Tenant exists (required)
Tenant record has been created and is active (not archived). - Plan assigned (required)
A pricing plan has been linked to this tenant. - Billing status known (recommended)
A billing account exists OR the tenant is marked as demo/manual billing.
Locations & users
- Locations added (required)
At least one active location exists for this tenant. - Users added (required)
At least one tenant user exists (not counting SaaS admins). - Role access has been checked (recommended)
An operator has confirmed each role sees only what it should — tenant owner, location manager, viewer.
Data sources
- Integration connected or CSV fallback ready (required)
At least one source platform is in a `connected` state, OR at least one CSV import has been successfully completed. - Initial sync or import has run (required)
At least one successful sync run OR completed CSV import exists for this tenant. - Source catalogue exists (required)
Raw source catalogue items have been pulled in and are available for mapping.
Metric mapping
- Mapping inbox reviewed (recommended)
No unmapped source items remain, OR the operator has acknowledged that the remaining unmapped items are intentionally excluded for the pilot. - Required mappings approved (required)
At least one metric mapping has been approved or activated for this tenant.
Baseline & snapshots
- Baseline created (required)
A baseline has been computed and saved for this tenant. - Default targets set (recommended)
Per-stage targets exist on the baseline (e.g. lead-to-trial, trial-to-join, retention). - Metric snapshots exist (required)
At least one liftrr_stage_score_snapshot row exists so historical trends can render.
Dashboard & actions
- Dashboard has data or a clear empty state (recommended)
The customer dashboard either shows real numbers OR shows the documented empty state explaining what is missing. - Data freshness is visible (recommended)
The newest snapshot is recent enough that the dashboard's 'as of …' label is meaningful (within 35 days). - Numbers reconciled with source where possible (recommended)
An operator has spot-checked active members, revenue and visits against the source platform (Mindbody/CSV) and they match. - At least one issue/action recommendation, or a documented empty state (recommended)
Either Liftrr has produced an action recommendation, or the dashboard clearly explains why none is shown yet. - Customer dashboard reviewed internally (recommended)
Someone on the Liftrr team has opened the tenant dashboard and confirmed it is understandable end-to-end.
Governance
- Pilot go-live notes complete (recommended)
Notes have been added to the pilot readiness record (customer contact, success criteria, anything special for this pilot).