Run the clubbehind the public profile.

It should help the club look official publicly and run private club work from one connected place: people, families, teams, sessions, messages, invoices, payments, roles, reports, setup, public publishing, and player progress where enabled.

Use the demo to map the work your club is currently chasing across spreadsheets, chats, paper forms, and separate tools.

No. The public club profile is the front door for parents, players, sponsors, and visitors. Behind it, the private dashboard helps club leaders manage the operating work that should not be public.

The public profile should build trust without exposing members, child records, invoices, messages, roles, reports, or private progress.

Club authorities and approved admins can work with people and families, programmes, teams, sessions, communication, requests, invoices, payment follow-up, reports, setup tasks, staff roles, public profile publishing, and performance tracking where the club uses those tools.

The dashboard conversation should start with the modules your club needs first, not a forced move of every process on day one.

They can use a private account area for the right club context. Depending on the club setup, families can manage linked child profiles, follow training and messages, review invoices, use online payment routes, and see private progress where enabled.

Parents and players are users of the system, but the buying decision stays with the club authority or committee.

Under-16 setup can include parent or guardian approval, linked child profiles, account activation, and the right private club workspace. Child and player records stay inside signed-in account areas.

The demo should confirm how your club wants parents, guardians, youth players, and existing player records to be linked.

Yes. Access can be shaped around the job someone does for the club. Coaches, treasurers, officials, team managers, and volunteers can be given the areas they need without exposing the whole club dashboard.

This is important for serious clubs because money, reports, settings, and private member records should stay controlled.

Public club pages can show published information such as activities, locations, sponsors, news, media, and contact routes. Child profiles, player progress, invoices, messages, member details, roles, reports, settings, and dashboard work stay behind sign in.

This separation matters because the public portfolio should help acquisition without leaking private club operations.

Official club links can carry the club context into sign-up, sign-in, password reset, invitations, and direct destinations. The aim is to send people to the right club journey instead of a confusing generic login route.

During a demo, confirm which emails and dashboard actions should send parents, players, officials, and staff into each journey.

A person may be a parent, player, club official, coach, or staff member. The account journey should preserve direct invitation destinations where possible and show the right workspace choice when a default landing needs it.

This protects direct email links while still helping multi-role users land in the right private area.

Families can review invoices, download records, view payment history, and use online payment routes where the club enables them. Payment provider setup, payment rules, and launch order are confirmed with each club.

Do not expect automatic collection or public checkout unless that is part of the agreed club setup.

Where enabled, coaches can use performance templates, feedback, reflections, attendance, and private progress reports. AI can help with prompts or templates, but coaches remain responsible for review and judgement.

Treat this as coach-supported performance tracking, not automatic player ranking.

No. The strongest onboarding route starts with the highest-value jobs first, such as public profile, people and families, staff access, sessions, communication, invoices, or player progress. The club can then expand in a planned order.

The demo should produce a practical first-phase setup path, not a generic tour.

MySportsHive is designed for grassroots clubs and academies, including football and multi-sport setups. The exact setup should be shaped around the club size, teams, roles, family access needs, payments, and reporting expectations.

Ekota Academy helped shape the product around real academy pressure, but each club still needs its own setup plan.

Bring the current club workflow: how people sign up, how parents and guardians are handled, how child profiles are managed, how sessions and messages run, how invoices are chased, who needs staff access, and what public profile information should be published.

The best demo should feel like a club operating review before it feels like a software presentation.