GoSeedly Dermatology Kit
A front desk and cosmetic coordinator workspace for a dermatology office. One segmented bar shows the whole recall year with past due pinned at the left, and underneath it every prepaid package is a punch card you can read in a second. Surface keeps the relationship and the commercial arrangement in one workspace and leaves clinical records in the practice’s own clinical system.
YOUR SURFACE FRONT DESK
01 — DESK
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 / DeskThirteen segments run left to right: past due, then the next twelve months. Each segment prints the count of patients whose annual recall falls in it and grows with that count, so the bar reads as a distribution. Choosing a segment lists its patients underneath with their recall state and attempts.
02 / Punch cardsA filled punch is a session used, a dashed punch is a session already booked, and an empty punch is a session that is neither. The three counts are written out under the punches. Expiring with sessions unused and fully used both say so in words, and the consult column runs alongside.
03 / PatientsReview the age band label, the preferred contact window, which office referred them, the annual recall month and state, pending consults, sessions still remaining and the derived desk state.
04 / Annual recallEvery recorded annual recall with its month, its column, the contact attempts, the last contact date, the state and the referring office. Recording a recall does not contact anybody and does not book anything.
05 / Cosmetic consultsConsults still pending a decision, oldest first, with the days since the consult, the follow-ups recorded and the decision so far. A consult past the window the office records for itself is marked overdue, in words.
06 / PackagesEvery active package with its label, its session counts, the sessions remaining, the purchase and expiry dates and the recorded amount as a reference. The kit does not price, invoice or take a payment, and it forecasts nothing.
07 / Reviews and referralsReview request states per patient, then the referring practices, specialist offices, salons and personal referrals as relationship rows, with the count of patients referred derived from the records and the last thank-you date somebody wrote down.
08 / InsightsCounts for each derived desk state, plus recalls on the bar, consults pending a decision, active packages, sessions still remaining, referring offices recorded and review requests asked for. Open the patients behind any number.
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 20 fictional patients. 18 carry an annual recall, 4 of them past due and 14 spread across the twelve month segments. 7 cosmetic consults cover all four decisions, 5 still pending and 2 of those past the follow-up window. 10 active packages, 3 expiring with sessions unused and 2 fully used. 5 referring offices. 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 record is one patient relationship. It holds the patient label, an age band label, the preferred contact window, the referring office, the annual recall month with its state, contact attempts and last contact date, the review request state with the date it was asked for, cosmetic consults as a date and a decision with their follow-ups, packages as the office’s own commercial label with sessions total, used and booked plus the purchase and expiry dates and a recorded amount, and an editable front desk checklist. Referring offices are workspace records with their own revision guard, because a referring office is not a patient.
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 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 record creation, edits, the two recorded desk windows, the referring office list and resource setup. They preserve native account permissions, unrelated custom fields and row history, check revisions before saving, and run the clinical guard before anything is written. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional, and none of them contains a messaging node.
This is a front-desk and relationship workspace, not a medical record. It 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 never stores diagnoses, conditions, lesion or mole descriptions, body areas, biopsy or pathology results, photographs or images, medications, product strengths, units injected, treatment settings, medical history, skin type classifications, insurance member or policy numbers, government identifiers or dates of birth; age is a band label at most and visit types are category labels only. Package and service labels are the office’s own commercial names, such as Series of 6 or Annual plan. The shared model refuses text that looks like a condition or finding word, a body area in anatomical phrasing, a drug, brand or device name, a dose or product strength, clinical vocabulary, an ICD-10 style code or an insurance member identifier, in every field, on the server as well as in the browser. Treat that as a guard against accidental entry rather than a guarantee. Clinical records stay in the practice’s own clinical system, and the kit gives no medical or skincare advice. Your practice decides what it records in its CRM and is responsible for its own privacy, security and regulatory obligations. There is no clinical system integration, no insurance or billing, no package payment processing or gift cards, no scheduling engine, no automated reminders or patient messaging, no patient portal and no payments. Recording a recall does not contact anybody and does not book anything, recording a session as used takes no payment, and the recorded package amount is a reference the office keeps for itself.
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.
Surface retains its application frame 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.