006:30Open
Fitness studio
One booking system. Four different views.
Build a scheduling app once. Your front desk needs today's calendar. Your trainers need their personal schedule. Clients need to book appointments. You need the revenue dashboard. ShapeKit lets each user shape what they see without you rebuilding it four times.
The problem
You built a solid booking system with all the core features: calendar, client list, trainer schedules, invoicing, activity logs. But now your team is frustrated. The front desk assistant needs a quick glance at today's schedule. Your trainers want to see only their appointments. Clients are confused by options they don't need. The owner wants a revenue dashboard nobody else should see.
You could build four separate interfaces. You could add a settings panel and feature-gate everything. Or you could spend the next month maintaining checkbox configs. There has to be another way.
How it works
Front desk: Today's schedule
Your receptionist says, “I just need a simple view of who's coming in today and when they arrive.” AI generates a clean calendar focused on arrivals, no trainer details, no client contact info. They get what they asked for.
Trainer: Personal schedule
Your trainers want to see only their sessions, client names, and notes. Not the full database. Not billing. Just their day. AI builds that view on the fly.
Client: Book and manage
Clients can browse available slots, book, reschedule, and cancel. They never see your internal data. AI generates a client portal that's clean, focused, and doesn't expose anything you don't want them to know.
Owner: Revenue dashboard
You want monthly revenue, upcoming bookings, trainer utilization, and churn signals. You build this once, let it shape itself, and you get the business metrics without writing custom queries every quarter.
Skills you use
Bookings
Schedule, reschedule, and cancel appointments.
Contacts
Manage client profiles and trainer details.
Dashboard
See what matters to each role at a glance.
Invoices
Generate and track payment records per session.
Why it matters
- You ship one booking system. Four teams get four tailored views.
- No more “can you add a column for my role” tickets.
- Front desk, trainers, and clients each see only what they need.
- Data stays safe. Clients never see revenue or internal notes.
- Scaling doesn't mean rebuilding. Add a new trainer type? They describe their view. AI builds it.
- Your business rules stay in one place. Views adapt to them, never the other way around.
Ready to stop rebuilding booking systems?
Start with your data layer. Let ShapeKit handle the rest.