Meet Melody
An autonomous AI studio manager that keeps teacher schedules full, students on the calendar, and revenue flowing — without anyone lifting a finger.
What does Melody actually do?
Melody runs a continuous autonomous loop over the studio's CRM. Every 30 seconds she scans the schedule, detects operational gaps, and acts on them — no prompt required.
Reads all upcoming lessons, teacher availability, cancellations, and student history from the CRM.
Finds makeup opportunities (missed lessons), churn risks (3+ consecutive misses), inactive students (no lessons in 14 days), and freed slots from cancellations.
Ranks each opportunity with a weighted formula: Revenue × 1.0 + Retention × 0.9 + Utilization × 0.8 + Parent Convenience × 0.5.
Sends a personalized outreach message via SMS, email, or in-app — then logs the action to the CRM so it won't send twice.
When a cancellation comes in, Melody instantly checks the waitlist. If there's an exact-match student, she auto-books them and notifies the guardian within seconds.
What decisions does Melody make on her own?
Who to contact and when
Melody decides which students to reach out to based on their lesson history, churn risk score, and waitlist status — prioritizing the highest-value opportunities first. She respects a 2-message-per-household-per-week throttle automatically.
Whether to auto-book or just offer
If a cancellation matches a waitlisted student exactly (same teacher, instrument, and time preference), Melody books the slot immediately without asking anyone. If there's no exact match, she sends an offer and waits for a response.
How urgent the outreach tone should be
Melody drafts different messages depending on context: a gentle check-in for a student who hasn't been in two weeks, a retention-focused message for someone at churn risk, and an urgent "slot just opened" message for a same-day cancellation. The Anthropic SDK optionally enriches these messages with LLM-generated personalization.
Where does Melody break down or hand off?
No two-way conversation
Melody sends outreach but can't yet parse a reply. If a parent texts back "Tuesday doesn't work," a human still needs to follow up. The next step would be a Podium Inbox webhook to feed responses back into the loop.
No payment or contract handling
Melody can book a lesson, but she can't collect a deposit or send an enrollment agreement. That's a natural handoff to Podium Payments.
Teacher judgment calls
When a student has 6+ consecutive no-shows or needs a placement assessment, Melody flags it as an escalation and surfaces it to the owner — she doesn't guess on edge cases that require a human conversation.
What we'd build next
Two-way SMS replies via Podium webhooks · Stripe payment collection on booking confirmation · A/B message testing with outcome tracking · Teacher schedule optimization across multi-location studios
Anything else you want judges to know?
This is a real problem. The average music studio runs at 65% teacher utilization. Two missed lessons per teacher per day × 5 teachers = $600/week in evaporated revenue. Melody targets that gap specifically.
The ROI is obvious. At $149/month, Melody pays for herself by recovering a single lesson. The math: one recovered 60-min lesson = $65. One recovered churn risk = $8,400 in lifetime student value.
Avery gets customers in the door. Melody keeps them on the calendar. This isn't a replacement — it's the vertical layer that Podium's horizontal AI can't do alone. Instrument-teacher matching, sibling household throttling, recital-prep scheduling — these are music school problems that require music school context.
The demo is live. Go to /melody, click ▶ Run Melody, and watch the action feed populate. Then go to /melody/simulate to fast-forward a full month in 8 seconds.
40%
Autonomy weight in judging
15.7×
ROI for studio owner
$8,400
Student LTV protected per churn risk
< 2s
Melody responds to a cancellation