Comparison
NannyMatchDesk vs Bullhorn
Bullhorn is built for recruiting firms running volume desks with recruiters and account managers, while NannyMatchDesk is built for the owner who runs a household search end to end herself.
Comparison
Airtable is the flexible database many owners build their first candidate tracker in, while NannyMatchDesk is the version that already knows what a household placement needs to record.
Almost every boutique agency passes through a home-built base, and plenty run well on one for years. Airtable is honest, cheap to start, and shaped exactly the way you shape it. The trouble arrives at scale: linked tables between families and candidates, a view for guarantee windows, reminders at day three and day thirty, and someone to maintain all of it when you are on a school run. NannyMatchDesk trades that flexibility for a finished placement record, follow-up prompts, and reporting on which searches held. Build it yourself if the building is the fun part.
| What you are deciding | NannyMatchDesk | Airtable |
|---|---|---|
| Who maintains the structure | The product, updated as household placement practice changes | You, every time your process or your team changes |
| Family and candidate matching | Requirements scored against candidate attributes automatically on each search | Linked tables and filtered views you design and keep in step yourself |
| Reference and screening record | Structured reference calls and screening stages inside the candidate file | Whatever columns and attachments you decide to create |
| Guarantee and follow-up | Guarantee window and day three, day thirty, day ninety check-ins prompted for you | Date fields plus your own reminders or automations |
| Onboarding paperwork | Per-placement checklist covering work agreement, I-9 timing, W-4, and state forms | A file attachment habit that depends on you remembering the sequence |
| Working with a coordinator | Shared placement records with roles, on the Agency tier at $129 a month | Shared base access with permissions you configure per table and view |
| Flexibility | Narrow on purpose, so it stays fast on a household desk | Nearly unlimited, which is the appeal and also the maintenance |
What follows on the right is the shape of Airtable as a category: the workflow it assumes and the buyer it is written for. Both keep changing, so check the current shape of each one before you choose. NannyMatchDesk is published by MLJ, SASU and this page is written by Jimenez Julien.
The typical build starts with one table of nannies and one of families. Then comes a placements table, because you need to know who went where and for how much. Then a table of reference calls, because notes in a single cell stopped being readable. Then automations to nudge you at ninety days, and a form for candidate applications, and a view that hides the archived people.
It works. The cost is that you are now the administrator of a small internal system as well as the person doing the searches. Every new fee structure, every new role type, every change to your guarantee terms means a schema decision on a Sunday night. That is fine while the desk is small and expensive when it is not.
The value of a purpose-built tool is the arguments it has already settled. A placement has a start date, a fee, a deposit, and a guarantee window. A candidate has work authorization documents, credentials, and references from private families rather than companies. A family brief has hours, ages, driving, live-in status, travel, and a compensation range. Those decisions are the product.
You lose some flexibility in exchange. If you want to track a fourteenth attribute nobody else tracks, a custom field carries it, but the core shape is fixed. Most owners find that trade worthwhile around the point they pass forty placements a year or bring on their first coordinator.
Your records hold children's names and ages, home addresses, school schedules, and candidate identity documents. However you store that, access should be deliberate: named people, roles rather than open links, and a clear answer when a family asks what you hold and how long you keep it.
A base can be locked down carefully, and many are. The risk is drift, since a view shared once for a temporary contractor rarely gets unshared. Whichever tool you land on, put a yearly reminder in your calendar to review who can open the candidate and family records.
Yes. Export each table as CSV and import candidates, families, and placements, mapping your columns to the standard fields. Free text notes come across intact. Owners usually bring active and recent records and archive anything older than about four years as a flat export.
Often, yes. With six or eight searches a year you can hold the whole picture in your head and a simple sheet is honest tooling. The pressure builds when several searches run at once and follow-up calls start slipping, which is usually somewhere past twenty placements a year.
Standard stages cover sourced through placed, and you can add your own attributes for things like swim supervision, special needs experience, or second languages. What you cannot do is rename the underlying placement concepts, since the fee, guarantee, and follow-up reporting are built on them.
Comparison
Bullhorn is built for recruiting firms running volume desks with recruiters and account managers, while NannyMatchDesk is built for the owner who runs a household search end to end herself.
Comparison
Zoho Recruit is a flexible applicant tracking system you shape to any industry, while NannyMatchDesk comes shaped for family requirements, reference calls, and household employment paperwork.
Two products read very differently on a page and differently again in the middle of a search. Send one placement you closed last year and we will rebuild it here while you watch: the family brief, four screened candidates, two former employer references each, the background authorization, the signed work agreement and the day three call. If the other product suits your agency better, that shows up just as quickly.