GoSeedly Physical Therapy Kit
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.
YOUR STRIDE FRONT DESK
01 — BOARD
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 / BoardOne 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.
02 / PatientsThe program label, visits used of authorized, visits booked, visits unused, the days since the last attended visit, the referrer who sent them and the derived desk state.
03 / Drop-off watchRecords past the clinic's own recorded threshold with nothing booked, with the contact attempts, the last contact date and the drop-off state. Recording a drop-off does not contact anybody.
04 / AuthorizationsRecorded end dates falling inside the recorded window with visits still unused, soonest first, including a date that has already passed. Recorded numbers and dates only; no member, policy or authorization number is stored anywhere.
05 / Discharge and reviewsRecords whose recorded visits are complete or that are already discharged, with the review request state and the return-for-wellness interest as labels the front desk records after a conversation.
06 / ReferrersPhysician offices, surgeons' offices, gyms and employers as relationship records, with patients referred counted from the records that name them and the two dates the desk keeps. The clinic's drop-off threshold and authorization window sit on the same view.
07 / InsightsCounts for each derived desk state, authorized visits against attended and booked, visits authorized and unused, and referrers never thanked. Nothing here is a forecast or a revenue figure.
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 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.
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. 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.
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 clinic 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 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.
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.
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.
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.
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.