
CRM KitsDaycares and preschools
Every room as recorded.
A classroom board that sets enrolled children against the capacity your center records, a waitlist ladder per room, tour follow-ups and enrollment paperwork. Each child is a first name and an age band, and Sprout keeps the numbers your office types in one connected workspace.
See the whole center at a glance.
A tile per classroom leads the board, then one wide panel per room draws enrolled children as seat squares against the recorded licensed capacity, with children per recorded staff member beside the recorded ratio limit and the enrolled children by age band. These are counts of what your office typed, not a licensing, ratio or safety check.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Classroom board operating view
- Families operating view
- Waitlist operating view
- Tours operating view
- Paperwork operating view
- Transitions operating view
- Insights operating view
- First names and age bands, with one-click conversion of 0.1.0 birth months
- A guard on every name and free-text field, in the browser, on the server and in the form drafts
- Three native form drafts and three editable document templates
- Editable per-child checklists and preserved row history
four pipelines
- Enrollment journey · 7 stages
- Tours and visits · 7 stages
- Waitlist and openings · 6 stages
- Re-enrollment and transitions · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Inquiry response
- Tour booking
- Tour follow-up
- Waitlist check-in
- Opening offer
- Paperwork reminder
- First week check-in
- Move-up notice
- Annual re-enrollment review
Inactive until you review and publish them. None send customer messages.
Forms and documents
- Tour and enrollment inquiry
- Enrollment details
- Family feedback
- Waitlist position letter
- Enrollment paperwork checklist
- Classroom transition notice
Editable native forms and document templates. Forms collect information for staff review.
Sample workspace
Explore 70 fictional children across five fictional classrooms. 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
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 center 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, age band conversion, the classroom record and resource setup. They preserve native account permissions, unrelated custom fields and row history, run the guard before anything is written, and check revisions before saving. They read records a page at a time, so counts read every record up to 5,000 and say when more were not read (0.1.0 read them through Seedly’s pipeline view, which stops at 1,000), and run setup in steps on a large account. Deploy them from your authoritative backend source. Pipelines and workflow drafts are optional. When updating from 0.1.0, remove 0.1.0 with its own installer and then install 0.2.0 in your working tree, with nothing deployed or built in between, deploy the backend, then build and deploy the web app. A page still open on 0.1.0 keeps working against the 0.2.0 backend meanwhile: every function it calls keeps its arguments and answers, and anything it can no longer do, such as adding a child without an age band, is refused with a message and nothing is written. Do not roll back to 0.1.0 after converting records or running setup.
One contact-linked record follows one child from inquiry to a start date: the child’s first name and age band (Not yet born, Infant, Toddler, Twos, Preschool, Pre-K or School age), classroom, status, waitlist position and date added, desired start month, tour date and follow-up state, schedule label, five paperwork flags that record only that a form was received, recorded transitions and an editable checklist. Classrooms (capacity, ratio limit and recorded staff count) and the center’s time zone, which sets today for days waiting and upcoming openings, are a separate per-workspace record. Other custom fields are preserved.
What changed in 0.2.0, a free update for 0.1.0 owners: a child is a first name and an age band instead of a birth month. A birth month 0.1.0 stored stays read-only until someone clicks Convert to age band, which names the band first, and the birth month is gone afterwards; nothing converts on its own. A guard in the browser, on the server and on every name and free-text field of the three form drafts refuses birth dates, ages, health, allergy, immunization and medication details, development and behavior notes, custody and pickup arrangements, a family’s immigration, income, benefits, housing, foster care or child welfare status, door codes, logins, and card, bank and ID numbers, as a guard against accidental entry rather than a guarantee. Naps, potty training, cubbies, diapers and wipes and classroom names pass. The over-ratio flag is gone: the board shows counts beside one another. Setup names any form or document 0.1.0 added and says how to replace it, and never edits one you own. Seats filled, children per staff and days waiting are derived from values your center records. Sprout makes no licensing, ratio, safety or regulatory determination, and does not provide attendance or check-in, billing or subsidy processing, parent messaging or daily reports, health record storage, or staff scheduling.
Four optional pipeline templates and nine inactive workflow drafts. 70 fictional in-memory 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 Daycare & Preschool 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
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?
Sprout 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 pets, family & care kits
Browse all 220 kits









