Skip to content
View packages

CRM KitsOrthodontic practices

Every consult to a start. Every start to the finish.

A coordinator desk with two halves: a consult-to-start funnel of five bands narrowing left to right, and a treatment timeline where every started patient is one bar measured in months. Archwire keeps the relationship work in one connected workspace and leaves clinical records in the practice’s own clinical system.

Coordinator desk in the GoSeedly Orthodontics Kit with fictional sample records

The funnel, with the pending band opened up.

Five bands narrow left to right through new enquiry, consult booked, consult done, pending decision and started. Each one carries its recorded patient count and the total of the contract amounts recorded on that stage, or says plainly that no amounts are recorded. The pending band expands into a chip per family, with the days since the recorded consult and the recorded decision state.

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

What’s in the kit

Screens

  • Coordinator desk with the funnel and the treatment timeline
  • Patients operating view
  • Consults operating view
  • Observation recall operating view
  • Active treatment operating view
  • Referring dentists operating view with derived referral counts
  • Insights operating view
  • Server-enforced clinical guard on every text field
  • Recorded follow-up window with its own revision guard
  • Three native form drafts and three editable document templates
  • Editable front desk checklists and preserved row history

four pipelines

  • Consult to start · 7 stages
  • Active treatment · 7 stages
  • Observation recall · 7 stages
  • Referring offices · 8 stages

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

nine workflow drafts

  • New enquiry task
  • Consult reminder task
  • Consult done note
  • Pending decision follow-up
  • Second follow-up after a wait
  • Start welcome task
  • Observation recall due task
  • Finish-day review request task
  • Referring dentist thank-you task

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

Forms and documents

  • New patient consult request
  • Appointment change request
  • Finish-day feedback
  • Consult follow-up call sheet
  • Treatment start checklist
  • Referring dentist thank-you letter

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

Sample workspace

Explore 22 fictional patients across all five funnel bands, with 6 pending decisions of which 2 sit past the sample follow-up window, 8 in active treatment of which 2 have passed their recorded estimated month count, 4 on observation recall, and 5 referring dental offices as their own records. 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 recorded follow-up window and resource setup. They preserve native account permissions, unrelated custom fields and checklist history, hold the record kind and currency immutable, 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.

One contact-linked record is one patient relationship or one referring dental office. A patient record holds the patient label, an age band label, the responsible party label, the referring office label, the funnel stage with the date it was entered, the recorded consult date, the decision state, the follow-up attempts and last follow-up date, the treatment type label, the contract amount and down payment in minor units, the start month, the estimated month count, the observation recall month and its attempts, the next milestone label and an editable front desk checklist.

This is a treatment-coordinator and front-desk relationship record, not a medical or dental record. It is not a HIPAA compliance product, it is not an EHR, EMR or practice management system, and installing it does not make a practice HIPAA compliant. Do not use it to store protected health information. It never stores diagnoses, malocclusion or Angle classes, tooth numbers, clinical findings, imaging, appliance details, wire sizes, medications, doses, medical or dental history, insurance member or policy numbers, government identifiers or dates of birth; age is an age band label at most. Treatment type and next milestone are the office’s own category labels, and contract amount and down payment are recorded reference numbers rather than a billing system, a payment plan or a financing product. The shared model refuses text that looks like one of those values 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 dental or medical advice. The practice is responsible for its own compliance and for whatever it chooses to record in its CRM. There is no practice management or imaging integration, no treatment planning, no insurance, billing or financing processing, no scheduling engine, no automated reminders or patient messaging, no patient portal and no payments. Every amount shown is the total of amounts somebody recorded, and consult to start is reported as recorded counts rather than a forecast.

Four optional pipeline templates and nine inactive workflow drafts. 22 fictional in-memory patients and 5 referring dental offices.

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 Orthodontics 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?

Archwire keeps its graphite coordinator rail across the kit views and the 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.