GoSeedly Chiropractic Kit
A chiropractic office does not lose money on the first visit. It loses it in week five, when a patient who agreed to eighteen visits quietly stops showing up and nobody notices until the schedule is thin. Align draws twelve weeks of recorded attendance as a grid, so a gap is visible before it becomes a lapse, and keeps the people who already stopped coming right beside it.
YOUR ALIGN FRONT DESK
01 — ATTENDANCE GRID
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 / Attendance gridOne row per care plan record and twelve weekly cells, shaded in four steps by the number of visits recorded as completed in that week. Rows are ordered by the most recent recorded visit, so a plan going quiet sinks on its own, and an entirely gray row has no recorded visit in twelve weeks at all. The reactivation queue sits beside the grid.
02 / Recorded visitsRecorded visits for the selected workspace date, grouped by the provider label on each row and shown in time order with the care plan each one belongs to. A booked row can be recorded as completed in one click, which shades the week behind it.
03 / Care plan registerVisits used of the planned count, the recorded cadence label, the recorded reactivation threshold, the last recorded visit and the native pipeline stage for every valid record. A plan whose recorded visits pass its planned count says so rather than showing a negative remainder.
04 / Reactivation bandsRecords past their own recorded threshold, banded at 30 to 59 days, 60 to 89 days, and 90 days and over, each with its recorded next touch date and note. A record with no recorded visit at all is its own group and is never treated as current. Red appears in exactly one place in the whole workspace: the 90 day band.
05 / Provider labelsRecorded provider labels exactly as the front desk typed them, each with its own twelve weekly cells, its care plan count and the visits recorded for the selected date. A label does not assign a person and asserts no licence or credential.
06 / InsightsPlan progress distribution, reactivation band counts, recorded visit outcomes and a week by week total for the selected pipeline. The kept rate is completed out of completed plus no-shows, and no qualifying row gives an unavailable rate rather than an invented zero.
07 / Care plan editorPlan label, provider label, plan start date, planned visit count, cadence label, reactivation threshold, wellness plan label, next touch date and note, and individual visit rows. Visits used is counted from the rows, never typed, and the editor carries a standing notice that this is not a clinical record.
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 twelve fictional care plans with 200 recorded visit rows across twelve weeks and four provider labels in the separate sample view. Three of them are deliberately lapsed, one in each reactivation band, so the queue is never empty and the 90 day band is visible. Example edits stay in the current page’s memory and reset on navigation or reload; sample records are never inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
PLEASE READ
THE KIT, UNPACKED
A care plan record is a native contact-linked opportunity with a namespaced plan label, provider label, plan start date, planned visit count, visit frequency label, reactivation threshold of 30, 60 or 90 days, next touch date and note, an optional wellness plan label, and individual visit rows. Visits used and the last recorded visit date are both derived from the recorded rows and are never stored as values of their own.
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, promise line, 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 chiropractic helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, checks the current record state before saving, enforces the next touch and plan start rules server side, and exposes no stage mutation of its own, so stage changes stay on your CRM’s own move. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
Align is a front desk and retention workspace, not a clinical record. It has no field for notes, findings, diagnoses, diagnosis codes, spinal levels, adjustments, techniques, measurements, imaging references, outcome scores or exercise prescriptions, and it makes no HIPAA or other compliance claim. The kit records no monetary amount at all, so nothing is billed, charged, claimed or collected, and there is no insurance or billing field anywhere in the schema. Visit rows reserve no room or table, hold no time, prevent no double booking, create no CRM appointment and send no reminder. Reactivation bands are arithmetic on recorded dates measured against the workspace date you choose, not churn predictions, and a blank last visit date means nothing was recorded rather than that the patient is gone. Provider labels do not assign staff, and a wellness plan label charges and renews nothing.
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.
Align keeps the brand, the promise and its workspace navigation in one violet bar across the original chiropractic views and native CRM modules. Full CRM tools remain available within the same signed-in account and application theme. 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.