What it is. A member surface and a club office that are one record laid out two ways. Members say what they're into and who they would like to meet; the office sees which nights to open, who to introduce, who is drifting, and what every event costs. Two-way texting on the club's own number, with a person approving every send.
What it's not. Not a new billing system, not a new website, not a public directory. Statements, tee times, reservations and point of sale stay where they are. We read the roster and write back three things: a note, a charge, and the member's own profile.
What we won't do. A member's contact details never leave the club's system. No advertising, nothing sold, no member sees another until both opted in. Every text carries its consent record, honours quiet hours and STOP, and is drafted by the machine and sent by a person.
Nineteen screens a membership director opens on a Tuesday.
Captured from the prototype two Indianapolis clubs are looking at. The club's name and logo are masked; the members and numbers are sample data. Tap a screen to see it at full size.



















Staffing Next
Shifts per event from the cost sheet, open shifts to staff phones, hours into ADP or the payroll the club already runs, and a text to everyone on tonight: "event at six, see you there." The forecast is built; the roster publishing connects to 7shifts, HotSchedules or UKG.
The scheduler Next
One calendar for events, promos, messages, private events and shifts, with conflicts caught before anything sends and room holds two-way with Microsoft 365 or Google.
The phone in the store Next
The member surface is already a phone app in the browser and in Wallet. Native wrappers for the App Store and Google Play follow the first paying club, under the club's own name.
The full list, feature by feature, with what we build ourselves, what each needs from the club's side, and the fallback when nothing is connected, is on the integrations page. Every feature works with no connection and says so on screen.
What landed, dated.
The prototype is rebuilt from what club managers ask for on calls. These are the last seven days.
Menu quantities scaled to the head count, dietary from member profiles flagged for servers, staffing hours priced, a wine limit, the margin. A prompt to cancel the empty event and move its budget to the full one two days later.
A dedicated view of the members about to leave, worst first, one action per row. The connect-two-members screen with the drafted intro, approve or skip, a batch of ten, and the log of who connected whom.
Every club on one page, sorted worst first; open a club for financials, staffing, performance and its messages with corporate. Every group and every member link in the product now opens.
A city club on its real September programme, rooms, referral rewards and systems; a second, independent club on its actual venues, hours, member groups and portal. Each on its own address in its own colours.
The member surface and the club office laid out for a phone: single header, tab bar, chips that never wrap, every list reachable with a thumb.
For every screen: what we build ourselves, what it needs from the club, the fallback with nothing connected, and our confidence. Published on the integrations page.
Thirty minutes, your club's own numbers.
We walk the office on your phone, put your dues and your calendar into the value model, and tell you which of your systems we connect to first. The call lands on our calendar and you pick the time. A mutual NDA comes before a single question about your stack.
Pick whichever of the four is you. The first two we can usually show on the first call; the second two are a short working session.
We didn't survey clubs. We joined one.
Before clubs we built and ran the same kind of system in skilled nursing, a regulated industry where every message carries a consent record, every fact carries its source and its date, and nothing sends itself. SNFRadar, the market intelligence owners in fifty states read, is that system published. The discipline came with us; a club's members are the most private list it has, and we treat the list that way.
Our founder is a member of a private club and watched the gap first hand. Two Indianapolis clubs, one part of a national group and one independent and member-owned, are looking at the prototype built on their own rooms, hours and programmes.
“One channel for sign-ups, bookings, dining, events. Build rapport with your people. Connections over membership. Networking over not working.”
“A signal isn't a send. The machine drafts, a person approves, and the ledger row is written before the message leaves. That's how we built it for nursing homes and that's how a club's members deserve to be treated.”
Straight answers.
Do we have to replace our club management system?
No. Billing, statements, tee times, reservations and point of sale stay where they are. We read the roster and write back three things: a note, a charge, and the member's own profile. Every feature works with no connection at all and says so on screen; a connection makes it better, never possible.
What does it cost?
Per club, per month, sold on what it saves. Three tiers and an enterprise conversation for groups; the numbers and what isn't in the price are on the pricing page. At the industry's average dues, the entry tier pays for itself if the club keeps one member a year.
Who sees a member's phone number or email?
The club's system of record, and nobody else. Members message each other through the club. A number or email reaches another member only when its owner hands it over in a chat. There is no public directory and nothing is sold or shared.
Does it text members without asking?
Never. Every text carries its consent record with the time, source and wording of the opt-in. Quiet hours, a daily cap, STOP and HELP are enforced by the system, and every send needs a staff approval. The compliance log is a screen in the office, not a promise.
How long until we're live?
About thirty days from the roster import. We import the club's spreadsheet in its own field names, connect the first system, print the table cards, and train the front desk in an afternoon. The member surface runs under the club's own name from day one.
We're a group of clubs. What changes?
Each club gets its own office, its own address and its own theme, and its staff never see another club. Corporate sees every club on one page, worst first, and messages managers inside the product. Whether club staff see payroll and cost is the group's choice.
Can we see it on our own members?
Yes, and that's the second call. Under a mutual NDA we take your roster export and your calendar and show you your own club in the office within a week. Two Indianapolis clubs are looking at exactly that today.