GoSeedly Med Spa Kit
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.
YOUR LUMEN FRONT DESK
01 — SERIES TRACKER
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 / Series trackerOne 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.
02 / Client bookEvery client record in the selected pipeline with its interest labels, series progress, membership state, next recorded session and follow-up date. Search across clients, series, providers and interests, then open a record to make an update.
03 / Consultation queueConsultation records grouped by what is still outstanding: quoted and waiting, consulted with no quote, quoted and under way, and records with no consultation date at all. Each card carries the recorded consult date, interest labels and quoted series reference.
04 / Membership renewalsRecorded memberships grouped into renewal bands measured from the workspace date: already passed, within 30, 60 and 90 days, and later. Tier label, start date, renewal date and monthly reference sit on every row.
05 / Provider dayRecorded sessions for the selected date grouped by provider label, in time order, with the treatment series each session belongs to. Nothing here reserves a room, holds a time or prevents a double booking.
06 / InsightsSeries status mix, how far each series got, recorded membership states and session outcomes for the selected pipeline. The completion rate is completed out of completed plus no-shows, and no qualifying record gives an unavailable rate rather than an invented zero.
07 / Client record editorInterest labels, consultation date, quoted series reference, the recorded membership, treatment series with their session counts, and individual session rows. Series, membership and quote rules are checked against each other before anything is saved.
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 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.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
PLEASE READ
THE KIT, UNPACKED
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.
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 practice name, descriptor, 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 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.
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.
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
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.
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.
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.
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.