What should a sports team test during a wellness software demo?

Test how an athlete and the responsible staff member would complete a real routine, find relevant context, and follow up. Ask who can access information, what support is available, and what implementation requires. A useful demo shows the workflow your team intends to run.

A polished dashboard can be interesting without resolving your team’s actual problem. Before the call, choose one ordinary situation that is currently difficult: explaining the routine to new athletes, coordinating a follow-up, or keeping staff responsibilities clear.

Then ask the provider to walk through that situation using demonstration data. This checklist is an original procurement framework, not a description of features Kivi or another product necessarily includes.

Which scenarios should you bring to the demonstration?

Choose scenarios involving the people who will use and support the system. Include an athlete’s first experience, a normal staff review, and a change in the team’s circumstances. Keep the questions specific enough to produce an observable answer.

  1. An athlete joins the roster. What would they receive, what would they need to do, and who would explain the purpose?
  2. An athlete has a process question. Where would they ask it, and who would respond?
  3. A staff member reviews the agreed routine. What context can they see, and how would they arrange appropriate follow-up?
  4. A staff member is absent. How would the team handle cover without assuming someone else noticed the issue?
  5. An athlete leaves the team. What happens to access, records, and any ongoing subscription?

For each scenario, distinguish product behaviour from a process your staff must provide. A manual step is not automatically a problem, but it needs an owner and time in the operating plan.

What should you ask about information access?

Ask the provider to explain permissions, account ownership, retention, and reporting in terms your staff and athletes can understand. Establish what each role can see and how access changes when someone joins or leaves. Do not assume paying for the system grants access to all athlete information.

QuestionWhat a useful answer clarifies
Who can see which information?Role-specific access and any separate permission requirements
How are access changes handled?Responsibility for roster and staff changes
What is retained after departure?Retention, account closure, and deletion processes
What can be exported?Available formats, access controls, and exit arrangements
How are questions or incidents handled?Support contacts and established response procedures

If your organisation works with minors, involve the people responsible for safeguarding and age-appropriate consent before implementation. Any proposed use of medical or other sensitive information needs appropriate professional and organisational review. A product demo alone cannot establish that your planned use meets every requirement.

How do you compare features with the staff capacity to use them?

Map each promised benefit to an action, a responsible person, and a realistic review window. Ask what happens when staff do not complete that action. A tool should be evaluated as part of the operating routine rather than as a substitute for one.

Suppose your aim is more consistent between-session follow-up. The relevant questions include who reviews the information, when they review it, how athletes receive a response, and how staff know a conversation happened. A screen that displays information answers only part of that problem.

Keep a short demo record with three headings: shown in the product, requires our team’s process, and needs written confirmation. This prevents an interesting possibility from becoming an assumed feature or service commitment.

The weekly athlete check-in guide provides a separate example of a coaching routine. If that routine resembles your intended use, bring it to the demo and test the actual current workflow.

What should a team confirm before a rollout?

Confirm the scope, pricing basis, implementation tasks, support arrangements, and exit terms. Select a manageable initial group and define what you want to learn. Introduce the purpose and responsibilities before asking athletes to participate.

  • Scope: What is included now, rather than planned or optional?
  • Accounts and costs: Who needs access, who pays, and how do roster changes affect the agreement?
  • Implementation: What must the provider and the team each complete?
  • Support: Who handles product questions and who handles athlete support?
  • Review: How will you assess whether the workflow is useful and workable?

Explore Kivi for sports teams and Kivi for coaches with those questions in hand. Share the athlete experience page with the staff planning communication so the discussion includes what participation means for the athlete, not just the buyer.

If your team needs people to help run the program, say so during discovery. Software access and a staffed delivery arrangement are different requirements.

Frequently asked questions

Should we bring real athlete records to the demo?

Use fictional or properly anonymised examples. Do not place athlete health or private information in Kivi’s general website inquiry form.

Will software determine whether an athlete is medically ready to play?

Do not assume that. Medical assessment and participation decisions require the appropriate qualified people and procedures; confirm the actual intended use of any tool.

Can we assume a feature on a roadmap is available now?

No. Separate currently demonstrated capabilities from planned development and confirm anything material in writing.

What is a useful outcome from the first demo?

A clear understanding of whether the current workflow fits, what your staff must do, and which questions need further confirmation before a decision.

Bring your team’s real workflow to a Kivi conversation.

Tell Justin who you support and where coordination gets difficult. Explore the current software and whether your team needs additional delivery support.

Book a discovery call ↗