GoSeedly Acupuncture Clinic Kit
A front-desk workspace for acupuncture clinics: each patient's visit package drawn as a string of beads you can count, the day's visits by room, recalls that come due and the practices that send people your way. Stillroom keeps series, the day book, packages, recalls and referrals in one connected workspace, and it is not a medical record.
YOUR STILLROOM WORKSPACE
01 — SERIES
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 / SeriesEach patient with an open package is a row of beads, one per visit: filled when attended, a ring with its date when booked, hollow when not booked yet, with the expiry date and the next visit beside it. New inquiries without a first visit, packages ending soon or expired with visits left, overdue recalls and missed visits not rebooked lead in the needs attention strip.
02 / Day bookA seven-day strip and, for the chosen day, one column per room label with visits in time order: time, minutes, patient, visit kind, status in words and which visit of the package it is.
03 / PatientsPatients in a series, between series, new inquiries, on a break and recently inactive, with the package, visits attended, the next visit and who referred them.
04 / PackagesOpen packages with bought and expiry dates, attended, booked and open visits and the price as recorded, then packages that expired with visits left and packages finished in the last 90 days.
05 / RecallsOverdue recalls first, then recalls due in the next 30 days and recalls recorded done, each with its kind label. Calls stay staff tasks; nothing is sent to patients.
06 / ReferralsOne card per referral source with the patients it sent, their first visit dates and the thank-you date as recorded, then patients by referral kind.
07 / InsightsPatients by state, visits by status, visits booked by kind, minutes booked by room, packages by state and package prices as a range per label. Visits, minutes and dollars are never added together.
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 10 fictional patients: four in a series, two between series, two new inquiries, one on a break and one inactive, with 7 packages and 46 visits across three rooms. Sample edits stay in memory and reset on navigation or reload.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
MORE OF THE WORKING DAY
Editable native forms and document templates give your team a practical starting point.
Choose forms individually in Setup & resources, then customize and publish them in the native form builder.
Open each template in Documents and complete it for the actual job or visit.
Record progress and notes in the kit’s operating views. Keep earlier rows by archiving them, and retain the context for the next person.
Forms collect information for staff review. They do not automatically change the kit’s custom records. Repeating setup preserves existing resource edits.
PLEASE READ
THE KIT, UNPACKED
One contact-linked patient record holds a first name and last initial, status, inquiry date, preferred days and times, the referral source and thank-you date, a recall date and kind, each package with its visit count, recorded price and bought and expiry dates, each visit with its date, time, minutes, room, kind, status and the package it draws from, a non-clinical staff note and an editable front desk checklist.
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 business name, descriptor 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 backend helpers are required for connected patient record creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, keep visits, minutes and money apart, refuse health information, dates of birth, insurance numbers, access codes, logins, card numbers and Social Security numbers, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
Stillroom records what the front desk agreed and saw. Only attended visits draw a package down, and it applies no cancellation or expiry policy. Visits, minutes and money each keep their own unit. It does not check room or practitioner availability, bill insurers, take payments or send messages. Conditions, symptoms, treatment and point notes, medications, pregnancy details, dates of birth, insurance member numbers, access codes, logins, payment card numbers and Social Security numbers are refused in recorded text and in the native form drafts, while front-desk text such as Room 2, 60 min follow-up and Package of 6 is kept.
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.
Stillroom keeps its white meridian bar, with a brass point under each view, across the kit views and native CRM tools in the same signed-in account. 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.