GoSeedly Yoga & Pilates Studio Kit
A studio does not sell one thing to one person once. It sells a cheap intro offer to a stranger, and everything after that depends on two questions a pipeline cannot answer. Mat draws the whole week of classes with a fill ring on every one of them, and puts every intro student on a five step journey underneath, so the timetable and the follow through sit on one screen.
YOUR MAT STUDIO WEEK
01 — THE STUDIO WEEK
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 / The studio weekClass blocks sit in the day column and the time band somebody actually typed, so the rows are the studio’s own start times rather than an invented hour ruler. Each block carries the class name, the teacher label, the room label and a CSS fill ring showing spots taken over capacity with the count inside it. Selecting a class opens its record and the roster for that date beside the grid.
02 / Intro journey stripUnder the grid, every student who records an intro offer gets one row, ending soonest first, with a five step stepper and the days left printed beside it. First class, second class, third class, offer ends, converted. Selecting a row opens the student record, the attendance log and the follow-up notes.
03 / ClassesEvery class record in weekday and time order with its style, teacher label, room label, capacity, and the spots taken for that class on its own day of the selected week. Archived classes stay listed and marked, because attendance records point at them. This is the view that adds and edits a class.
04 / StudentsEvery student record in the selected pipeline with the start date, the intro offer, the classes attended, the active series and its remaining classes, the conversion, and the native pipeline stage. Filter to students on an intro offer, students on a series or membership, or converted students. Classes attended is counted from the attendance log, never typed.
05 / Intro offersEvery recorded intro offer ending soonest first, each row carrying the same five step stepper the week strip draws with the step it has reached named under it, the classes attended, the recorded end date, the days left, the teacher the student asked for, and the latest follow-up note. An offer that ended without a conversion is marked rather than hidden.
06 / Series and membershipsEvery student who records an active class series or membership, with the label, the classes remaining out of the total, the recorded expiry date, the days until it expires and the recorded price with its cents. Classes remaining is a number somebody wrote down, not a balance the kit decrements.
07 / Studio insightsTimetable fill by style for the selected week as ruled bars, the intro step distribution with the recorded conversion rate beneath it, the attendance status counts from the sign-in sheets, the fullest and emptiest class of the week, and recorded series price totals grouped by currency and never added across them.
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 twenty two fictional classes across the seven days in all five styles, and fourteen fictional students with one hundred and forty six attendance records between them. Six students record an intro offer and each one sits at a different step of the five, including one with nothing attended yet. Three classes are at capacity so the solid ring is visible, two are under half full so the thin ring is too, and four students record an active series. Example edits stay in the current page’s memory and reset on navigation or reload; sample students are never inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
THE KIT, UNPACKED
One student is a native contact-linked opportunity with a namespaced student record name, start date, intro offer label and recorded end date, converted flag and product label, teacher preference, an active series with its class total, classes remaining, expiry date and recorded price, student notes, attendance records and follow-up notes. The same person returning a year later with a new offer is a second record, because the offer and its outcome are the record. Other custom fields are preserved.
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 company name, descriptor, the promise line, 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 studio helper is required for connected student creation and editing, the class timetable and starter setup. It checks the active account, native permissions and the current record state, preserves unrelated custom fields and unknown values, and invokes the native Seedly mutations inside one transaction. The helper exposes no stage mutation at all, so recording attendance never moves a native pipeline card. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional, and no schema migration is required.
The timetable is a recurring weekday and start time somebody typed, held as one account-scoped record set rather than as opportunities. Selecting a class books nobody, a roster row is a record entered after the fact, and nothing reserves a spot, holds a place, promotes a waitlist or prevents a double booking. Spots taken counts the recorded booked and attended places for that class on that date; a late cancel freed the spot and a waitlist place never had one, so neither takes one. Classes attended is derived from the attendance log and never stored. The intro step is one shared rule used by the strip, both tables, the insights and the server’s own reading of a record. A recorded series price is a reference in integer minor units: it is never written into native opportunity value, it charges nobody, and there is no invoice, card, direct debit, refund or revenue recognition anywhere. A teacher label is text, so the kit computes no hours, rate, per-head pay or timesheet and assigns nobody to anything. Nothing connects to a watch, a ring, a strap or a health platform, and a prenatal class is a class name on a timetable: the kit records no condition, injury, clearance, consent or clinical note and makes no health or medical claim. Attendance records and follow-up notes are archive only, there is no delete anywhere in the kit, and empty values read as words rather than a dash.
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.
Mat keeps its studio navigation on the canvas across the original studio views and the native CRM modules. Full CRM tools remain available within the same signed-in account and application theme. 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.