GoSeedly Chiropractic Kit / INSTALLATION

A clear path
to your workspace.

Bring the kit into your compatible Seedly installation, preserve existing work, and choose the starter content that fits your team.

Start with your Seedly project.

Use your separately obtained Seedly CRM 5.8.4 installation with extension API 1, a configured backend, and working authentication. Keep a private source checkpoint, including existing customizations. Use Node.js 20 or newer.

Run guided setup.

Extract the kit outside the Seedly source folder. From the kit directory, run node setup.mjs. The check identifies supported integration files, changed files, and destination conflicts before installation.

Build and connect.

Deploy the included required helper from your authoritative backend source before connected edits. Follow QUICKSTART.md with your project’s existing package manager. Build the web app, sign in, and open your existing /location/YOUR_LOCATION_ID address. Verify access, navigation, and your important CRM flows.

Install the interface.
Choose the starting content.

Frontend installation and optional account content are separate. 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. Follow QUICKSTART.md and STARTER_CONTENT.md for the exact integration. The frontend installer does not deploy your backend.

Pick your starting structure.

Starter setup offers New patient intake, Active care plan, Wellness membership, Reactivation. Select individual pipelines and drafts, or use a suitable existing pipeline with the exact stage needed by the chosen draft.

Adapt each workflow.

All nine workflows remain inactive drafts. Review their native triggers, internal tasks, notes, timing, and assignments before publishing in Seedly. Timed waits do not check whether a task is complete or the stage has changed. These examples do not send customer messages.

Explore sample mode.

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. Add ?example=1 to the home or custom-view URL. Leave sample mode to return to your real account.

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.

INSTALLING WITH AN AI AGENT?

Give it the context.
Keep your custom work.

Existing records and unrelated custom source do not require starting over. Modified integration files need a deliberate merge.

Start with the copy-and-paste prompt in INSTALL_WITH_AI.md.

Read AGENT_INSTALL.md for routes, permissions, provider wiring, backend contracts, and compatibility requirements.

Run node setup.mjs check "/path/to/seedly" before modifying files.

Preserve existing extensions, providers, account controls, custom pages, and unrelated data.

Use a reviewed merge for changed integration files; never replace them with clean copies or bypass the installer’s fingerprints.

Deploy the required write helper from the authoritative backend source before connected edits; preserve existing functions and authorization.

Build and verify account access, original CRM modules, new screens, saving, and reload behavior before publishing.

Make the workspace
feel like your team.

Edit apps/web/components/devlaunch-chiropractic/config.ts to set practice name, descriptor, promise line, and default pipeline name, then rebuild. The design applies to the entire web installation. Use separate web installations to evaluate different full-interface kits, rather than stacking their installers.

Starter removal, updates, and rollback

Review unused starter additions for removal in Starter setup before removing the frontend. Server checks preserve edited or published workflows and pipelines with jobs or references. The process targets recorded kit additions rather than sweeping account records.

Preserve your local configuration and source edits. Preview frontend removal with node setup.mjs remove "/path/to/seedly" --dry-run. The automatic uninstaller uses a private restoration receipt and refuses to overwrite later edits. Keep that receipt private and out of public hosting or source exports. Removing frontend files does not remove account data or undeploy backend functions.

For an update, follow the documented removal/install process and reapply your preserved changes. A manually merged installation needs its own private change ledger and reviewed source rollback.

What the workspace records

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.

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.

The kit’s original operational screens share the frame with full CRM modules from your own Seedly source. Existing account permissions, feature gates, and configured providers still determine access to those modules.

See the interface and everything included.

Back to GoSeedly Chiropractic Kit

A clear pathto your workspace.