Straight answers.

Yes — the platform has no per-seat caps and runs for clubs from single-instructor operations up through multi-location organizations. Our design-partner gym is a mid-sized gymnastics club and the architecture is multi-tenant from day one.

For a new club starting fresh, onboarding usually runs in days — provision the tenant, configure programs, point Stripe Connect at it. Migrating from an existing platform takes weeks because we walk through your data with you. Either way, you're not doing it alone.

Yes. Onboarding includes walkthroughs of the parts of the platform your team will live in. Most front-desk staff are comfortable within a session or two — the UI is designed around how clubs actually work, not a generic admin schema.

Yes, via CSV import for the standard tables (members, athletes, memberships, programs, enrollments, payment history). We do this together — you export, we map it, we walk through edge cases before anything goes live in your tenant.

Yes. Most clubs do — they run both during a billing cycle to validate the cutover before turning the old system off. We design the migration plan around that.

We import it. Past payment history, prior enrollments, attendance history — all of it. Anything we can't import gets explained in the migration plan before we start.

You do. Full stop. We're the operator of the platform; the data is yours.

Yes. Standard exports for members, enrollments, attendance, payments, and orders are built into the manage app as CSV. A full database export is available on request.

You get a full export. We retain the database for 30 days post-cancellation in case you need to restore or pull additional data, then it is permanently deleted.

Yes — structurally. Every tenant runs in its own isolated Supabase project (separate database, separate connection). Tenants don't share a single multi-tenant table with a tenant_id column — they don't share a database at all.

It does the same things staff can — answer schedule questions, book trials, dispatch password resets, take messages — but for the calls that come in after-hours or while staff is on the gym floor. It is not a replacement for staff; it is a way to stop staff from being interrupted eight times an hour by the same questions.

On complaint, financial dispute, or any time the caller says they want to talk to a person. Also on high-tier actions like refunds where the verification level required exceeds what the AI is allowed to handle alone.

Yes. The AI is grounded in your tenant's data — your real class schedule, your programs, your prices — and on a knowledge base you maintain in the manage app. Update an article, the next answer reflects it. No retraining cycle, no redeploy.

A 4-digit support PIN. Members set theirs in the profile area. The voice + SMS + chat receptionist uses a tiered verification ladder — public info is answered freely, account-specific actions require the PIN, and high-tier actions (refunds, payment method changes) require the PIN plus matching context.

We talk pricing in the demo. The right configuration depends on how you run — billing model, channel mix, AI usage — and we'd rather model it against your actual numbers than quote you something that doesn't fit.

No multi-year lock-ins. Month-to-month is the default. The conversation about adjusting your configuration is welcome any time.

Through Stripe Connect. You connect a Stripe account, money flows to you directly — we never custody funds. Processing fees are passed through at cost from Stripe.

Yes. Tenants can run in a cash-only mode where payments are recorded manually and no Stripe integration is required. Alternative processors are on the roadmap.

Yes. Primary + secondary users per membership, each with their own login and per-action permission flags. The primary controls what the secondary can see and change.

Yes. Per-user Stripe customers under one membership, with billing routing — Mom's saved card pays for Saturday class, Dad's pays for Tuesday. Both show up in the membership's billing history with the correct "charged to" label.

Receipts, payment notifications, and consent-related emails are CC'd to both parents by default. Each user controls their own per-channel opt-in (email, SMS, push, in-app) from their profile.

Yes — PIN-only login on a separate /athlete portal. Parents enable it from the membership profile with explicit COPPA-compliant consent stamped at enable time (IP, user agent, consent snapshot). Off by default.

Per-program waivers — each program can require its own. Renewals re-prompt if the policy text has changed. Medical fields are staff-only by default.

Not today. The underlying controls a SOC 2 audit would look for — access logs, encryption at rest, environment separation, change management — are in place; the formal report is not yet completed. Happy to walk through a security packet with your IT team.

We do not handle card data. Stripe Elements collects and tokenizes card numbers in the browser; we store Stripe tokens, not the card numbers themselves. PCI scope offloads to Stripe.

Supabase Postgres, US-region. Each tenant in its own project. Encrypted at rest and in transit. Daily automated backups; manual pg_dump on request.

Per-user data export and erasure flows live in the manage app. Right-to-be-forgotten requests are processed through an audit-logged delete that retains records of what was removed, not the data itself.