Adoption across a very wide user base

Club OS

Our operating system for members’ clubs: court booking, dining, guests, directory and committee governance, built for a membership whose youngest user is nine and oldest is ninety.

Sheet
W-01
Title
Case study
Issued for
Information
Drawn by
Snilld

Sheet W-01 · Adoption across a very wide user base · Membership and hospitality

Live
The home screen of an invented demo club: a greeting to the member, an illustration of the clubhouse and its courts, and the member’s next booking.
01 / 06The club, on a member’s phone
A booking screen listing the tennis, squash and badminton courts with what is free now, the coach for each, and games that want a player.
02 / 06Book a court
The same booking screen switched to a junior member, showing only what juniors may book and saying that adult open games are not offered.
03 / 06Booking for a child
The members’ book: an alphabetical directory of invented members with their membership type, the year they joined and their sections.
04 / 06The members’ book
The noticeboard: upcoming fixtures, and a question put to members about extending court hours, with three answers to choose from.
05 / 06Notices, and a question put to members
The booking screen in large-text mode, with bigger headings, labels and buttons.
06 / 06Large text, for older members

Demo data. Every name and number is invented.

Goes in
A noticeboard, a phone call, and a secretary who remembers everything
What we built
Booking, announcements, an open-play partner board, a directory and guest passes
Comes out
A member does it on their own phone — in large-text mode or kids mode if they need it
The line it does not cross
Each club is isolated by Postgres row-level security, not by application code alone

Note 1 · The constraint

A heritage private members’ club in Goa with more than 2,500 members runs on a noticeboard, a phone call and a secretary who remembers everything. Existing club software is priced for the United States and assumes members who will happily learn a new app. Most of this membership will not.

Note 2 · What we built

A mobile-first member platform with booking, announcements, an open-play partner board, a directory, guest passes and committee tools, plus a large-text mode and a kids mode because the age range demands both. Members sign in with a one-time code rather than a password, and a member who never installs anything can still be served at the office. It runs in production on Oracle Cloud in India, on Postgres with row-level security so each club’s data is isolated at the database rather than by application code alone, and every feature ships with a test proving one club cannot see another’s members. Consent and messaging follow India’s data protection law, and a member who should not be messaged is suppressed in the database before any notice goes out.

Note 3 · What transfers

The discipline that decides whether a shop floor, a depot or a field team actually uses what you commissioned. Most systems in this bracket fail on adoption rather than on features.

A platform we operate

This one is a product we own, host and run. It has its own site, with pricing and a way in.

Members at launch club
2,500+
Client
Anonymised
Isolation
Postgres row-level security
Hosting
Oracle Cloud, India region
Accessibility
WCAG 2.2 AA as the floor
Interactive demo
Public, no sign-up
← All workclubs.snilld.in/demo →Visit the product site →

Start with a prototype

Two to four weeks working from your own files, and at the end you hold something real. It is the cheapest way to find out whether any of this applies to you.

Start with a prototype