Coaches, clubs & matches

A platform with three distinct roles, a jobs marketplace and a match-organising flow is a several-month build rather than a few weeks, because each role is effectively its own product on a shared data model. What moves the timeline is how different the roles' permissions are and whether scheduling, invitations and messaging are all in scope from the start. We phase it so the busiest role ships first.

Because their jobs barely overlap. A coach is looking for work and fixtures, a club is recruiting and managing a squad, a referee just needs assignments and availability. Bending one screen to fit all three produces an interface that serves none of them well, so Coachie gives each role its own views and permissions over the same underlying data.

Yes, and there is a real advantage in keeping them together. The same profiles that power hiring also power fixtures, so a club that recruits a coach can immediately organise matches with them — invitations, venues, times and referees — without exporting anything to a separate calendar or messaging tool.

It depends on scope, and the honest answer is that nobody can quote it from a feature list alone. The biggest drivers are the number of distinct roles, whether scheduling and messaging are included, and how much of a marketplace the jobs side needs to be. Shanti Infosoft scopes it on a short call and returns a fixed quote.