A small pilot.
A decision you can trust.

One workflow, one question.

Don’t make the pilot a miniature software replacement. Choose a specific handoff or follow-up process, document how it works today and agree why improving it would matter.

Your readiness checklist

0 of 12 ready

• Name one recurring process the club wants to improve.
• Identify the person who owns it and who approves a pilot.
• Review which parts the current software already handles.
• Verify the actual Stathyn feature, including any manual steps.
• Agree the minimum data and confirm authorised access.
• Resolve security, privacy, roles and written data-processing terms where needed.
• Record a baseline before the workflow changes.
• Choose a measurable outcome and a realistic evaluation window.
• Agree who reviews or approves member communication.
• Write down price, taxes, start, end and continuation terms.
• Schedule the review and define a sensible stop decision.
• Separate observed outcomes from unproven causal revenue or retention claims.

This checklist is kept in this page session only. Use Print or save the text copy for your records.

What counts as evidence?

A working demo proves that a demonstration works. A real pilot can establish whether staff can use the workflow, what effort it takes and what outcomes are observed. Stronger claims about incremental retention or revenue need appropriate comparisons and sufficient data.

At the review

Review the agreed baseline, usage and outcomes with the person who owns the process. Decide to continue, change the scope or stop. Put any paid next step in writing rather than silently extending an evaluation.