A massage practice runs on rooms, therapist hours and prepaid packages that quietly run out. Knead lays the treatment rooms out as horizontal lanes under one 9 am to 8 pm axis and draws every appointment as wide as its recorded duration, so a 90 minute session is visibly half again the width of a 60 minute one and the gaps are the gaps.
Four room lanes under one hour ruler. Each appointment sits at its recorded start time and is drawn to the scale of its recorded duration, carrying the client, the modality and the therapist label. A hatched band between two recorded appointments in one room is the turnover time, labelled with its minutes. Every lane head carries the room, the minutes recorded in it against the 660 the axis covers, and the next client in that room: their package balance as filled and hollow pips, as a count above twelve sessions or as the words “No package recorded”, and whether their intake form is on file.
Selecting a block opens the client beside the day book: the preferred therapist, the pressure preference, the focus areas as labels, the intake flag with its recorded date, and the staff notes. Then the package with its pip row and its total, used and remaining counts, the whole appointment log including archived rows, and the follow-ups. The pipeline stage control beside it is the native CRM’s.
The preferred therapist, the pressure preference, the intake flag, the package label, the recorded balance and the next booked appointment, filterable by pressure preference. Native opportunities that carry no massage therapy details yet are listed separately and counted nowhere, so a number on this page is always a number somebody recorded.
Every non-archived appointment across the loaded clients, grouped into a ruled band per recorded date with the newest date first. Start time, client, modality, therapist, room, length and recorded status from booked, completed, no show and late cancel, filterable by status.
The clients recording a package, ordered by the fewest sessions remaining and then by the earliest recorded expiry, so the renewal conversation and the package about to run out are the first two rows. A depleted balance is marked on its own rather than counted as a low one, and the clients recording no package at all are counted separately instead of shown with an empty balance.
The clients whose intake flag is not recorded as on file, ordered by the next booked appointment with how many days away it is. An unticked flag always means nobody recorded a form, because the flag and its date require each other. The clients already on file are listed with the date somebody filed it.
Recorded appointment statuses as a ruled count, modality labels and therapist labels as ruled bars, the minutes recorded in each room against the 660 the axis covers, the package balance split with low, depleted, expiring and expired counted separately, the intake split, and recorded package price totals grouped by currency and never summed across them.
YOUR PROCESS, YOUR STARTING POINT
Useful structure. Only what you choose.
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
01 / FOUR PIPELINES
Choose your starting structure.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
New client intake · 8 stages
Package renewals · 7 stages
Corporate and event chair massage · 7 stages
Gift certificates and referrals · 7 stages
02 / NINE WORKFLOW DRAFTS
Give the next step a shape.
Intake form request task
First appointment follow-up
No-show follow-up
Two sessions remaining task
Package expiring reminder
Renewal offer task
Six-week rebook check-in
Corporate event confirmation task
Gift certificate redemption note
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
03 / SAMPLE WORKSPACE
Explore before adding records.
Explore eleven fictional clients in the separate sample view. Fourteen appointments are recorded on the workspace day across all four rooms and three therapist labels, in 60 and 90 minute blocks: ten individual clients with one each, and a corporate chair massage account whose four back-to-back appointments fill Room 4. Four clients record no intake form, three record a low package balance, one records a package expiring within 30 days and one is already depleted and expired. Example edits stay in the current page’s memory and reset on navigation or reload; sample clients are never inserted into your CRM.
No sample customers are inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
PLEASE READ
A front-desk workspace, not a medical record.
This kit is not a HIPAA compliance product and does not make a practice HIPAA compliant. It is not an EHR, EMR or practice management system.
It is built for relationship work: recalls, reminders due, follow-up, intake progress and front-desk tasks. Clinical notes, diagnoses, prescriptions, test results, insurance details and other protected health information belong in your clinical system, not here.
You install the kit on your own Seedly CRM. DevLaunch does not host, receive or process your patient data. Your practice decides what it records in its CRM and is responsible for its own privacy, security and regulatory obligations, including any agreements with its hosting and software providers.
THE KIT, UNPACKED
Your workspace. Your starting point. Your code to edit.
One client is a native contact-linked opportunity with a namespaced preferred therapist label, pressure preference, up to eight focus area labels, an intake flag with its recorded date, staff notes, a fixed six-key package object, appointment rows and follow-up rows. Two people in the same household stay independent records, because the package, the form and the pressure preference belong to a person. Other custom fields are preserved.
Four-lane room day book where block width is recorded duration, with CSS turnover hatching and a current time rule
CSS package pips and intake flags on every lane head, with a numeric fallback above twelve sessions
Client sheet with the client record, the package, the full appointment log and the follow-ups
Client book, appointment log, package balances and intake desk views
Practice insights drawn from recorded workspace data only
Charcoal and fuchsia Knead application frame with the permission-filtered CRM tools drawer
Four optional pipeline templates and nine inactive workflow drafts
Eleven fictional in-memory clients with recorded appointments, packages, intake flags and follow-ups
Guided setup, compatibility report, and private rollback receipt
AI-agent documentation for customized installations
Original editable source, configuration, and tests
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
02
Connect the required helper.
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.
03
Set up your own team.
Edit practice name, descriptor, and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.
Compatibility and operational details
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 massage therapy helper is required for connected creation, editing 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. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional, and no schema migration is required.
An appointment row is something the desk typed. It reserves no room, holds no therapist, checks no availability, creates no native Calendar event and sends no confirmation, and there is no online booking or scheduling engine. Sessions remaining is derived from the recorded total and used counts and never stored, so the pips and the tables cannot disagree with the record; sessions used is deliberately not reconciled against completed appointments, because a client can arrive with sessions already drawn down and the desk decides whether a late cancel consumes one. Two clients may record appointments that overlap in one room: the lane splits into stacked sub-rows and the overlap is marked "Double booked" rather than refused, because the kit reserves nothing. Staff notes are a plain note the desk keeps, never a chart, a SOAP note or a clinical opinion, and the kit holds no intake form content, health history, consent record, insurance field or medical claim. Package prices are recorded references, separate from native opportunity value, invoices and payments; nothing is charged and no session is redeemed automatically. Empty values read as words, never a dash, and counts are pluralized against their own value.
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.
Checking access…
DEVLAUNCH ALL ACCESS
Every kit. And everything else.
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.
All 195 CRM kits
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
Every class, course, and product
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Private calls with Aaron
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
DevLaunch All Access
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.
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
Good questions. Clear answers.
Is this kit HIPAA compliant?+
No, and it does not claim to be. It is not a HIPAA compliance product, an EHR or a practice management system, and installing it does not make a practice compliant. It is a front-desk and relationship workspace for recalls, reminders, follow-up and intake progress. Keep clinical notes, diagnoses, prescriptions, test results, insurance details and other protected health information in your clinical system. The kit runs on your own Seedly CRM; DevLaunch does not host, receive or process your patient data, and your practice remains responsible for its own privacy, security and regulatory obligations.
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?+
Knead keeps its day book navigation across the original massage therapy 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.
Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.
Your privacy, your choice.
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.
01 / Room day book
