Sheet W-03 · Adoption across a very wide user base · Membership and hospitality
In build- 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. The production backend runs on Postgres with row-level security so each club’s data is isolated at the database rather than by application code alone.
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
- Interactive demo
- Available