GoSeedly Nanny Service Kit
A nanny agency spends its day comparing one family against two or three caregivers, then following the trial that comes out of it. Placed builds the workspace around that comparison: a white canvas, a graphite chrome bar, and one violet accent that means a running trial or a completed placement.
YOUR PLACED MATCHING BOARD
01 — MATCHING 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 / Matching boardEach family that is not yet placed is one wide card split down the middle. The left half is the household the family described. The right half is up to three proposed caregivers with a fit note and a state. A violet bar across the card foot appears only when a trial start date and a trial length are both recorded.
02 / Family sheetSelecting a card fills the sheet below it: the household record with its must-have tags, the full shortlist including archived rows, the recorded trial with its dated check-in notes, and the placement. The native CRM stage control sits in the sheet header.
03 / Family intakeChildren, schedule, hours per week, requested start date and recorded intake date in one table, with the derived state beside each family. Filter by matching, trial or placed, and open a record to edit it.
04 / Caregiver rosterThe kit keeps its own per-workspace caregiver roster with availability, experience and current state, and shows which families each label appears on. Labels are matched exactly after trimming and case folding, so a roster row on no family and a family label on no roster row are both reported rather than guessed.
05 / Running trialsFamilies with a recorded trial, ordered by days remaining, with the recorded check-in notes beside each one. Elapsed days are clamped to the recorded length at both ends, so nothing reads negative and nothing overflows.
06 / Recorded placementsPlaced families ordered by placed date, with the caregiver, the recorded guarantee end date, the schedule and the placement fee reference. A family becomes placed because a caregiver label and a placed date were recorded, never because a state field was set by hand.
07 / Agency insightsCounts by family state, shortlist state and roster state, drawn from the records loaded in the selected pipeline. Placement fee references are totalled separately in each currency and nothing is converted; a family with no recorded fee is excluded rather than counted as zero.
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 nine fictional families in the separate sample view: three in a running trial, two already placed and four still matching, with eighteen shortlist rows in total and twelve fictional caregivers on the roster. Example edits stay in the current page memory and reset on navigation or reload; sample families are never inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
THE KIT, UNPACKED
A family engagement is a native contact-linked opportunity with namespaced household details, must-have labels, a placement fee reference, a shortlist of caregivers with stable IDs, a recorded trial with dated check-in notes, and a recorded placement. The caregiver roster is the kit own per-workspace record set with its own 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 agency 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 nanny service helper is required for connected creation, editing, the caregiver roster and starter setup. It preserves native account permissions and unrelated custom fields, enforces the two cross-field date rules, and checks the current record state before saving. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
Everything on screen is staff-entered. The kit runs no background checks, screening or reference verification, no payroll or tax handling, no scheduling engine or calendar sync, no contracts or e-signature, no payment processing and no family or caregiver messaging, and it makes no licensing or regulatory claim. Family state is derived from the recorded trial and placement fields rather than stored, so the board and the counts cannot disagree. The trial bar is elapsed days clamped to the recorded length; it does not end a trial, move a stage or predict an outcome. Interview and guarantee dates are recorded values that reserve nothing. A placement fee reference is a planning number, not an invoice or a collected amount.
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
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.
Placed keeps its agency navigation across the original nanny service 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.