Why Pavilion exists
A cricket club holds an enormous amount in its people's heads and in places that do not talk to each other: scorebooks, spreadsheets, group chats, provider websites and the memory of whoever has been around longest.
Pavilion started inside one club with terrible processes. Availability was chased by message, fixtures and results lived in different places, and the club's history was slowly getting lost. We built the tools that club needed, and found that almost every club had the same problems.
Today Pavilion brings six products together around one shared record of a club's teams, players, fixtures and grounds.
To give the people who run cricket clubs better tools for the work they already do.
Keeping the record, planning the week, picking the side, running training, telling the club's story and looking after the ground.
A cricket club where the information is in one place and the history is easy to find.
So volunteers spend less time chasing details and more time on cricket.
To become the platform clubs reach for first, wherever the game is played.
While being straightforward about what the software does and doesn't do.
Evidence should support judgement.
Pavilion shows what is known and what is missing. The decision stays with the coach, selector or curator.
A club's history belongs to its people.
The record should be easy for players, past players and supporters to find.
Tools should fit how clubs really work.
Volunteers have limited time, and that should shape every screen.