For nanny and sitter agencies

Most agencies run on a form, an inbox, and the owner’s phone. I build what sits behind them.

A family asks for Saturday night, and your evening goes to texting sitters one at a time. I’m Garrett Holmes. I spent nine years as an executive assistant, and I build the operations behind small agencies: requests that arrive sorted, sitters offered the job by text, and a record of every family that isn’t kept in your head.

Book fifteen minutes → or write to me

Two phones side by side. The parent’s shows “Sunny is confirmed for Saturday, Sept 26 at 6:00pm.” The sitter’s shows the job offer, a YES reply, and the confirmation with the family and neighborhood.

Demo

Where the evening goes

And what takes it back

Today

Every family fills in the same long form, whether they want a nanny placement or a sitter for Saturday night.
Each request lands in an inbox. Then you text sitters one at a time until somebody says yes.
Who sat for which family, whose CPR card lapses next month, and the sitter a family never wants back all live in your head and your phone.
Caregivers apply by email attachment, and their certifications end up in a downloads folder.

What I build

A request form that asks what kind of care first and folds the rest away. A returning family gets one short screen.
Sitters offered the job by text. The ones a family prefers are asked first, the first yes gets the sit, and two sitters can never both be booked for it.
Families who book often can do it in one text, in their own words. It is read back to them, and only YES books.
A record for every family and every sitter: who they prefer, who they never want back, and every sit and text on one timeline.
A roster that watches CPR and First Aid expiry and tells you on Monday morning.
Applications on your site, with résumés and certifications uploaded straight to private storage.
Memberships and invoices through Stripe.
Anything that can text or charge a family has its own switch, and nothing goes out until you turn it on.

Built for one agency first

Case file № 001

All of it was built for Three Peas in a Pod, a Denver nanny and babysitting agency. The new site has been live on the agency’s own domain since September 20, 2026. Sitter offers, booking by text and billing are built and in testing, each behind its own switch.

Read the case file → threepeasagency.com ↗

The Three Peas request form on a phone: “What do you need?”, with “A sitter for a date” selected and short-term care, a nanny placement, and a membership folded below it. — Exhibit A The request form, on a phone. It asks what kind of care first; once a family picks one, the other choices fold down to a line each.

A family record: three sitters with Preferred, No preference and Never send buttons, one marked Never send with the owner’s private note, and the start of the family’s history, filterable by sits, texts, enquiries, notes and changes. — Exhibit C Part of a family’s record on the desk: the sitters they prefer, who are asked first, and the one they never want back, who is left out of every offer. The history below holds every sit and text.

Captured from the live request form, the demo, and the desk rendered with an invented family and sitters. No real family or caregiver data.

How it works

From a call to a switch

01 Fifteen minutes You tell me how a request reaches you today and where the evening goes. I tell you honestly whether anything is worth building.
02 A written scope What I would build first, in what order, and what it costs, by email. No deck.
03 One piece at a time Start with whatever costs you the most evenings. The rest can wait until the first piece has earned it.
04 Plain underneath Ordinary tools, written down and handed over, so it keeps running whether or not I am around.

Closing entry

Fifteen minutes.

Tell me how a request reaches you today. You’ll leave with an honest read on what’s worth building, even if the answer is nothing yet.

Book fifteen minutes →

or write to [email protected]. I reply within one business day.