GoSeedly Orthodontics Kit
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.
YOUR ARCHWIRE COORDINATOR DESK
01 — COORDINATOR 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 / Coordinator deskFive 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.
02 / Treatment timelineThe second half of the desk. Every started patient sits on a shared month axis from their recorded start month to their recorded estimated finish month, with a marker at the current month and the count written out as "Month 9 of 22". A bar whose elapsed months have passed the recorded estimate is the only red on the timeline.
03 / PatientsReview the age band label, the responsible party, the funnel stage and the date it was entered, the recorded consult date, the recorded contract amount, the treatment type or month count, and the derived desk state.
04 / ConsultsEvery family still deciding, longest since the recorded consult first, with the decision state, the follow-up attempts and the last follow-up date. The follow-up window above the list is a number the practice records for itself, saved with a revision guard.
05 / Observation recallPatients who have not started and carry a recorded observation recall month, soonest first, with the contact attempts already recorded. Recording a recall does not contact anyone and does not book anything.
06 / Active treatmentThe timeline as a list: treatment type label, start month, estimated finish, the month count, the months left and the next milestone as a visit category. Past estimate is a recorded month count, not a clinical judgement.
07 / Referring dentistsEach referring dental office is its own record. Patients referred and started are derived by matching the referring office label recorded on each patient record, beside the date of the last thank-you somebody recorded.
08 / InsightsEvery derived desk state with the patients behind it, plus consults recorded, starts recorded, families still deciding and treatments past their estimated months. A record only counts as consulted once a consult date is on it.
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 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.
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 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.
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 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.
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.
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.
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.
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.