
CRM KitsPhysical therapy clinics
Every authorized visit used. Every drop-off caught.
A visit counter board: every patient is a row of segments, one per authorized visit, filled for attended and outlined for booked, with a drop-off marker the moment somebody stops coming. Stride keeps the front desk and the referral relationships in one connected workspace and leaves clinical records in the clinic's own system.
The count, and who stopped coming.
One row per patient record with a segmented visit bar, one segment per authorized visit: filled for attended, outlined for booked, empty for neither. The same counts are written out beside it. Drop-offs come first, then authorizations ending with visits still unused. The referrer column sits on the right.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Visit counter board with a segmented bar per patient record
- Patients operating view
- Drop-off watch operating view
- Authorizations operating view
- Discharge and reviews operating view
- Referrer relationship records with derived patient counts
- Insights operating view
- Server-enforced clinical guard on every text field and the program label
- Recorded drop-off threshold and authorization window with their own revision guard
- Three native form drafts and three editable document templates
- Editable front desk checklists and preserved row history
four pipelines
- Patient relationships · 7 stages
- Authorization and visits · 7 stages
- Drop-off recovery · 7 stages
- Referrer relationships · 8 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- New referral received
- Registration reminder
- Evaluation visit booked
- Drop-off call
- Second drop-off attempt
- Authorization ending
- Discharge review request
- Referrer thank-you
- Wellness return check
Inactive until you review and publish them. None send customer messages.
Forms and documents
- New patient registration
- Appointment request
- Discharge feedback
- Drop-off call sheet
- Referrer update cover letter
- Discharge and review checklist
Editable native forms and document templates. Forms collect information for staff review.
Sample workspace
Explore 18 fictional patient records across 230 authorized visits, with 5 drop-offs, 4 authorizations ending inside the recorded 30-day window with visits unused, 3 discharged records awaiting a review request and 6 referrer relationships. 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
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.
How setup works
Full installation guideCheck your Seedly
Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.
Connect the helper
Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.
Make it yours
Set clinic 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 desk numbers, the referrer records 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. A record created by the 0.1.0 kit opens without migration and keeps every field this release no longer writes. Deploy the helpers from the authoritative backend source. Pipelines and workflow drafts are optional.
One contact-linked record is one patient relationship. It holds the patient label, an age band label, the referrer it names, a plain program label the clinic types, the authorized, attended and booked visit counts, the authorization end date, the last attended visit date, contact attempts and the last contact date, the drop-off, discharge, review request and wellness interest states, the preferred contact window and an editable front desk checklist. Referrers are their own relationship records, kept with the clinic's two recorded numbers under a server-owned revision.
This is a front-desk and referral relationship record, not a medical 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 clinic HIPAA compliant. Do not use it to store protected health information. It never stores diagnoses, injuries, body regions, surgeries, pain scores, range-of-motion or strength measurements, goals, exercises or home programs, clinical notes, medications, referral diagnoses or codes, insurance member, policy or authorization numbers, government identifiers or dates of birth. The authorized visit count and the authorization end date are recorded numbers only, the age band is a label, and the program label is a plain label the clinic types. The shared model refuses text that looks clinical in every field, on the server as well as in the browser, while accepting ordinary front-desk phrases such as "Call back after 4" and "7 of 12 used". Treat that as a guard against accidental entry rather than a guarantee. Clinical records stay in the clinic's own system, and the kit gives no medical or rehabilitation advice. There is no EHR or EMR integration, no practice management integration, no clinical documentation or outcome measures, no insurance verification, authorization submission, claims or billing, no scheduling engine, no automated reminders or patient messaging, no patient portal and no payments. A booked count is a number the front desk typed: it reserves no room, holds no time and creates no calendar entry.
Four optional pipeline templates and nine inactive workflow drafts. 18 fictional in-memory patient records.
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 Physical Therapy Kit

DevLaunch All Access
Every kit and every template.
- All 220 CRM kits for Seedly CRM
- All 270 website templates for Seedly Sites
- Every class, course, and product we release, added as it ships
- Private calls with Aaron
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?
Stride 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.
More health, beauty & wellness kits
Browse all 220 kits









