Your sport. Your processes. Your system.

We do not start with a catalogue of modules that your organisation must fit into. We start with your tasks, rules and bottlenecks: who registers athletes, who approves documents and where information gets lost. We then design the screens, roles and automations around that work. We reuse proven foundations, but build the scope and workflows for you.

Yes. We can build a tool in your chosen language or a multilingual environment where participants work with shared data in their own languages — particularly useful for international tournaments. Our offer is not limited to a fixed language list. Together we define translations, sport-specific terminology and which documents and notices need multiple language versions. Translation of user-entered content is scoped separately.

Yes — your processes are the starting point, not the name of the sport or the size of the federation. A project can cover a single tournament, club, league or entire federation. Together we define competition rules, scoring, roles and documents. WPOLO demonstrates a working water polo implementation; a solution for another discipline is designed and validated around its requirements.

First we understand your current work and agree priorities. We then define the scope, demonstrate key scenarios and test them with representative users. We can start with a pilot or one operational area and expand from there. Timing depends on workflows, migration and integrations; the delivery plan and acceptance criteria are agreed before development begins.

You do not necessarily have to enter everything again. We review available exports, formats, data quality and relationships before agreeing the migration scope. A trial import and validation can be planned before launch. Together we decide how much history to transfer, how to handle duplicates and which records need to be completed.

We can include document workflows, financial administration, exports and data exchange with existing tools. First we establish which information should move, in which direction and who approves it. Integration depends on the available interfaces and access permissions. You do not have to replace every tool that already works well; we design the missing connections.

WPOLO supports local match-sheet saving and export. For your project, we define which tasks must work offline, how work is recovered and when results may be published. Cross-device synchronisation and conflicting edits need their own design. Offline support does not mean that every function operates without a connection.

Access is designed around responsibilities: clubs, referees, delegates, administrators and public visitors need not see the same information. Before launch we agree hosting, data export, backups and maintenance responsibilities. Training, issue reporting and further development are also defined so the system can evolve with your organisation.

Pricing reflects the scope: workflows, user groups, migration, integrations and language versions. Our proposal separates implementation from agreed maintenance and further development. To start, tell us about your organisation and its most time-consuming task. You do not need a finished specification — we help turn the problem into a practical solution plan.