Navigate by lifecycle

Use the current phase to find the next operating decision. A phase is not a maturity badge: revisit earlier phases when ownership, products, locations, law, vendors, or technical capacity change.

1. Validate

Define the member problem, service promise, location assumptions, manual baseline, risks, and stop condition before selecting software.

• Start with buy vs build vs self-host.
• Compare owner-operator tasks.
• Use the ROI calculator only with your own measured baseline.

2. Plan

Map products, roles, workflows, data, systems of record, approvals, budget, professional boundaries, manual fallback, and exit requirements.

• Define the canonical data and portability boundary.
• Browse roles and operator problems.
• Record recurring labor, not only software cash.

3. Select

Compare complete operating models and evidence, not feature lists. Confirm license, pricing, privacy, security, export, accessibility, support, and maintenance facts against current official sources.

• Use the Stack Builder.
• Browse business models, technical ability, and budget.
• Read the evaluation criteria.

4. Implement

Configure one isolated, reversible pilot with synthetic data. Name business, data, privacy/security, technical, and functional owners.

• Use starter packs only as non-production references.
• Follow the security baseline and backup/restore guide.
• Keep unrun runtime stages marked pending.

5. Launch

Reconcile migration, permissions, money, access, communications, fallback, support, and rollback before introducing members or consequential automation.

• Rehearse member onboarding.
• Test room booking and tour-to-close exceptions.
• Obtain required professional review.

6. Operate

Run the service with named queue owners, daily reconciliation, member-facing alternatives, access reviews, patches, backup checks, and documented incidents.

• Follow the maintenance cadence.
• Browse operational tasks.
• Keep consequential decisions and service recovery with people.

7. Grow

Improve qualified demand, conversion, retention, utilization, and product fit without weakening consent, service, capacity, or financial controls.

• Review growth and sales.
• Map marketing campaigns and member feedback.
• Measure quality, exceptions, and labor alongside revenue.

8. Scale

Add products, staff, integrations, or locations only after the first operating unit has accepted procedures, recovery, and local exception ownership.

• Evaluate the multi-location stack.
• Stage the multi-site rollout.
• Re-test data authority, privileged access, support coverage, and recovery at each site.

9. Renew or exit

Reassess vendor terms, observed outcomes, labor, incidents, ownership, portability, and alternatives. Renewal is a new decision, not an automatic continuation.

• Run vendor renewal and vendor offboarding.
• Test a reconciled export against the portability model.
• Revoke access, preserve only required records, rotate credentials, and close member/staff loops.