CRM KitsDance studios
Every class filled. Every costume on time.
A season roster board with a recital costume tracker beside it. Barre puts the studio week, the filled places against your recorded capacity and the costumes still short of ordered on one white screen.
The week, and what the recital still needs.
Day columns of class cards, each with its level and age band labels, room, teacher first name and time, and an enrolment meter of filled places against the recorded capacity. Beside them, the recital costume tracker gives every class a five-step line and leads with the classes past their order-by date.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Season board with day columns, enrolment meters and the recital costume tracker
- Families operating view
- Classes operating view with the season class editor
- Trials and enquiries operating view
- Costumes operating view
- Recital operating view
- Insights operating view
- Three native form drafts and three editable document templates
- Editable per-family checklists and preserved row history
four pipelines
- Season enrolment · 7 stages
- Trials and enquiries · 7 stages
- Recital preparation · 8 stages
- Studio accounts · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- New enquiry
- Trial class reminder
- Trial follow-up
- Enrolment confirmed
- Waitlist spot opened
- Costume measure day
- Costume order-by date check
- Tuition past due conversation
- Recital volunteer confirmation
Inactive until you review and publish them. None send customer messages.
Forms and documents
- Trial class request
- Season enrolment request
- Recital volunteer sign-up
- Class roster sheet
- Costume order summary by class
- Recital day call sheet
Editable native forms and document templates. Forms collect information for staff review.
Sample workspace
Explore 24 fictional families holding 38 dancers across 14 weekly classes: 4 classes full with waitlists totalling 9, 6 trials inside the week, 10 classes with a costume of which 2 are past their order-by date, and 5 families past due beyond their grace days. 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
How setup works
Full installation guideCheck your Seedly
Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.
Connect the helper
Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.
Make it yours
Set studio 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 family creation, edits, the season class store and resource setup. They preserve native account permissions, unrelated custom fields and row history, enforce the season rules and the children’s data guard on the server, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
One contact-linked opportunity is one family. It holds the household label, guardians with a relationship label and a preferred-contact flag, dancers as a first name and an age band label, class places with a status, a costume step, a size label and recorded absences, the tuition plan with its recorded state and grace days, ticket reservations, a volunteer role, the enquiry and trial steps with their dates, and an editable checklist.
A dancer is a first name and an age band label. The kit stores no date of birth, no age in years, no medical, allergy or injury note, no photograph, no school name and no custody detail, and every free-text field refuses the obvious accidental entries in the browser and again on the server. That is a guard against accidental entry, not a guarantee. A costume is flagged the day after its recorded order-by date while a dancer is still short of ordered, and tuition is flagged only beyond the grace days the office recorded. There is no online registration or booking engine, no tuition billing, autopay or payments, no ticketing or seat maps, no costume vendor ordering integration, no attendance check-in kiosk, no parent portal, no automated messaging and no scheduling engine.
Four optional pipeline templates and nine inactive workflow drafts. 24 fictional in-memory families across 14 classes.
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 Dance Studio Kit
Checking access…
DevLaunch All Access
Every kit and every template.
- All 220 CRM kits for Seedly CRM
- All 270 website templates for Seedly Sites
- Every class, course, and product we release, added as it ships
- Private calls with Aaron
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?
Barre keeps its white application frame across the seven 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.
More hospitality, events & creative kits
Browse all 220 kits
