Skip to content
View packages

CRM KitsPediatric practices

Every family kept on schedule.

A family card wall for a pediatric front desk. One card per household, one row per child with an age band label and a well-visit recall pill, and a footer that tells you which siblings could be booked in one call. Growing keeps the relationship work in one connected workspace.

Families in the GoSeedly Pediatric Practice Kit with fictional sample records

One card for every household.

Each card names the family and its preferred contact, lists one slim row per child, and closes with the siblings due together, the forms outstanding and the window to call in.

Actual interface captures with fictional sample data. Open a screenshot to see it full size.

What’s in the kit

Screens

  • Families card wall operating view
  • Children operating view
  • Well-visit recalls operating view
  • Sibling bundles operating view
  • New families intake operating view
  • Forms and paperwork operating view
  • Insights operating view
  • Two recorded desk windows behind one revision guard
  • Three native form drafts and three editable document templates
  • Editable per-family checklists and preserved row history

four pipelines

  • Family relationships · 7 stages
  • Well-visit recalls · 8 stages
  • Sibling bundles · 7 stages
  • Forms and paperwork · 7 stages

Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.

nine workflow drafts

  • New family enquiry
  • Forms reminder
  • Forms returned note
  • First visit booked note
  • Well-visit recall due
  • Recall second attempt
  • Sibling bundle call
  • Paperwork ready
  • Family reactivation

Inactive until you review and publish them. None send customer messages.

Forms and documents

  • New family registration
  • Appointment request
  • School or camp form request
  • Well-visit recall call sheet
  • New family welcome checklist
  • Paperwork pickup slip

Editable native forms and document templates. Forms collect information for staff review.

Sample workspace

Explore 12 fictional households with 26 children across all six age bands, 9 well visits due this month, 5 past due, 4 sibling bundles, 4 families still in intake and 7 school or camp paperwork requests. 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
Read the installation guide

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.
  1. Check your Seedly

    Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.

  2. Connect the helper

    Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.

  3. Make it yours

    Set practice 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 family record creation, edits, the recorded desk windows and resource setup. They preserve native account permissions, unrelated custom fields and row history, run the clinical guard on the server, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.

One contact-linked opportunity is one family relationship. It holds the household label, the preferred contact window, the intake step with the date it was reached, guardian rows with a relationship label and a preferred-contact flag, child rows with a first name label, an age band label and a well-visit recall month, paperwork request rows with a category label and its dates, and an editable checklist.

The kit records no date of birth: an age band label is the only age information it holds. It records no diagnosis, symptom, growth measurement, immunization, medication, dose, allergy, medical history, custody detail, insurance number or school identifier, and it holds no monetary field at all. 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. Recording a recall or an intake step does not contact anyone and does not book anything. There is no scheduling engine, no automated reminder or message of any kind, no patient or parent portal, no billing or payments, and the kit gives no medical advice.

Four optional pipeline templates and nine inactive workflow drafts. 12 fictional in-memory households with 26 children.

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 Pediatric Practice Kit

Checking access…

DevLaunch All Access

Every kit and every template.

See DevLaunch All Access

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?

Growing keeps its rounded indigo chrome panel 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.

Browse all 220 kits

Customer experiences / Trustpilot

What customers say
about DevLaunch.

Read all reviews on Trustpilot ↗

Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.