Yield
+18%
Tee-sheet utilization, first 90 days
Live gap detection plus member-segment auto-fill replaces phone tag and waitlists nobody updates.
An invitation, no. 001
The operating systemevery country clubhas been waiting for.
Ashlr unifies the tee sheet, point of sale, member billing, inventory, events, and AI operations on a single ledger — so the general manager, the head pro, and the controller stop arguing with four different screens before lunch.
- 12+
- Surfaces in one OS
- 90 days
- Average pilot to live
- 1 ledger
- Per member household
Plate I
The 18th, golden hour
36°48'N · 78°24'W
01 · The premise
ountry clubs run on legacy software the way grand hotels once ran on key boards. It mostly works, until a Saturday morning when a booking is double-sold, the controller is reconciling four spreadsheets, and the locker-room attendant is texting the GM a photo of the broken POS.
We built Ashlr with operators who had run those mornings for decades. The product treats the club as one operation, not seven modules stitched by an integrator. One household. One ledger. One screen the manager opens at 6:30 a.m. and the head pro closes at sundown.
02 · What changes
Three numbers we report back to every pilot.
Speed
<2 min
From card swipe to closed POS ticket
Stripe Elements posts directly to the household ledger; receipt and audit trail go out on tap.
Visibility
<24 hr
AR aging from billing event to controller queue
Dunning, statements, and household-level risk feed the same picture the GM and owner see at 7 a.m.
Targets reflect Ashlr pilot data through Q1 2026. Your mileage scales with how cleanly you migrate; our team owns the parallel run until the controller signs off.
03 · The cockpit
The morning scramble,retired.
Ashlr's general-manager cockpit is a single live picture of the club: revenue, tee gaps, member balances, inventory exposure, and the AI's next three suggested actions — refreshed in real time from one Postgres ledger.
- Projected daily revenue$42.8K
- Open tee inventory18
- Dining minimum risk36
- Inventory exceptions11
Live · Brookhaven Hills · Saturday 06:48
/app
Revenue · today
$14,812
+12% vs trailing 4-Saturday median
Pro shop$3,210
F&B$5,108
Greens fees$4,294
Lessons$2,200
Ops Copilot · queued
- 01
Offer 8:40-9:20 tee gaps to members with high weekday conversion.
- 02
Move premium wedge restock ahead of Saturday fitting block.
- 03
Text social members at minimum risk with chef's table availability.
- 04
Add two outside-service staff during junior event arrival window.
Tee sheet · next 90 minutes
drag to reschedule · ⌘F to find member
ConfirmedMemberOpen · auto-fill candidate
04 · The index
Twelve surfaces.
One ledger.
Every Ashlr module reads and writes the same household, reservation, and ledger tables. Switch from the tee sheet to the member portal to the controller queue without re-keying a name.
- I
Tee sheet & resources
Conflict-checked, drag-to-reschedule
- II
Point of sale
Stripe Elements, member-charge ledger
- III
Member billing
Statements, dues, dunning, autopay
- IV
Inventory
Receive · adjust · transfer · serialized clubs
- V
Member directory
Households, privacy controls, search
- VI
AI ops copilot
Daily recommendations, fully audited
- VII
Lessons & packages
Pro calendar, package balance, billing on completion
- VIII
Public booking widget
Embeddable iframe; staff one-click approval
- IX
Notifications & GM digest
In-app bell + daily 6 a.m. digest
- X
Two-factor & audit
TOTP MFA, typed audit log on every event
- XI
Reporting
Daily revenue, AR aging, utilization, top members
- XII
Migration & imports
Validation, parallel run, controller sign-off
05 · Migration
The hard part isn't the software.It's the trust.
Switching club software is a board-level decision. We walk every pilot through a 90-day parallel run — your old system keeps charging dues until the controller signs the report saying Ashlr's books match.
- 1
Legacy export intake
We run a discovery week with the GM, head pro, controller, and IT lead. You leave with a written 90-day plan and a single shared spreadsheet of every legacy field.
- 2
AI field mapping
Members, households, dues plans, inventory, vendor list, prior-year transactions — all imported through validators that flag every conflict before they touch a live table.
- 3
Data quality report
Both systems run for two billing cycles. Ashlr emits a daily reconciliation: balances, dues collected, statements sent. The controller initials each one.
- 4
Parallel run
On a date the board picks, the legacy system goes read-only and the next dues cycle generates from Ashlr. The old vendor stays available for one statement past cutover.
- 5
Statement validation
- 6
Go-live cockpit
06 · Integrations
Plays nicely with the rails clubs already trust.
Ashlr owns the operating workflow and connects out to payments, accounting, calendars, messaging, simulator data, AI providers, and the legacy systems we're migrating you off of.
- Stripe
- Supabase
- xAI
- OpenAI
- QuickBooks
- Xero
- Twilio
- SendGrid
- Google Calendar
- Toast
- Lightspeed
- TrackMan
07 · Trust
Built like a system the controller would actually approve.
- Multi-tenant by design
- Postgres row-level security on every table. Tenant context resolved server-side; service-role keys never touch the browser.
- TOTP two-factor for staff
- Owners and managers enroll an authenticator at /app/settings/security. Middleware enforces aal2 elevation on every protected route.
- Stripe Connect & idempotent webhooks
- Each club is its own Stripe merchant. Webhooks deduplicate by event id; payments and refunds post atomically with the audit log.
- Audited from the ground up
- Every state change writes a typed audit_events row — auth, billing, reservations, POS, inventory, AI actions, integrations.
08 · Invitation
An invitation to pilotAshlr Golf OS.
We're onboarding a small cohort of country clubs through the end of 2026. Pilots include white-glove migration, a dedicated implementation lead, weekly board-readiness reviews, and a published rollback path. If your board has been asking for a modern operating system, we'd like to talk.