Skip to content
View packages

CRM KitsMusic lesson schools and music studios

Every slot on the grid. Every open minute in sight.

A teacher week grid for music lesson schools: teachers as rows, the day in 15-minute slots, every weekly lesson, make-up and trial placed by time and every open stretch of 30 minutes or more drawn as open time. Metronome keeps students, make-up credits, trials, recitals and next term's re-enrollment in one connected workspace, with students kept to a first name and an age band.

Schedule in the GoSeedly Music Lesson School Kit with fictional sample records

Teachers by time slot.

Households with an alert lead, then the term and week, day tabs with lessons and open minutes, and the day grid: lessons, make-ups and trials placed by time, open slots outlined and clashing slots flagged in words.

Actual interface captures with fictional sample data. Open a screenshot to see it full size.

What’s in the kit

Screens

  • Teacher week grid with lessons placed by time, open slots and slot clashes flagged
  • Term calendar that decides which weeks have lessons
  • Students kept to a first name and an age band, with a guardian for minors
  • Make-up credits with expiry and booking
  • Trial outcomes and next-term re-enrollment
  • Recital performer lists
  • Teacher cards and insights ledgers in separate units
  • Three native form drafts and three editable document templates
  • Editable household checklists and a guard against children's data, access codes, card numbers and Social Security numbers

four pipelines

  • Lesson inquiries · 8 stages
  • Term re-enrollment · 7 stages
  • Recitals and showcases · 7 stages
  • Adult students · 7 stages

Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.

nine workflow drafts

  • Trial preparation
  • Trial outcome follow-up
  • Slot offer
  • First month check-in
  • Re-enrollment question
  • Re-enrollment reply review
  • Recital pieces
  • Recital program review
  • Adult progress check

Inactive until you review and publish them. None send customer messages.

Forms and documents

  • Trial lesson request
  • Make-up lesson request
  • Term re-enrollment reply
  • Weekly slot confirmation
  • Recital running order
  • Term practice notes

Editable native forms and document templates. Forms collect information for staff review.

Sample workspace

Explore 20 fictional households with 33 students, 30 weekly slots, 5 teachers, 3 terms, 8 make-up credits and 16 recital entries. Sample edits stay in memory and reset on navigation or reload.

No sample customers are added to your CRM.

Setup and source

  • Guided setup and compatibility report
  • Private rollback receipt
  • AI-agent guide for customized installations
  • Original editable source, configuration, and tests
Read the installation guide
  1. Check your Seedly

    Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.

  2. Connect the helper

    Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.

  3. Make it yours

    Set school name, descriptor and default pipeline name. Then sign in and check the workflows and permissions your team uses.

Technical details and compatibility

Seedly CRM 5.8.4 · extension API 1. Node.js 20 or newer. The installer checks supported integration-file versions and does not deploy your web app or backend. The included original backend helpers are required for connected household creation, edits, teachers and terms, and resource setup. They preserve native account permissions, unrelated custom fields and row history, refuse dates of birth, exact ages, school names, medical details, access codes, payment card numbers and Social Security numbers, require a guardian for students under 18, and check revisions before saving. The native form patterns are built from the same rules. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.

One contact-linked household holds the parent or guardian, contact note, recorded tuition and next-term re-enrollment, its students as a first name, age band and instrument, weekly lesson slots with teacher, weekday, time and minutes, make-up credits with expiry and booking, recital entries and an editable household checklist. Teachers with their teaching hours and the term calendar are the school's own record.

Everything shown is what the office recorded. The kit does not book lessons online, sync calendars, assign or move slots, track attendance beyond recorded make-up credits, take payments, invoice or charge late fees, calculate lesson rates or teacher pay, grade students or certify levels, sell recital tickets or send messages. It stores no date of birth, exact age, school name, medical or allergy detail or photograph.

Four optional pipeline templates and nine inactive workflow drafts. 20 fictional in-memory households.

Calling, messaging, signing, payments, and external integrations depend on your Seedly installation, account permissions, plan, and configured providers. Screenshots use sample data and reference imagery. Hosting, installation, and ongoing maintenance are your responsibility.

Get the Music Lesson School Kit

Checking access…

DevLaunch All Access

Every kit and every template.

See DevLaunch All Access

Already a member? Open your downloads.

Questions

How do I receive the kit?

Purchase securely through Whop. Your original source ZIP and installation documentation are delivered manually to the email used at checkout. This is a one-time purchase of this kit; Seedly software, hosting, and installation services are separate.

Does this include Seedly CRM?

You obtain and configure Seedly separately. The kit adds original frontend screens, a shared theme, starter definitions, and integration instructions. It does not include Seedly’s codebase, license, hosting, or a separate CRM database.

Is this one connected workspace?

Metronome keeps its violet-ink canvas, top bar and staff band across the kit views and the native CRM tools in the same signed-in account. Contacts, Calendar, Estimates, Documents, and other full modules retain the functionality supplied by your own Seedly installation. Existing authored content and provider screens retain their own layouts.

Can I use it with existing customizations?

Yes, with a compatibility review. The installer checks the supported integration files. Changed integration files need a reviewed merge; the included AI-agent guide explains how to preserve custom extensions, permissions, providers, and routes.

Do I have to import all the starter content?

No. Choose individual pipelines and workflow drafts, use a compatible existing pipeline, or install none. Workflows remain inactive until reviewed and published. They use native triggers, internal tasks, optional notes, and timed waits. A wait does not verify task completion or recheck the current stage. The included drafts do not send customer messages.

Can I remove the examples and starter content?

Sample records stay in memory and never create customers in your CRM. Leave sample mode to return to your account. Starter setup lets you review removal of unused kit additions; server checks retain edited or published workflows and pipelines with live work or references. Removing the frontend does not delete account records.

Can different subaccounts use different kits?

The current design and branding apply to the whole web installation. Subaccounts still separate data and access. Use a separate web installation for another full-interface kit; running different kit designs by subaccount in one installation requires additional customization.

Browse all 220 kits

Customer experiences / Trustpilot

What customers say
about DevLaunch.

Read all reviews on Trustpilot ↗

Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.