Your members open your club.
A private club spends a century building a name. Members should not have to learn a software vendor's brand to order a sandwich at the turn. So the app carries the club's name, the club's crest and the club's colours — and BetterClub is credited in one line at the bottom of the screen.
Named after something that is recognisably theirs.
A club founded in 1912 becomes "Club 1912" — its founding year, its crest, its own subdomain. A club with a famous hole or a founder's name uses that instead. It is the club's decision, made once at setup, and it is a data change rather than a build.
Every member-facing surface follows it: the app icon on the home screen, the push notification when the course opens, the statement email, the tab receipt. The one place our name appears is a small credit line, and it looks like this:
Shown at the foot of the member app. Not on the icon, not on the splash screen, and never in front of a guest.
The things that happen between the first tee and the last drink.
One app for the whole club — the course, the courts, the pool, the range, the dock, the dining room, the pro shop and the account behind all of it. Ordered by how often a member would actually use them rather than by how impressive they look in a grid, and the status badge on each one is honest.
Your week, in one place
LiveEvery booking the member has anywhere in the club — tee time, court, lane, squad, slip, lesson — answered as one question rather than six logins. Including the ones somebody else booked them into.
Statements and the balance
LiveThe itemised statement, the household it consolidates onto, the payment methods and autopay. A card number never reaches us — only a processor token, the brand and the last four.
The card goes round with them
LiveThe scorecard on their own phone, one hole at a time, marking the whole fourball. Then the round history, the handicap, and the leaderboard if it was a competition day.
Book a lane, sign the waiver
LiveThe pool's own member half: lane reservations against the club's privilege rules, and the waiver signed from the phone rather than on a clipboard at the gate.
What the club may send them
LiveA topic-by-channel grid the member controls, with the reason shown where they cannot change something. Nobody — including the club — can switch off an emergency.
Joining, properly
LiveAn application with a proposer and a seconder, the noticeboard period, and the board motion that admits them. An applicant is a real person before they are a member, and the system treats them as one.
Charge to the account
LiveAt the shop till, the bar, the dining room, the gate, the dock or the halfway house. Authorised against their real balance, credit limit and privileges at the moment it is rung.
Family permissions
PartialA spouse who may charge but is not billed is enforced at the moment a charge is rung, alongside the account's status and credit limit. Per-transaction caps and per-outlet restrictions are recorded and editable by staff and are not yet enforced by the posting engine — so a dependent's cap is a note today, not a refusal. Enforcing it, and letting a member manage their own household's permissions, are both still to come.
Order from where they are
PartialA poolside or beverage-cart order rung by an attendant lands on the account correctly today. A member placing it themselves — with a lounger or a hole number attached — is the next member-facing thing we build.
Announcements and closures
SpecifiedThe course shuts for lightning and the system already knows. What it cannot do yet is tell anybody, because no carrier is connected — so a closure is a phone call today. This is the first thing on the roadmap for that reason.
Minimum spend progress
SpecifiedThe minimum is billed and forfeited correctly. Showing a member how they are tracking against it, before the last week of the quarter, is a screen we have not built.
Referrals and event requests
Not builtA member-initiated vouch flow, the weddings portal for the members hosting one, and reciprocal access at other clubs. None of these exist.
The seasonal server, in week two.
Clubs hire in April and lose people in September, and the gap between a new server and a twenty-year veteran is almost entirely knowledge: who this member is, what they drink, which account it goes on, whether their guest may charge.
When the order comes in from the member's own phone, with the member's own account attached, most of that gap closes without anybody memorising anything. The staff member delivers to hole seven and the accounting takes care of itself — including the F&B minimum, including the spouse's charging privileges, including the guest fee.
The tee sheet, the courts, the lanes, the kitchen and the roster are now the same system, which is what makes that possible. The club does not yet know on Wednesday what Saturday needs — that wants a season of its own operating data first — but it is now a question the data could answer rather than one four vendors structurally cannot.
That is the version of this that a GM can describe to a board in one sentence, and it does not require the word "platform."
Built for a membership that is not all thirty.
A meaningful share of private club members and nearly every board are over sixty-five. So contrast is measured rather than eyeballed, no critical information is carried by colour alone, every status on this site is spelled out in words as well as shown in a colour, and the member-facing type is set larger than a consumer app would use.
Where we are not yet where we want to be: the staff back office still has secondary and tabular text below our own floor, and some of the fine print on this site sits just under it. Raising both is work in hand rather than a claim we are going to make ahead of it.
A member should not need to enlarge the screen to read what they were charged.
See it under your club's name.
Tell us the club and the founding year, and we will show you the member app carrying it.