Three plans, three sizes of club. Start with the pilot to prove Ashlr against your legacy stack, run live day-one payments, then graduate when the controller is ready. No annual lock-in unless you choose one.
01 · The plans
Three tariffs. One ledger.
Every plan is the full operating system. The difference is scale, support, and the integrations your board insists on.
Dedicated implementation lead for the 4-week pilot
The paid pilot starts with live Stripe/Connect readiness and a migration review. Convert to Operations or Estate after the pilot, or step away with a full SQL export.
Multi-property clubs run on a single workspace and reconcile across courses, courts, and dining venues with one ledger.
Prices in USD. Billed monthly via Stripe. Pilot rolls into Operations or Estate at conversion; we ask 30 days' notice if you choose to step away.
02 · The baseline
What you get on every plan.
These don't move with the tier. They're the contractual floor of working with Ashlr — the things a board or controller will ask about regardless of size.
Stripe Connect, end-to-end
Each club is its own merchant. We never touch the funds.
Postgres + RLS multi-tenancy
Row-level security on every table; tenant context resolved server-side.
Audit log on every event
Auth, billing, reservations, POS, inventory, AI actions — all written to a single typed feed.
Migration off-ramp guarantee
If you ever leave, we generate a final statement run and a full SQL export for the new vendor.
03 · Questions, answered
The fine print, in plain English.
01
Is there a long-term commitment?
No. Pilot and Operations are month-to-month. Estate clients sometimes choose an annual term in exchange for a small price reduction, but it's optional.
02
Do you charge a percentage on top of Stripe fees?
No. You pay Stripe directly for processing; we never take a percentage of your gross. The plan price is the plan price.
03
What does white-glove migration include?
A discovery week, a written 90-day plan, validated imports of members and prior-year transactions, two billing cycles of parallel run, and a controller-signed reconciliation before cutover.
04
Can we leave with our data?
Yes. Every plan includes a full SQL export at any time, and we'll generate a final statement run if you choose to migrate to a different vendor. The data is yours — that's contractual.
05
Do member-facing surfaces require their own seat?
No. Member accounts and the public booking widget are unlimited on every plan. You're billed per staff seat, not per member.
06
How do you handle multi-property clubs?
Estate workspaces let one ownership group reconcile multiple courses, racquets venues, dining outlets, and lodging properties on the same household ledger.
04 · Ready when you are
Start the pilot.We'll do the migration.
Four weeks to prove the operating system with live day-one payments. 90 days to a fully reconciled cutover. The controller signs off on every statement before cash moves.