Priced per season. Quoted in writing.

If your season is simple, it might. A chatbot can draft a round-robin for eight teams on one field. But large language models are probabilistic: they predict the most likely next word, which works well for writing and poorly when every rule has to hold at the same time. Ask one for a real season and you can get a schedule that looks right and still hides a double-booked facility in week six, with no proof it checked anything. LeagueNav is built on a deterministic rules engine: every game is checked against every facility window, availability and scheduling commitment, the same way every time. AI sits alongside it to recommend an option and explain the tradeoff in plain language, but the engine underneath decides what is valid.

Plenty of organizations do, until the spreadsheet becomes the single point of failure. When the logic lives in one person's head, a season's worth of institutional knowledge walks out the door with them. LeagueNav keeps the constraints, decisions, and rationale in a system that survives turnover.

No. You do not have to replace what already works. LeagueNav can begin beside the registration, stats and communication tools you already run, replace one specific workflow that is breaking, or take on more of the operating stack over time where that is useful. Scheduling is where we start and go deepest, and the schedule connects to the systems you keep.

Yes, and it is free. A LeagueNav Preview is a private link that shows the product built around your organization: your name and colours, your terminology, sample teams and facilities in your structure, and a few of the rules you actually schedule around. We build it from public or approved information, you review it, and nothing is provisioned. It takes two minutes to scan. Ask with a short intake form and it arrives within 2 business days.

Within an agreed scope: preparing and validating inputs, building the schedule, surfacing tradeoffs, supporting review and publication, and handling the agreed post-publication support. The exact scope (review cycles, publishing outputs, change allowance, in-season support) is written into your proposal, so there are no surprises.

Co-Pilot is for a capable internal operator who wants to run the schedule themselves on LeagueNav, with structured configuration, review checkpoints, expert support, and escalation. It is offered on select engagements as implementations are proven out, not a broad self-service subscription.

The season keeps moving. Reschedules, game-level exceptions, results, officials, and communications all follow publication. Managed engagements include an agreed level of in-season support so those changes are handled without losing the context behind the original build.

Through scoped implementations. Where an approved API and access permit, we build direct integrations. Where they do not, we build structured import, export, and human-approval workflows. A healthy connection moves data. It does not, on its own, decide which system is the source of truth.

We make the authority explicit: which field is edited in LeagueNav, which is read from another system, and what gets flagged for mapping review. Disagreements are reconciled deliberately, not silently overwritten.

A clear read on how you schedule today, where it is breaking, and a recommended next step: Managed, Co-Pilot, a workflow implementation, or a simpler option. You leave knowing what fits, whether or not that is LeagueNav.

Managed is priced per season. The price depends on how many games and teams we schedule, your divisions and facilities, how clean your data is, how complex your rules are, how fast you need the schedule, and how much publishing, communication and in-season support you hand to us. After a free 30-minute assessment you get scope and price in writing, and nothing is billed until you approve both.

Your team and division structure, a representative slot inventory, the rules and scheduling commitments that matter, your current publishing platform, and one example of a recurring scheduling failure. The messier the real picture, the more useful the session.

Any sport where two teams meet at a venue, and any organization where limited facilities, team requests, and real-world complexity collide: leagues and associations, tournaments and events, multi-sport facilities, and recreation programs. Simple single-venue round-robins are better served by our free tools.