CRM KitsMed spas & aesthetics
Every series on track. Every membership renewed.
A med spa sells consultations, treatment series and memberships. Lumen puts all three on one white canvas under a deep plum bar, so the front desk can see how many sessions are left and when the next membership renews without opening a single record.
Sessions left, in one look.
One row per recorded treatment series. A filled dot is a session the desk recorded as done, a ringed dot is the next scheduled one, and a hollow dot is still to come. The package price reference and the next recorded date sit beside every strip.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Series tracker with a session dot strip on every recorded series
- Searchable client book with interest labels and membership state
- Consultation queue grouped by what is still outstanding
- Membership renewal bands measured from the workspace date
- Provider day and insights drawn from recorded workspace data
- Deep plum Lumen application frame with full CRM tools
four pipelines
- Consultation to series · 8 stages
- Treatment series · 7 stages
- Membership renewal · 7 stages
- Referral and events · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Consult prep note
- Quote follow-up task
- Series start note
- Mid-series check-in task
- Series completion follow-up
- 60-day renewal task
- Lapsed membership outreach
- Referral thank-you note
- Event follow-up task
Inactive until you review and publish them. None send customer messages.
Sample workspace
Explore ten fictional client records with ten treatment series, 35 recorded sessions and recorded memberships in the separate sample view. Example edits stay in the current page’s memory and reset on navigation or reload; sample records 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
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.
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 practice name, descriptor, 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 med spa helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, checks the current record state before saving, and exposes no stage mutation of its own, so stage changes stay on your CRM’s own move. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
A client record is a native contact-linked opportunity with namespaced interest labels, a consultation date, a provider label, a quoted series reference, a recorded membership, follow-up notes, treatment series rows and session rows. Package, quote and monthly figures are recorded planning references, separate from actual billing and payments.
Lumen is a front desk and sales coordination workspace, not a clinical or patient health record. It has no field for treatment notes, dosages, product lots, medical history, consent forms or photographs, and it makes no HIPAA or other compliance claim. Sessions and series counts are staff-entered records: they reserve no room, create no native Calendar booking, prevent no double booking and send no reminder. Provider labels do not assign staff. Memberships are records, not billing: nothing is charged, collected or renewed by the kit.
Four optional pipeline templates and nine inactive workflow drafts. Ten fictional in-memory client records with ten series and 35 recorded sessions.
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 Med Spa 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
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?
Lumen keeps its workspace navigation in a single plum bar across the original med spa views and 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
