Skip to content
View packages

CRM KitsDermatology practices

Every annual visit recalled. Every package used.

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.

Desk in the GoSeedly Dermatology Kit with fictional sample records

The recall year, then the packages.

Thirteen 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.

Actual interface captures with fictional sample data. Open a screenshot to see it full size.

What’s in the kit

Screens

  • Desk operating view with the recall bar, the punch card wall and the consult column
  • Patients operating view
  • Annual recall operating view
  • Cosmetic consults operating view
  • Packages operating view
  • Reviews and referrals operating view
  • Insights operating view
  • Server-enforced clinical guard on every text field and non-name label
  • Two recorded desk windows and a referring office list behind one revision guard
  • Three native form drafts and three editable document templates
  • Editable front desk checklists and preserved row history

four pipelines

  • New patient welcome · 7 stages
  • Annual recall · 7 stages
  • Cosmetic consults · 7 stages
  • Package follow-through · 8 stages

Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.

nine workflow drafts

  • New patient welcome task
  • Annual recall due task
  • Recall second attempt
  • Consult booked note
  • Consult follow-up task
  • Second consult follow-up
  • Package expiring task
  • Package fully used renewal task
  • Review request task

Inactive until you review and publish them. None send customer messages.

Forms and documents

  • New patient registration
  • Cosmetic consult request
  • Visit feedback
  • Annual recall call sheet
  • Package summary slip
  • Consult follow-up call sheet

Editable native forms and document templates. Forms collect information for staff review.

Sample workspace

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.

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
Read the installation guide

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.
  1. Check your Seedly

    Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.

  2. Connect the helper

    Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.

  3. Make it yours

    Set practice name, descriptor 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 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.

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.

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.

Four optional pipeline templates and nine inactive workflow drafts. 20 fictional in-memory patient relationships.

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 Dermatology Kit

Checking access…

DevLaunch All Access

Every kit and every template.

See DevLaunch All Access

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?

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.

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.

Browse all 220 kits

Customer experiences / Trustpilot

What customers say
about DevLaunch.

Read all reviews on Trustpilot ↗

Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.