Serious Bizz Studios — development roadmap
Build the foundation. Automate everything else after.
Five phases, each with its own technical requirements, integrations, cost estimate, testing criteria and launch checklist. Phase 1 — the booking calendar and engineer dashboards — is the only thing being built right now.
5 phases
Roadmap
Phase 1
In build now
Phase 1
In build now
One calendar, one record
Every booking, dashboard and payment reads the same reservation record. No disconnected calendars.
Rules enforced on the server
Conflicts, prices and permissions are checked before anything is saved — never in the browser.
Approval between phases
Each phase ends at a management gate. The next phase stays off until testing is signed off.
Owner keeps control
Overrides, extensions, reward cost and every automated campaign stay under owner switches.
The Foundation
Booking calendar + engineer dashboards
One calendar for both rooms, and a real dashboard for every engineer.
Make the booking calendar and the engineer dashboards trustworthy enough that the studio can run a full week without anyone fixing a booking by hand. Nothing else is switched on until this is proven.
Already running in your app
Separate Studio A, Studio B and Whole Studio schedules
Availability is queried from every booked session on the room, so one room never hides the other.
24-hour bookable day with overnight sessions
The studio day runs 10:00 AM through 10:00 AM the next morning, so a 10 PM to 2 AM session is priced and held correctly.
Room conflict protection
The server rejects any overlapping reservation, including every date in a recurring weekly or monthly series.
Card and Cash App payments
Stripe checkout for card payments and owner-confirmed Cash App payments already settle sessions.
Email confirmations to client, engineer and owner
Booking confirmations, day-before reminders, thank-you notes and unpaid-session owner alerts run automatically.
Self-service cancel and reschedule
Members and customers change eligible sessions from their portal instead of calling the studio.
Owner override and manual booking
The owner and dispatch boards can book, reassign and settle a session outside the public flow.
Engineer portal with real assignments
Engineers see assigned sessions, room assignments and client details, plus a task list from dispatch.
Engineer double-booking protection
A booking is refused when that engineer is already busy at the same time in either room, and their booked hours close on the public calendar.
Secure engineer accounts
Engineers are invited by email, sign in with their own account, and only ever see the sessions carrying their own name.
Availability and time off
Each engineer posts the weekly hours they work and requests time off; everything outside those hours closes on the booking calendar and cannot be sold.
What this phase adds
Engineer term and permissions
Every engineer record carries a start date, end date, permission level and assignment status the owner controls.
SMS confirmations
Booking and reminder texts go to the client, the engineer and management alongside email.
Engineer assignment confirmation
Engineers acknowledge an upcoming session from their dashboard; unconfirmed sessions surface on the dispatch board.
Live calendar refresh
Both room calendars update the moment a booking lands, so two people never see different availability.
Override audit trail
Every emergency or manual booking records who made it, when, and why.
Technical requirements
- 01
StudioReservation is the single booking record. Both room calendars, the engineer dashboard and payments read from it — no parallel calendar anywhere.
- 02
The availability endpoint returns busy blocks per room and per engineer, and the calendar re-reads it on every change.
- 03
Room, engineer and recurring-date conflicts are all checked server-side inside the booking call; the UI is never the gatekeeper.
- 04
Session length is computed from absolute start and end times so overnight sessions cross midnight correctly.
- 05
Prices are calculated on the server from the studio catalog; the browser sends the choices only, never the amount.
- 06
A session counts as paid only after a signature-verified Stripe webhook or an owner Cash App confirmation.
- 07
Unpaid sessions hold the slot, then alert the owner after 48 hours instead of disappearing quietly.
- 08
Engineers are invited through platform accounts and linked to their team record on first sign-in; terms and permissions live on that record.
- 09
Bookable hours are the studio day minus that engineer’s availability, class blocks and approved time off.
Integrations
Estimated cost
Card payments
2.9% + $0.30 per charge
Existing Stripe rate — unchanged by this build.
SMS confirmations
$0 – $15 / month
Carrier email-to-text gateways are free; a paid SMS provider runs about a cent per message plus a small monthly number fee.
Engineer accounts
$0
Invitations and dashboards are part of the app; no per-seat software.
Build effort
Largest phase
Mostly tightening rules and replacing PIN sign-in — no new subscriptions.
Estimates only — confirm provider rates before committing. Platform usage and credits follow your current plan.
Testing criteria — must pass before launch
- 1
Two customers book the same room for the same hour at the same moment: the second is refused, told which slot is taken, and is not charged.
- 2
The same engineer is booked in Studio A and Studio B for overlapping times: the second booking is refused.
- 3
A 10 PM to 2 AM session is stored, priced and blocked correctly across midnight.
- 4
A recurring weekly series blocks every date in the series, not just the first.
- 5
A card payment confirmed by webhook marks the session paid; an abandoned checkout leaves no paid session behind.
- 6
A Cash App booking shows as unpaid until the owner confirms it.
- 7
Client, engineer and owner each receive a confirmation within one minute of booking.
- 8
Engineer availability, class blocks and approved time off remove those hours from the customer calendar.
- 9
An invited engineer signs in, sees only their own sessions, and confirms an assignment.
- 10
A customer cancels inside policy online and the room and engineer are released immediately.
- 11
The owner overrides an unavailable slot, the override is recorded with a reason, and the engineer is alerted.
- 12
Ten engineers and both room calendars load in one session with no crossed assignments.
Launch readiness checklist
Launch readiness · 0/8
0%Phase gate
Phase 2 stays off until this checklist is complete. The dispatch and attendance work only reads bookings that Phase 1 proves are correct.