
CRM KitsYoga and Pilates studios
A week of classes. How full each one is.
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.
Seven days, and a ring on every class.
Class 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.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Weekly class grid with CSS conic-gradient fill rings, solid at capacity and thin under half full
- Intro journey strip of five step steppers with the days left on every row
- Class sheet with the class record and the roster for the selected date, and a student sheet with the attendance log and follow-up notes
- Classes, Students, Intro offers, Series and Insights views drawn from recorded workspace data only
- Black chrome Mat frame over a stone white canvas with the permission-filtered CRM tools drawer
four pipelines
- Intro offers · 8 stages
- Class series and memberships · 7 stages
- Private sessions and small groups · 7 stages
- Workshops and teacher training · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Welcome note
- First class follow-up
- Mid-offer check-in task
- Offer ending reminder
- Conversion offer task
- Series renewal reminder
- Lapsed student outreach task
- Workshop registration follow-up
- Private session booking task
Inactive until you review and publish them. None send customer messages.
Sample workspace
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.
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 company name, descriptor, the promise line, 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 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.
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.
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.
Four optional pipeline templates and nine inactive workflow drafts. Twenty two fictional classes and fourteen fictional in-memory student records.
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 Yoga & Pilates Studio Kit

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?
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.
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 health, beauty & wellness kits
Browse all 220 kits









