SaaS vs Custom

Recording studio (Sydney CBD, established 2019). 3 recording rooms: Room A (music/drums, isolation booths, full kit, 12-person capacity for ensemble sessions), Room B (voiceover/podcast/interview, treated acoustic, 4-person capacity, high-end condensers), Room C (post-production/mixing suite, 3-person capacity, SSL console, monitoring setup). Weekly sessions: 60–70 bookings across 3 rooms (mix of hourly, day-rate, and 4/6/8-hour packages). Revenue: $250–450/hour depending on room + engineer skill (junior engineer Room B voiceover $250/hr, senior engineer Room A music tracking $400/hr, mixing Room C $350/hr). Monthly gross: 70 sessions × average 2.5 hours × $320 = $56k/month = $672k/yr. 6 engineers (3 senior, 2 mid-level, 1 junior), hourly cost $45–80/hr (engineer pay) + studio cut 40% = engineer earning $60–120/hr depending on tier + overheads. Overhead: rent $8k/mo ($96k/yr), equipment maintenance $3k/yr, software (Calendly, Dropbox, Stripe, email) $5k/yr, insurance $6k/yr, utilities $2k/mo ($24k/yr) = $134k/yr total, margin (672k - 134k) = $538k/yr gross (80% margin ideal, 75% actual = $504k operational profit). Reality: margin is theoretical. Actual 68% because of operational friction: (1) Booking chaos (Room A (music) popular, fills Tuesdays/Thursdays, Calendly shows "available 2pm–5pm Tuesday", but spreadsheet has engineer Jake assigned same room 3pm–6pm same Tuesday via handwritten schedule nobody synced, booking system unaware, client books 2pm–5pm, engineer Jake also gets same slot from WhatsApp assignment, Tuesday arrives, Jake shows up 3pm, client mid-session, "oh sorry didn't know you were here, let me check the spreadsheet", 20 minutes of confusion, session runs over 5pm cutting into next booking, next client arrives 5:15pm to "occupied studio", reschedule, $400 lost session fee, plus client resentment, plus engineer frustration). Happens 1–2 times/month = $4.8–9.6k annual revenue loss plus reputation damage. (2) Master file delivery slow/chaotic (engineer finishes mix, exports WAV to personal Dropbox folder, sends Dropbox link to client via email, client downloads, doesn't know if final version or draft, WhatsApp messages engineer "is this the master?" engineer replies "rough draft, waiting on your feedback", client re-downloads 48 hours later, engineer pushed new version to Dropbox, client's earlier download was overwritten, client has version B not A, confusion on what's approved, no version history, revisions unclear, client asks for "revision 2", engineer doesn't know which version was revision 1 = rework, lost hours, delayed payment). Happens every session, kills productivity. (3) Engineer scheduling manual (Jake works varied hours, Monday 8 hours, Tuesday 10 hours, Wednesday 6 hours, Thursday 8 hours = 32 hours, but Friday scheduled via "can you come in?" WhatsApp at 4pm Thursday, Jake says yes, works 6 hours Friday = 38 hours. Payroll approver rounds to 40 hours, Jake loses $45 × 8 hours OT premium, or next week Jake is exhausted, assigned another 40-hour week, burnout risk, turnover. Studio has 6 engineers, informal scheduling = 3–4 untracked OT hours/week per engineer × 6 × 50 weeks = $50k/yr in unaccounted payroll or engineer dissatisfaction). (4) Client portal nonexistent (podcast producer Audio Jack: "Can I see when I'm booked for the next 12 weeks, or download my past sessions from your website?", studio says "no, you email us, we send links", Jack frustrated, "your competitor has a client portal, shows all my bookings + files, I'm switching", lost recurring client = $400/week × 52 weeks = $20.8k annual revenue). (5) Repeat packages manual (Audio Jack is a podcast producer, books "every Thursday 2pm, 2-hour session, for 12 weeks, $2,000/mo package" = 24 bookings over 12 weeks. Admin books week 1 manually Thursday, week 2 manually, week 5 admin forgets to block Room B Thursday 2pm, another client calls, books it, Audio Jack arrives, room taken, "sorry we double-booked, can you reschedule?", Jack furious, cancels package, studio loses $2k/mo × 12 weeks = $24k contract). Existing SaaS (Calendly + Stripe + Dropbox) built for: generic availability (one calendar, no multi-room awareness). NOT built for: recording studios (session multi-room coordination, engineer assignment, file versioning, master delivery approval, repeat packages with auto-booking, client portal with session history). Studio workaround: Calendly (room availability only, no engineer visibility), separate spreadsheet (engineer scheduling, manual input, no conflict alerts), Stripe (invoicing, no session data linked), Dropbox (file sharing, no version control or approval workflow), email + WhatsApp (scheduling final confirmations, redundant, error-prone), no client portal (client calls for booking history, studio manually sends). Post-event: zero analytics (which rooms underutilized, which engineers most-booked, which client segments most profitable, which time slots highest churn).

Six Core Features Custom Recording Studio Platform Delivers

1. Multi-Room Session Booking — Room Availability, Engineer Assignment, Zero Double-Books

Monday 10am: client calls "Can I book Room B voiceover session, Thursday 2pm–4pm, for podcast interview? Need Jake (senior engineer)?" Studio staff checks Calendly: "Room B Thursday 2pm available" ✓. Checks spreadsheet: "Jake Thursday... let me see... [scrolling] ... looks free". Confirms: "Yes, Thursday 2pm–4pm, Room B, Jake assigned, $600 (2 hrs × $300 voiceover rate)". Books in Calendly. Thursday: Jake shows up 2pm, client shows up 2pm, system has zero visibility that "Room B is now occupied, Block B unavailable until 4pm". Another client walks in 2:30pm thinking they can use Room C (post-production), engineer Mark is setting up monitor calibration in Room C (booked but not a real session, just maintenance), client confused, Mark annoyed, chaos. Custom system: [Monday 10am, staff opens "Session Booking" dashboard, sees: Room A (music, 12pax) — Tuesday full, Wednesday 9am–12pm free, Wednesday 12pm–6pm free, Thursday full. Room B (voiceover, 4pax) — Thursday 2pm–4pm FREE. Room C (post-prod, 3pax) — Thursday 2pm–4pm occupied (maintenance block, gray, not available). Staff clicks "Room B, Thursday 2pm–4pm", system shows: [available engineers: Jake (senior voiceover, 4.5★, $300/hr), Emma (mid-level, $250/hr), unassigned newbie intern ($150/hr but audio engineer Mark thinks intern not ready for paid clients)]. Staff selects Jake, confirms client (Audio Jack podcast), $600 locked in, system auto-reserves Room B Thursday 2pm–4pm, blocks calendar, sends Jake notification: "You're assigned: Thursday 2pm–4pm, Room B, Audio Jack interview podcast, come 15min early for mic setup." Same moment, another staff member tries to book Room B Thursday 2pm (reschedule request from different client), system says "UNAVAILABLE — Jake + Audio Jack, 2pm–4pm Thursday". Zero double-booking. Real-time sync: Jake opens engineer app (mobile + studio desktop), sees "Room B Thursday 2pm — you're on. Client name: Audio Jack. Podcast interview. Room has condenser mic + pre-amp ready." At 1:50pm Thursday, Jake walks to Room B, already set. System benefits: every room + engineer assigned = no confusion, no "wait I thought you were in Room A", no maintenance blocks clashing with revenue sessions, zero revenue-killing double-books. Multiplied: 70 sessions/week, assume 2–3 double-book attempts/month (calendar + spreadsheet mismatches) = 6–9 sessions worth of friction/month × $500 avg session = $3k–4.5k/month lost opportunity = $36–54k/yr. Zero double-books = $36–54k annual value.

2. Multi-Room Calendar Sync — Engineer Visibility, Real-Time Conflict Alerts, Fair Scheduling

Jake (senior engineer) works Tuesday–Thursday typical, but next week has two options: (A) Work Monday–Thursday (OT, 32 hours base + 8 OT) or (B) Work Tuesday–Thursday (32 hours, no OT). Current system: staff texts Jake "can you work Monday?" Jake replies "maybe, let me check my calendar", Jake has personal calendar vs studio schedule in spreadsheet = mismatch, Jake says "sure", Monday arrives, Jake forgets, doesn't show, client arrives 9am, "where's Jake?", studio calls Jake 9:15am, Jake sleeping, "oh sorry didn't realize", studio scrambles, assigns Mark (junior engineer, client wanted senior Jake for mixing) = client unhappy, session quality drops. Custom system: [Monday morning, Jake opens studio mobile app, sees "This Week" dashboard: Tuesday 9am–6pm assigned (Room A music tracking), Wednesday off (personal), Thursday 2pm–6pm assigned (Room C mixing). System auto-calculates: "You're assigned 22 hours, 0 OT this week. Want to add Monday?" Jake sees dropdown: "Monday open: 9am–12pm Room B voiceover (Mark covering, you're backup)", "Monday 2pm–5pm Room A free", "Monday 5pm–8pm Room C free (night rate +10%)". Jake clicks "Monday 5pm–8pm night shift, Room C", system locks it, updates his schedule to 25 hours, no OT, and emails studio staff "Jake added Monday 5pm–8pm Room C". Same moment, system checks: is Jake already booked another session Monday 5pm–8pm? No conflict. Is Room C available Monday 5pm–8pm? Yes. Confirm. Real-time sync: every engineer sees their own schedule + studio capacity = informed decisions, no double-books, no forgotten shifts. System prevents: (a) engineer burnout (Jake can see he's at 32 hours, adding Monday night is 5 more = 37 hours with premium pay, knows it's OT upfront, can refuse), (b) unfair scheduling (Emma has been assigned 40 hours, Jake has 22, system alerts staff "engineer workload imbalanced", staff can redistribute), (c) cascade confusion (no more "Jake thought he was off Monday, Mark thought he was on, both no-show, Mark's session prepped at 9am, sits empty until 10am when staff realizes).

3. Billing: Hourly, Day Rate, Packages, Auto-Invoicing — Revenue Capture, Transparent Pricing, Subscription Packages

Audio Jack podcast producer: "I want to book every Thursday 2pm–4pm voiceover, for 12 weeks, locked rate of $1,800/month (6 sessions × $300 = $1.8k, slight discount from $600/session standard rate)." Current system: admin manually books each Thursday in Calendly, creates recurring Stripe invoice, sends email reminder, week 6 forgets to block Room B, double-booked, package collapses. Custom system: [Staff creates "Packages" offering: 12-week recurring voiceover package, Thursday 2pm–4pm Room B + Jake engineer, $1,800/month, billed upfront. Audio Jack subscribes via client portal, pays $5,400 upfront (3-month block, billed monthly if annual = $21.6k/yr locked revenue). System auto-creates 24 bookings (12 weeks × 2 sessions = 12 sessions, 2 bookings per session for intake + confirmation = 24 touches). Each Wednesday, system auto-emails Jake + client: "Your session tomorrow Thursday 2pm Room B, confirmed." No admin effort after signup. Revenue: $1,800/mo × 12 months locked in from day 1, zero churn risk (package is paid, subscription locked). Contrast: Calendly + manual invoicing = admin overhead, easy to miss a Thursday, easy to forget reminder. System benefits: (a) upfront cash (client pays $5,400 upfront, studio has working capital immediately), (b) zero churn within package term (can't cancel mid-contract), (c) auto-booking (zero admin, 0 hours/month scheduling), (d) engineer certainty (Jake knows "every Thursday 2pm for 12 weeks, I'm booked, budgeted earnings = $1.8k × 12 weeks / 3 = $7.2k in 12 weeks = reliable income"), (e) client convenience (Audio Jack doesn't think about booking each week, shows up, recorded). System also supports: day-rate packages ("5-day recording intensive music production = $8k per day, 5-day lock, $40k upfront"), hourly ("$300/hr voiceover, billed in 30-minute increments"), mixing retainers ("2 hours mixing per week for 8 weeks = $5.6k retainer, 3 revisions included"). Multiple billing models = flexibility, upsell opportunities. Multiplied across 6 repeat clients: 6 × $1.8k/mo = $10.8k/mo locked recurring revenue = $129.6k/yr from packages alone (currently zero package revenue, all ad-hoc bookings = churn risk).

4. Master File Delivery + Approval Workflow — Version History, Draft Watermarking, Client Sign-Off

Engineer Mark finishes mixing an audio drama podcast (12 audio files, stereo 48kHz WAV, 2.1 GB total), exports to Dropbox, sends Dropbox link to client via email. Client (podcast producer) downloads, listens, sends back email "sounds good but the voice-over in episode 5 is too quiet, can you turn it up 2dB?" Mark: "ok, adjusting". Mark re-exports, overwrites Dropbox file, sends email "new version ready". Client: "wait which version is the new one?", downloads again, now has updated file, old file gone, no version A/B comparison, confusion. Custom system: [Engineer Mark finishes mix, clicks "Master Export" in studio software, system auto-processes: (1) detects file is draft status, adds watermark "DRAFT — NOT FINAL" 20% opacity across bottom of each audio file waveform display, (2) generates secure delivery link (encryption, expiration 7 days, download limit 5x), (3) creates client notification: "Your podcast mix is ready for review. [Download Link] — please provide feedback within 48 hours. Status: DRAFT (watermarked for identification)"]. Client receives email, clicks link, downloads, plays back in Podcast app (watermark doesn't interfere with playback, but if client tries to use draft file for publishing, watermark serves as warning). Client listens, responds "episode 5 too quiet, +2dB", system logs feedback as "Revision 1 — turn up episode 5 +2dB". Mark opens system, sees feedback, adjusts episode 5 file, re-exports, system creates "Revision 1 — Version B" (version history), watermarks still applied ("DRAFT — REVISION 1 — NOT FINAL"), new delivery link generated, client notified, downloads Revision 1. Client listens again, responds "perfect, approved, ready to publish." System: client clicks "Approve as Master", system removes watermarks from final files, generates "MASTER — APPROVED" certificate, encrypts files with client access token, client can download unlimited times from "Masters" folder in portal (permanent access), billing marked "paid in full" (or invoiced if on net-30 terms). Studio keeps encrypted copy for 7-year archive (legal requirement for copyright/licensing). Benefits: (a) zero version confusion (every iteration labeled + timestamped), (b) draft protection (watermark prevents accidental use of in-progress file), (c) approval trail (system logs who approved what version when, audit-proof for royalty/licensing disputes), (d) client confidence (portal shows "Approved Master" status = professionalism), (e) efficiency (asynchronous feedback loop, client doesn't have to call or email, typed notes in system, Mark sees immediately, no back-and-forth email lag). Multiplied: 70 sessions/week = 70 deliverables/week. Current system: 15–20 minutes/delivery (email back-and-forth, version confusion, rework clarifications) = 70 × 0.25 hours = 17.5 hours/week = 25% of one engineer's time wasted on delivery chaos. Custom system: 5 minutes/delivery (client downloads, approves via portal click, done) = 70 × 0.083 hours = 5.8 hours/week = 8% of one engineer's time. Savings: 70 × (17.5 - 5.8) / 70 = 11.7 hours/week engineering time freed = $45/hr × 11.7 hours × 50 weeks = $26.3k/yr engineer productivity recovered (engineer can now do more mix work, billable hours increase).

5. Engineer Roster + Scheduling — Shift Optimization, Expertise Matching, OT Tracking, Fair Allocation

Studio has 6 engineers: Jake (senior mixing, 15 years, $80/hr cost, commands $400/hr client rate, 4.8★ reviews), Emma (mid-level voiceover specialist, $60/hr cost, $300/hr rate, 4.7★), Mark (junior music recording, $45/hr cost, $250/hr rate, 4.2★), and 3 part-time weekend engineers. Current roster: Jake over-booked (40–50 hours/week, burnout risk, says "I'm thinking of quitting, too stressed"), Emma under-booked (20–25 hours/week, wants more hours, frustrated), Mark at capacity (32 hours/week, no room to grow). System has zero visibility into workload, expertise matching, or OT. Payroll manually counts hours, guesses at OT, Jake receives unexpected shortfalls. Custom system: [Staff views "Roster" dashboard: engineer availability + expertise + workload. Jake: 52 hours assigned this week (40 base + 12 OT at 1.5x = $960 OT premium), system flags "WARNING — Jake 52 hours >40 base, OT accruing, confirm with Jake?" Staff clicks link, auto-message to Jake: "You're scheduled 52 hours this week. OT = $960 extra. Accept or reduce schedule?" Jake replies "Ok but not next week, I need a break." System auto-adjusts next week to 32 hours base, redistributes Tuesday/Wednesday sessions to Emma (voiceover-skilled, can handle podcast interviews better than Mark anyway). Emma gets +8 hours, Jake gets -8 hours (rest), everyone happy, studio maintains capacity. System also shows expertise map: "This Thursday, Room A music tracking session needs senior experience (complex arrangement, 12-piece ensemble), Jake is only 4.5-hour availability, Emma has 8 hours free but does voiceover not music tracking." System recommends: "Hire weekend contractor Anil (senior music engineer, freelance $85/hr cost, available Thursday 9am–12pm), covers 3-hour gap, upsells client to senior rate ($420/hr = $1.26k session vs $320/hr junior = $960 session, uplift $300 = 31% margin increase)". Staff clicks "book Anil", Anil gets notification, confirms, session booked with senior engineer, client happy (got senior engineer at premium rate), engineer happy (Anil earns $255, premium pay), studio happy (margin increased). Benefits over spreadsheet system: (a) fairness (Emma gets visibility into why she's not booked, system shows her voiceover sessions gone to Jake by mistake earlier this month, staff acknowledges, reallocates), (b) OT tracking (Jake knows upfront his hours, can negotiate with studio, no surprises on paycheck), (c) burnout prevention (system alerts when Jake >45 hours, staff preemptively rests him, retention improves), (d) expert matching (system matches engineer skill to session type, improves output quality, client satisfaction, word-of-mouth), (e) payroll automation (system exports "Jake: 32 base hours + 8 OT hours, rate $80/hr base + $120/hr OT = $2,960 + $960 OT = $3,920 weekly" to payroll software, no manual entry, zero errors). Annual value: reduce 1 engineer turnover (recruitment + training = $20k cost), improve utilization (Emma gets +4 hours/week = $240/week = $12.5k/yr revenue uplift at $300 rate), eliminate 5 hours/week admin scheduling time × $30/hr = $7.8k/yr savings. Total: $20k + $12.5k + $7.8k = $40.3k year 1 value from roster system.

6. Client Portal + Session History — Repeat Bookings, File Access, Invoicing, Engagement

Audio Jack (podcast producer, recurring Thursday client): logs into "Client Portal", sees dashboard: [My Sessions (past 12 months): 2024 Jan — 4 sessions, 8 hours total, $2,400 spend. 2024 Feb — 4 sessions, 8 hours, $2,400. ... Dec — 4 sessions, 8 hours, $2,400. Total annual spend: $28.8k (12 months × $2,400)]. [My Files]: folder structure by month, each session tagged with date/engineer/room, click "Feb episode 3 recording session", opens folder with: (1) original raw 12-track files (archived, read-only), (2) final stereo master (approved, downloadable unlimited times), (3) edit notes (who approved, when, revisions log). [My Packages]: shows "Thursday Recurring Podcast Package — Active, Expires Dec 2024, 8 sessions remaining, $400/session". [Book Next Session]: click button, system auto-populates "Thursday 2pm–4pm Room B, Jake engineer, $600 package rate (or $1,200 if new session outside package)", confirms, books 2 clicks. Contrast current system: Audio Jack calls studio "Hi, can I book the Thursday slot again?" Staff: "Yes, what date?", checks Calendly, confirms, books manually, sends Stripe invoice, client pays, no portal history, next month client calls again, staff has no easy reference to "what did we last deliver?", has to search Dropbox folder, 10-minute hunt. Custom portal: Audio Jack sees everything in one place, books without calling, downloads past masters anytime, system becomes client's archive + convenience tool. Benefits: (a) frictionless re-booking (2-click repeat booking = higher attachment/lifetime value, client stays), (b) instant file access (no more "can you resend the master from June?" — client logs in, downloads anytime), (c) professionalism (portal screams "we're professional, your files are safe, your history is respected"), (d) data insight (staff sees "Audio Jack's 12-month usage: 48 sessions, $28.8k spend, 4.9★ satisfaction, churn risk low because package is locked", can proactively offer upgrade or renewal early). Analytics: studio can see "Top 10 clients by revenue, by session frequency, by project type", identifies high-value relationships, nurtures them (personalized email "Audio Jack, saw you've done 48 sessions with us, thanks for loyalty, here's a 10% discount code for next quarter"). Portal drives retention + upsell: estimate 5–10% revenue uplift from improved client stickiness + perceived value.

Three Rooms, Real ROI Numbers

Studio network context: 3 rooms (A music, B voiceover, C post-prod), 70 sessions/week, 6 engineers, $672k annual gross, $134k overhead. Current system: Calendly + Stripe + Dropbox + manual spreadsheet = $5k/yr software + $23.4k/yr admin labor = $28.4k annual bleed. Double-booking losses ($36–54k/yr), delivery friction lost hours ($26.3k/yr engineer time), engineer turnover cost ($20k), sub-optimal scheduling revenue loss ($12.5k) = total annual friction cost ~$95–114k/yr. Custom platform build: $95k (one-time), ops $10k/yr. Year 1 investment: $105k. Year 1 value captured: (1) Zero double-books save admin time + client friction: $36k, (2) Master delivery workflow (engineer time freed, faster turnaround = faster client payment, cash flow improves): $26.3k, (3) Engineer roster fairness/retention: prevent 1 turnover ($20k) + utilization uplift ($12.5k) = $32.5k, (4) Repeat package revenue (6 packages × $1.8k/mo × 12 = $129.6k new recurring, minus churn risk 10% = $116.6k net): gross value $116.6k (but already accounted in revenue increase, so pure margin uplift ~60% of package value = $70k new margin), (5) Admin time savings (15 hours/week → 5 hours/week = 10 hours/week saved × $30/hr × 50 weeks): $15k, (6) Client portal engagement (5–10% repeat booking uplift on $672k base = $33.6–67.2k new revenue, margin 70% = $23.5–47k new margin). Year 1 conservative total value: $36k + $26.3k + $32.5k + $70k + $15k + $30k = $209.8k. Year 1 net: $209.8k - $105k = +$104.8k net positive (break-even in 6 months, then print money). Year 2: value repeats ($209.8k) minus one-time build cost, minus 5% churn from feature issues ($10.5k), net = $199.3k pure profit. 3-year projection: Year 1 +$105k, Year 2 +$199.3k, Year 3 +$199.3k, cumulative $503.6k value vs $105k investment = 4.8x ROI, payback 6 months. Current system cost (no platform): Year 1 $28.4k (software + admin) + $95k (friction losses) = $123.4k annual bleed. Custom system: $115k year 1, then $10k/yr ops = vastly superior. Want to model your studio? Check platform pricing, or book a call to calculate ROI (current session volume, engineer count, room utilization, churn rate, repeat client packages planned).

Six FAQs

How do you prevent double-booking when two clients book the same room simultaneously?

Database-level atomic transactions. When client A books Room B Thursday 2pm–4pm (millisecond 1), system locks Room B record, checks availability (2pm–4pm clear ✓), allocates to client A, commits transaction. Client B clicks "book same slot" (millisecond 2, before transaction 1 completes), system queues request, transaction 1 completes (Room B now "booked 2pm–4pm by client A"), transaction 2 processes ("Room B 2pm–4pm now unavailable"), returns to client B "room full, available slots: 4pm–6pm Thursday, 9am–12pm Wednesday", no double-booking. Verification: load-test with 200 concurrent bookings on same time slot, confirm exactly 1 succeeds, remaining 199 get "unavailable" response. Built-in safety, no overbooking.

What if an engineer cancels a session last-minute and a client is already booked?

Escalation workflow: if engineer Jake cancels <4 hours before session, system immediately alerts studio manager + auto-searches backup engineer availability (Emma voiceover-skilled, has 2-hour open slot same time? Yes). System offers: [Manager, Emma available Thursday 2pm–4pm same room. Confirm Emma covers, OR reschedule client to Friday, OR notify client immediately?]. Manager clicks "Emma covers", system auto-assigns Emma, sends Emma notification + client email "Engineering change: Emma will be your engineer instead of Jake (both 4.9★ engineers, Emma specialized in voiceover). Same time/room." Client accepts or requests reschedule. If no backup available, system immediately notifies client "Your Thursday 2pm engineer had emergency, we're offering: reschedule to Friday 2pm same engineer (Jake back by then), or Thursday 4pm with Emma engineer, or 20% discount on session for inconvenience." Client chooses. Zero revenue loss if backup found, minimal friction if not. Engineer cancellation <4 hours = studio flags engineer (3-strike rule, after 3 cancellations engineer put on 1-week unpaid break = incentive to not cancel flippantly).

How do you handle billing if a session runs over its scheduled time?

Auto-billing rule: session booked 2 hours Room B $600 (2 × $300), scheduled 2pm–4pm. At 3:55pm, 5 minutes before end, system alerts engineer + client "5 minutes remaining, confirm end time or extend?" Engineer + client discuss, if extend to 4:15pm (+15 min), system auto-calculates billing tier (15-min increment = 0.25 hours × $300 = $75 extra), updates invoice to $675, notifies client immediately. If engineer exceeds without client consent (engineer talking over 4pm, keeps recording), system logs overage, manager reviews, applies 0.5x rate for non-authorized extension (engineer mistake, not full overage charge to protect goodwill), credits engineering time to engineer's next 6 hours as offset (engineer gets time back, learns to end sessions on time). Prevents billing disputes via real-time communication.

Can clients access their past masters forever, or do you delete files after a period?

Forever access for "Master Approved" files (client downloads rights, studio retains encrypted archive copy for 7 years per copyright law AU/APRA/AVCC requirements). Raw session files (original 24-track recording before mixing): retained 90 days post-approval (allows client revisions/tweaks after delivery), then archived offline (studio storage, not live portal, to preserve space). If client requests "I need the raw 24-track again 6 months later", system says "Available from archive, $100 retrieval fee + 2-day turnaround to restore and deliver via secure link." Encourages clients to retain their own copies of masters (best practice, client owns their content). System is guardrail, not permanent vault, but masters = forever access + client trust.

How do you manage royalty tracking (APRA/AMCOS, AVCC) if multiple engineers and collaborators worked on one track?

AU royalty compliance: system auto-logs every track recorded (metadata: date, room, engineers, session owner/client, track name, duration, session notes). At end of month, studio exports "Session Register" listing every project completed (50 voiceover gigs, 20 music recording projects, 10 mixing-only projects). Music projects include: composer/artist name, performer names (if applicable), engineer names, mix engineer names, studio notes (e.g., "Original composition vs cover vs APRA-managed"). This register is submitted to APRA-AMCOS for royalty declaration (if studio is registered digital distributor) and archived. If client is independent artist, system flags them: "Don't forget to register your compositions with APRA if you wrote this track (self-written tracks = compositional/publishing royalties handled by artist, not studio)". System doesn't calculate royalties (that's client's accountant + APRA), but ensures complete audit trail for licensing disputes. AVCC (copyright collection): system auto-tags "voiceover recording = copyright vests in client (client owns VO), studio retains tech copyright (recording session). If client republishes VO without studio credit, studio can claim derivative copyright". Log every session client name, confirms client owns output, system sends annual "Copyright Audit Trail" confirming studio is protecting all parties' interests.

What's the cost comparison: custom platform vs Calendly/Stripe/Dropbox for 3-room studio?

Off-the-shelf annual costs: Calendly ($12/mo × 12 = $144), Stripe (2.9% + 30¢ per transaction on $56k/month × 12 = $19.7k/yr transaction fees), Dropbox Pro ($22/mo × 12 = $264), manual admin (15 hours/week × $30/hr × 50 weeks = $22.5k), plus friction losses (double-booking chaos + delivery inefficiency + engineer scheduling mistakes + no client portal = $95–114k/yr lost revenue/time). Total year 1: $144 + $19.7k + $264 + $22.5k + $100k = ~$142.6k annual bleed. Custom platform: build $95k (one-time), year 1 total cost $95k + $10k ops = $105k. Year 1 value generated: $209.8k (as calculated above). Year 1 net: $105k - $209.8k value = break-even to highly profitable (platform pays for itself in 6 months from value capture). Year 2+: $209.8k annual value, $10k annual cost = 20x ROI annually. At 3 rooms, 70 sessions/week, 6 engineers, platform invests itself immediately and prints money. Want to calculate your ROI? Check platform pricing, or reach out to discuss session volume, engineer count, room utilization, repeat packages, and growth plans — we'll model your specific scenario.