Angeles One

Each system served a purpose. Opus1 tracked students and lessons. Webflow powered the marketing site and prospect forms. Google Sheets handled reporting and reconciliation. AppSheet managed internal workflows. Zapier tried to wire them all together.

On paper, it worked. In practice, staff toggled between five logins daily. Data lived in five places, and keeping it synchronized meant hours of manual reconciliation every week. When a parent called, no one had the full picture without checking multiple systems. When the team wanted performance numbers, someone had to pull data from three tools and assemble a report by hand.

The deeper problem was structural. Generic CRM platforms don't understand music education. The relationships are unique: parents are account managers for their children. A single family might have a parent managing three children, each studying different instruments, with different instructors, at different locations, on different schedules. Students get matched to instructors by instrument, location, and availability. Enrollments involve 16 discrete steps covering contact details, instrument selection, lesson scheduling, payment processing, and policy acknowledgment. Withdrawals can be partial (dropping one lesson while keeping another) and need billing deadline logic, feedback collection, and automated cleanup of downstream records.

No off-the-shelf tool models this. So the staff worked around limitations instead of through streamlined workflows. Every workaround was time spent on the software instead of on the students.

Angeles Academy needed software that understood their business at a structural level. Not a CRM with a "students" field bolted on. A system where the entire data model, every table, every relationship, every workflow, was designed around how music education actually operates.

The data model we built spans 25 PostgreSQL tables across 95 migrations. Clients carry role flags (is_student, is_account_manager, is_dependent) that aren't mutually exclusive. A parent is an account manager. Their children are dependents and students. The client_relationships table models these connections explicitly with AccountManagerOf and DependentOf relationship types, complete with primary flags and date ranges. When you open a client profile, you see their family grouped together: the parent's account with each child's lessons, instructors, and enrollment history nested underneath.

Lessons are first-class entities, decoupled from enrollments. Each lesson tracks its own lifecycle (Active, Paused, Cancelled, Withdrawing) with its own instructor assignment, schedule, instrument, level, and tuition. A student can have multiple concurrent lessons. Pausing one doesn't affect others. Withdrawing from one triggers its own feedback flow while the rest continue. This granularity was impossible in the old system.

The enrollment pipeline models the actual intake call. When a parent calls to enroll three children, the staff member walks through a 16-section guided form: student type (Adult or Child), contact information with existing client search, instrument selection with admin-configurable scripts that change dynamically based on student type and proficiency level, studio location (Brentwood, Westwood, Tarzana, or Online), availability grid, lesson scheduling, instructor matching, pricing with discount support, policy acknowledgment checkboxes (tuition, makeups, substitutes, calendar), Stripe payment collection, and staff assignment. One atomic API call creates the account manager, all student records, all family relationships, all lesson records, all enrollment records, and all activity events. If anything fails, everything rolls back.

Communication tracking is truly unified. RingCentral integration captures every phone call, SMS, and voicemail via webhook subscriptions that auto-renew every 6 days. Gmail API integration polls three location inboxes (brentwood@, info@, and tarzana@angelesacademyofmusic.com) every 60 seconds using a service account with domain-wide delegation and history-based polling via SSM Parameter Store. Every communication is automatically matched to a client record by phone number or email address, normalized to E.164 format. Unmatched communications surface in a triage view. And every communication, whether it's a 30-minute phone call or a quick email, gets an AI-generated summary via AWS Bedrock so staff get context in seconds.

This level of domain specificity doesn't exist in generic software. It had to be built.

The activity feed is where everything comes together. Every client profile has a unified timeline that merges internal staff actions with external communications into one chronological view. When you open a client's profile, you see the complete story: when they were created as a prospect, every phone call and email exchange, when their manager was changed, when their child was enrolled, every instructor change, every note added, every lesson created or modified, and every withdrawal initiated or completed.

The system tracks over 20 distinct activity types. Internal actions like client_created, client_enrolled, managed_by_change, instructor_change, relationship_added, lesson_created, lesson_upgraded, lesson_downgraded, and withdrawal_initiated are logged automatically whenever staff take action anywhere in the platform. Each activity event records who performed the action, which staff member was involved, the previous and new values for any change, and structured metadata in JSONB for rich context.

Communication events from RingCentral and Gmail flow into the same timeline. A phone call shows the duration, direction, caller ID match, and AI summary. An email shows the subject, body preview, and which inbox it came through. SMS messages and voicemails each have their own transformer handling the specific data shape from their source system. The result is that when a parent calls about their child's lesson, the staff member sees not just the call history, but every enrollment change, instructor swap, note, and withdrawal attempt in one scrollable feed.

This is the kind of integration that falls apart with disconnected tools. When communications live in RingCentral, notes live in a CRM, and enrollment changes live in a spreadsheet, nobody has the full picture. Angeles One puts everything in one place, automatically, with zero manual data entry.