GoSeedly Dance Studio Kit
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.
YOUR BARRE SEASON BOARD
01 — SEASON BOARD
Actual interface captures with fictional sample data. Open a screenshot for a closer look.
TAKE A CLOSER LOOK
One connected workspace, with views built around the decisions your team makes each day.
01 / Season boardDay 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.
02 / FamiliesHousehold label, dancers by first name and age band, classes enrolled, guardians with the preferred contact, the tuition plan and its recorded state, ticket reservations and volunteer role. Families past due beyond their recorded grace days lead the ledger.
03 / ClassesOne roster per class with every enrolled, waitlisted and trial dancer, the household behind them, the costume step, the size label and attendance as recorded absences only. The season classes themselves are edited here.
04 / Trials and enquiriesEvery enquiry with its step, the class of interest with its day and time, the recorded enquiry and trial dates, whether the trial falls inside this week, and how many follow-up attempts the office has made.
05 / CostumesThe same five steps per class and per dancer, with sizes as plain labels, the vendor and the order-by date. A class past its order-by date with a dancer still short of ordered says so in words, in red, with its own marker.
06 / RecitalThe running order as class entries with dancers on stage, the rehearsal call time recorded against each entry, and the volunteer roles and ticket reservation counts the office wrote down beside them.
07 / InsightsFamilies, dancers by age band, classes full, trials this week and the recorded costume step on every enrolled place, each one a filter over the ledger below it.
YOUR PROCESS, YOUR STARTING POINT
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
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.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
MORE OF THE WORKING DAY
Editable native forms and document templates give your team a practical starting point.
Choose forms individually in Setup & resources, then customize and publish them in the native form builder.
Open each template in Documents and complete it for the actual job or visit.
Record progress and notes in the kit’s operating views. Keep earlier rows by archiving them, and retain the context for the next person.
Forms collect information for staff review. They do not automatically change the kit’s custom records. Repeating setup preserves existing resource edits.
THE KIT, UNPACKED
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.
FROM KIT TO CONNECTED WORKSPACE
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
Deploy the included helper from your authoritative backend source before connected edits. Build your web app, then choose any optional pipelines and drafts you need.
Edit studio name, descriptor and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.
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.
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.
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.
DEVLAUNCH ALL ACCESS
DevLaunch All Access includes every GoSeedly CRM kit, all 195 available today, along with every class, course, and product we release, and private calls with Aaron.
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
Want more than one kit? All Access covers the whole CRM kit library and the rest of what we make. See everything it includes on the All Access page.
See DevLaunch All AccessAlready a member? Open your downloads.
For your own compatible Seedly CRM. Seedly software, hosting and installation services are separate. Each full-interface kit uses its own web installation.
BEFORE YOU MAKE IT YOURS
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.
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.
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.
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.
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.
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.
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.
Find a workspace that fits the way you work.
Explore all CRM kitsCustomer experiences / Trustpilot
Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.
We use essential storage to keep the site working. With your permission, we also use analytics and the Whop Pixel to understand visits and advertising results. Optional analytics stay off until you choose.
Read our Cookie Policy and Privacy Policy.