A waitlist ladder read against the open recurring slots. One rung per waiting family with the days and time windows they can do, and under every open slot the three longest waits it already fits. Milestone keeps the wait, the visits and the relationships in one connected workspace.
Each rung carries a client first name, an age band label, the service line, the days and time windows recorded, the whole weeks waited and the last contact. Each open slot names its matches by ladder position, oldest wait first.
A first name label, an age band label and a service line label, with the preferred caregiver, the recorded days, the recurring slot and the authorized visits beside them. No date of birth is recorded anywhere in the kit.
A day, a time, a clinician first name and a service line. The time window is derived from the time, and the matches are a plain availability comparison, capped at the three longest waits.
Visits used of visits authorized, written out in words before a single thin meter, with the visits unused, the end date and a flag once an authorization falls inside the window you record.
Relationship records for schools, pediatric offices and other referrers, a name, a contact label and a follow-up date, beside the caregiver follow-ups the desk already owes.
Each derived desk state counts the clients behind it, and opens them.
YOUR PROCESS, YOUR STARTING POINT
Useful structure. Only what you choose.
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
01 / FOUR PIPELINES
Choose your starting structure.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
Client relationships · 7 stages
Waitlist calls · 8 stages
Open recurring slots · 7 stages
Authorized visits · 7 stages
02 / NINE WORKFLOW DRAFTS
Give the next step a shape.
New enquiry task
Waitlist welcome note
Waitlist check-in call
Slot offered task
Slot offer follow-up
First session booked note
Authorization ending task
Caregiver follow-up due task
School or referrer thank-you task
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
03 / SAMPLE WORKSPACE
Explore before adding records.
Explore 24 fictional clients: 9 on the waitlist with the longest at 17 weeks, 2 with a slot offered, 11 active, 1 on hold and 1 removed. Six open recurring slots, four of which already fit a waiting family, five authorizations ending inside the recorded window with visits unused, four caregiver follow-ups due and six relationship records. Sample edits stay in memory and reset on navigation or reload.
No sample customers are inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
MORE OF THE WORKING DAY
From the first inquiry to the final handoff.
Editable native forms and document templates give your team a practical starting point.
01 / INTAKE & FOLLOW-UP
Three ready-to-edit forms.
New family enquiry
Availability update
Family feedback
Choose forms individually in Setup & resources, then customize and publish them in the native form builder.
02 / WORKING DOCUMENTS
Three reusable templates.
Waitlist call sheet
Slot offer confirmation letter
Authorization ending call sheet
Open each template in Documents and complete it for the actual job or visit.
03 / THE NEXT STEP
Checklists alongside the work.
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
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.
THE KIT, UNPACKED
Your workspace. Your starting point. Your code to edit.
One contact-linked opportunity is one client and family relationship. It holds the client first name label, the age band label, the service line label, the stage with the date it was reached, the waiting-since date, the contact attempts and last contact, the recurring slot day, time and clinician first name, the authorized visit count, the visits used and the end date, the caregiver follow-up due date, the school or referrer label, caregiver rows with a relationship label and a preferred-contact flag, availability rows of a day and a time window, and an editable checklist. The open recurring slots, the relationship records and the recorded authorization window live in one account store behind a single revision guard.
Waitlist desk operating view with the ladder and the slot matches
Clients ledger operating view
Waitlist ladder operating view
Open recurring slots operating view
Authorized visits operating view
Caregivers, schools and referrers operating view
Insights operating view
A workspace store for the authorization window, the open slots and the relationship records, behind one revision guard
Three native form drafts and three editable document templates
Editable per-client checklists and preserved row history
Four optional pipeline templates and nine inactive workflow drafts
24 fictional in-memory clients with 6 open recurring slots
Guided setup, compatibility report, and private rollback receipt
AI-agent documentation for customized installations
Original editable source, configuration, and tests
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
02
Connect the required helper.
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.
03
Set up your own team.
Edit clinic name, descriptor and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.
Compatibility and operational details
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 client record creation, edits, the workspace store and resource setup. They preserve native account permissions, unrelated custom fields and row history, run the boundary guard on the server, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
Matching is a plain availability comparison: the same day, the same time window and compatible service lines, sorted oldest wait first. Nothing is weighted, scored or decided for you, and offering a slot is still a call somebody makes. The kit records no date of birth, diagnosis, condition, disability category, test score, therapy goal, session or progress note, education plan, home program, medication, medical history, insurance member, policy or authorization number, school identifier or government identifier, and it holds no monetary field at all. An age band label is the only age information it holds, and an authorized visit count with an end date is a recorded number and a date. A server-enforced guard refuses free text that looks like any of those in every field, which is help against accidental entry rather than a guarantee. There is no scheduling engine or calendar sync, no insurance verification, authorization submission or billing, no automated reminder or message of any kind, no family login, no payments, and the kit gives no therapy or medical advice.
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.
Checking access…
DEVLAUNCH ALL ACCESS
Every kit. And everything else.
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.
All 195 CRM kits
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
Every class, course, and product
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Private calls with Aaron
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
DevLaunch All Access
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.
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
Good questions. Clear answers.
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?+
Milestone keeps its slim black top bar across the kit views and native CRM tools in the same signed-in account, with no sidebar taking room from the two lists. 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.
Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.
Your privacy, your choice.
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.