Custom software for private tournaments and member events.
For golf trips, member weekends, invite-only tournaments, private clubs, retreats, and recurring groups that have outgrown spreadsheets, GroupMe, inboxes, and “ask the one guy who knows.”
Best for
annual golf trips · member events · retreats
Build shape
invites · schedules · live boards · archives
Typical start
3–5 weeks · $6K+ event hub
Built for live schedules, scoring/status boards, invitations, roles, messaging, archives, and data ownership — not another generic RSVP form.
Reference build
Tournament OS
Built from the CS Invitational model
Built first around golf. Useful anywhere the event has members, roles, live status, and history.
The reference build is a 36-player, 2-captain, 3-day invite-only tournament with live Ryder Cup-style scoring, tee sheets, captain views, GroupMe-friendly field updates, archives, and a permanent source of truth.
36 players
member records · invite links · roles
Live scoring
scoreboard · tee sheets · captain views
Field updates
GroupMe/SMS-style participant interface
History
archives · records · champions
Why this exists
Run the event. Preserve the lore. Make the whole thing feel official.
The best private events are already institutions. The software should make them feel that way — without trapping the people, records, and history inside consumer platforms.
The thesis
Free tools are fine until the thing starts to matter.
Google Forms, spreadsheets, group chats, Venmo notes, inboxes, and screenshots work right up until the event, club, sale, league, or decision becomes important enough to deserve a real source of truth.
We are not replacing free duct tape. We are replacing embarrassment.
Where this goes next
Events are the wedge. The pattern travels.
Tournament OS is the flagship proof. The same primitives — people, roles, access, live status, messaging, records, archives, decisions, and data control — show up in other high-context workflows.
Private events
Events OS
Operating systems for recurring tournaments, retreats, clubs, and invite-only communities that deserve more than a signup form.
Fantasy football
Dynasty OS
A read-only dynasty command center that turns league context, projections, rosters, picks, and timing into actions to consider.
Decisions + votes
Governance OS
Private decision infrastructure for boards, councils, clubs, and stakeholder groups that need records and accountability.
Revenue workflows
Sales OS
Custom sales systems for referral networks, weird pipelines, customer councils, sales contests, and the parts CRM never models right.
eBay / Whatnot / cards
Marketplace OS
Seller operating tools for inventory, listings, comps, show prep, streams, auctions, and fragmented marketplace workflows.
Proof case
A private tournament became an operating system.
The CS Invitational model starts as a recurring golf trip powered by emails, GroupMe, tradition, history, and human memory. The build turns that chaos into a private event OS.
The event did not need another signup form. It needed to feel like an institution.
Privacy & control
Own the people. Own the records. Own the history.
Important workflows should not live permanently inside a group chat, someone’s inbox, a copied spreadsheet, or a consumer platform you do not control.
No more institutional memory living in one guy’s inbox.
How it works
Start with one painful workflow. Leave with an operating system.
Fixed-scope sprints. Direct contact with Kendall. You own the code, the data, and the history at the end.
01
Map the mess
What runs through spreadsheets, chat, email, memory, and social pressure?
02
Find the operating truth
People, roles, permissions, events, records, rituals, decisions, money, and status.
03
Build the private layer
Branded app, admin tools, data model, bot/interface, archive, and dashboards.
04
Run it with real users
Launch, support, learn, iterate, and preserve the history.
Engagement shapes
Three sizes of build. All fixed scope. All yours at the end.
Event hub
$6K – $10K
3 – 5 weeks
One private event, tournament, club weekend, or ritual. Members, roles, live board, archive. The thing your spreadsheet keeps almost being.
·1 organizer
·≤200 participants
·1 recurring event
Operating system
Most builds$15K – $30K
6 – 10 weeks
A real source of truth. Multi-role permissions, integrations, bots, dashboards, durable history. The default for serious recurring work.
·Multiple roles
·Real workflows
·Integrations + bots
Recurring partner
$40K+
3+ months
Ongoing build + support. New features, new seasons, new integrations. For systems important enough to invest in continuously.
·Long-running OS
·Active iteration
·Live support
Numbers are starting points, not menus. Final scope is set after the first call.
Common questions
The things people ask before they send the first email.
How long does a build actually take?
Event hubs: 3–5 weeks. Operating systems: 6–10 weeks. Recurring partnerships are open-ended. The first two weeks of any build are scoping and the operating-truth pass — fixed scope locks at the end of that.
Who owns the code and the data?
You do. Source code, hosting account, database, member records, exports — all yours from day one. If we part ways, you keep running it without me.
What is the stack?
Next.js + TypeScript + Postgres for most builds, deployed on Vercel or your own infra. Integrations live where they need to (Slack, GroupMe, Sleeper, Stripe, whatever the workflow demands). Stack choices are explained, not imposed.
Why not just use {Notion / Airtable / a CRM}?
Those are great until you need real roles, durable history, live status, branded experience, or workflow logic the platform refuses to model. The moment 'we made it work in Notion' becomes the actual problem, you are ready for a real build.
Will I work with Kendall or with a team?
You work with Kendall directly. One founder, two to three live builds at a time. No account managers, no junior handoffs, no Slack purgatory.
What is NOT a fit?
Big public-facing consumer apps. Marketplaces hoping to be the next eBay. Anything that needs a 12-person engineering team. The fit is private, high-context, workflow-shaped — not platform-shaped.
Talk through your event
Have an event, club, league, or workflow that should feel more official?
Send the shape of the mess. Kendall will follow up if it looks like the kind of private system worth building.