Contacts
Each side names one owner for configuration, day-to-day questions and running the review.
KOA / PILOT
Agree the scope, walk the whole workflow, then decide from what actually happened. There is no expansion plan waiting in the background.
Book a gym demo01 / THE PATH
Choose the site, the roles and the daily tasks to walk through. Write down what is in and what is out.
Work out accounts, role permissions and how member data is handled, and who owns each before anything is configured.
From a member's programme and logged sets through to a staff follow-up task and its recorded outcome.
Discuss what was actually used, where it stuck and what support was needed, then agree an adjustment or an extension.
02 / PILOT SCOPE
Both lists are confirmed again before a pilot starts. The second is not a roadmap promise — it is where the boundary sits today.
03 / WHO DOES WHAT
Each side names one owner for configuration, day-to-day questions and running the review.
Decide before the pilot which data is used, who maintains it and what happens to it at the end. We will not decide that for you.
Response route and hours are agreed up front. There is no 24/7 commitment, and it is not written into the default terms.
A pilot has a review date. Continue, adjust or stop is decided there, not assumed.