Implementation
Two weeks, and most of it is us waiting for you to press send.
Days 1–2
Plan configuration
We do
We build your benefit plan: covered care types, entitlement unit (days or hours), annual allowance per employee, copay schedule, blackout dates, per-week caps, and effective dates.
You do
One 45-minute call with whoever owns the benefit. Bring your allowance and copay preferences, or take our defaults.
Days 3–5
Eligibility
We do
We stand up eligibility one of two ways: SSO-domain verification, where employees confirm with their work email, or a CSV census upload. The census import shows you a diff — adds, changes, removals — before anything commits.
You do
Either confirm your email domains, or send one CSV. That's it. No HRIS project, no IT ticket queue.
Days 6–8
Communications
We do
We write the launch email, the manager one-pager, and the intranet blurb. You get them in your voice, ready to send, plus a Spanish version.
You do
Review and approve. Tell us your internal channels — email, Slack, Workday announcements, break-room poster.
Days 9–14
Launch
We do
Employees activate. First bookings land. We watch fill rate and time-to-confirm daily for the first month and tell you unprompted if either slips.
You do
Send the email. Then nothing — families contact us directly, not your HR team.
What actually goes wrong
Three things that turn two weeks into two months.
None of them are technical. All of them are avoidable if you know about them on day one.
Waiting on a census file
The single most common cause of a slow launch. If your HRIS export needs a ticket, start it on day one — or launch on SSO-domain verification and add the census later. You do not need both.
Legal review of the DPA
Ours is short and we sign yours if you'd rather. We'll send it before the contract so the two reviews run in parallel instead of in sequence.
Waiting for open enrolment
You don't have to. Back-up care isn't an elected benefit — there's nothing for employees to enrol in and no plan-year lock. Launch whenever.
After launch
Utilisation is our job, not yours.
A benefit nobody knows about doesn't get used, and a benefit that doesn't get used doesn't get renewed. We run the reminder campaigns — at school-year start, before winter break, at flu season — and report what they moved.
Weekly
Usage digest by email during month one, monthly after.
Monthly
Fill rate, time to confirm, and days of work saved — including the bad months.
Quarterly
A board-ready export, and a call if anything in it needs explaining.