How to build a website like Care.com

Published date: 2024-03-15 Last updated: 2026-09-11

How to build a website like Care.com

Care.com built its business on one of the hardest problems in the service marketplace space: convincing a family to let a stranger into their home to care for a child or an aging parent. Twenty years and two changes of ownership later, that trust problem is still the whole product.

The platform connects families with caregivers across childcare, senior care, pet care, and housekeeping in more than 20 countries. It has also been through public failure: a $500M sale to IAC in 2020, an $8.5M FTC settlement in 2024, and a resale to Pacific Avenue Capital Partners for $320M in March 2026, a $180M loss for IAC. None of that changed the underlying challenge. This guide covers how Care.com actually works, what the regulatory landscape looks like since the FTC action, and how to build a caregiving platform where trust is engineered in from day one rather than bolted on after a scandal.

What is Care.com and how does it work?

Care.com is the largest online caregiving marketplace in the US, matching families with caregivers across childcare, senior care, pet care, and housekeeping. The platform peaked at 31.7 million combined members (families and caregivers) before going private in 2020, the last publicly disclosed figure (Care.com 10-K). Since the IAC acquisition, user counts are no longer broken out in public filings.

Families search by care type and location, then subscribe to unlock messaging and job posting. Caregivers build a profile with rates, availability, and certifications, and apply to family job posts or appear in search. The June 2025 rebrand was the most significant product shift in years: Care.com added CareProtect (continuous background monitoring for new subscriptions), a 24/7 safety hotline, AI-enhanced search, and expanded categories including adult care, kids' camps, senior living communities, and daycares. CEO Brad Wilson described the change as a shift to "transform Care.com from a transactional platform to a more holistic and guided platform" (Care.com).

How Care.com makes money

Care.com runs a freemium subscription model layered with a transaction fee. Families get a free basic account that lets them browse but not contact caregivers or post jobs. Premium unlocks at $39/month billed monthly, $26/month billed quarterly, or $13/month ($156/year) billed annually, and includes direct messaging, background check results, and job posting. Caregivers pay roughly $9/month for premium profile placement in search results.

On top of subscriptions, Care.com charges families a 12% transaction fee on bookings, with an optional 2% families can add on behalf of the caregiver. Background check add-ons are sold as tiered packages with pricing not publicly disclosed. The fastest-growing line, though, is Care@Work, the B2B enterprise channel where employers buy backup care benefits for staff. Its Enterprise (Care for Business) segment grew 18% in 2024, though Care.com is no longer part of IAC, having been sold to Pacific Avenue Capital Partners in March 2026 (IAC investor relations).

The 2024 FTC complaint surfaced an important structural fact: more than half of the job postings on Care.com came from users on free accounts who could not actually hire anyone. For founders, that's a useful warning. Total listing count is a vanity metric. What matters is how much of your visible supply, or demand, is actually transactable.

What makes Care.com work: key features

Layered background checks. Care.com uses Checkr to run national criminal database checks, county courthouse records, sex offender registry checks across all 50 states, and SSN trace. No check is complete: juvenile records are sealed, aliases create gaps, and fingerprint-based checks aren't standard on consumer platforms. Disclosing exactly what a check does and doesn't cover is now closer to a regulatory obligation than a nice-to-have.

Continuous monitoring. CareProtect, launched in June 2025, alerts the platform if a caregiver's background check record changes after hire. Most competitors run a one-time check at signup and stop there. Ongoing monitoring changes the trust proposition meaningfully, since a clean record at signup says nothing about the next three years.

Certification verification. Care.com collects and displays first aid, CPR, dementia care, and state licensing credentials. Verifying rather than just displaying self-reported credentials requires integration with certifying bodies or manual review, which is expensive to do well.

Recurring booking architecture. Unlike task marketplaces built around one-off jobs, caregiving runs on weekly recurring arrangements. The booking system needs to support recurring schedules, easy modification, and clear cancellation terms, not just single-session checkout.

Session logging. Especially in elder care and special needs care, caregivers log what happened during a session and families review it. This creates an accountability trail that matters when something goes wrong and nobody was there to see it.

Platform-mediated reference checks. References are requested by the platform, not the caregiver, which removes the obvious selection bias of a caregiver picking their own references.

In-platform messaging enforcement. Platforms that let contact move off-platform lose both the ability to intervene in a developing problem and the commission on the transaction that follows.

The competitive landscape

Sittercity has one of the largest caregiver pools in the US and a straightforward listing model, but requires a paid membership to contact applicants, which creates the same free-tier friction that got Care.com in regulatory trouble. The opening: a platform that's transparent about what's included at each price point, with no bait-and-switch between browsing and contacting.

UrbanSitter built its differentiation on a social graph, surfacing sitters used and recommended by friends and neighborhood parent groups. It's strong in dense urban markets with active parent networks but weaker where those networks don't exist yet. The opening: social proof works, but only where the social graph is already dense; a geographically focused competitor can build the same trust signal locally before UrbanSitter does.

Bambino goes hyperlocal, built around neighborhood-level matching. It's a good model for community trust but has limited category breadth compared to Care.com. The opening: hyperlocal focus plus category breadth (childcare and senior care in the same neighborhood network) is an underserved combination.

Helpr specializes in B2B corporate backup childcare, competing directly with Care@Work. It's narrower than Care.com but deeper on the enterprise integration side. The opening: a Helpr-style B2B specialist for senior care backup coverage, a category Care@Work has not built out as thoroughly.

Rover, now owned by Blackstone after a $2.3B acquisition that closed in 2024, dominates pet care specifically and has better category-specific trust tooling for that vertical than Care (Blackstone).com's generalist pet care offering. The opening it creates: Care.com's pet care category is an afterthought inside a broader platform, which leaves room for a specialist that goes deeper on pet-specific verification (vet references, in-home trial visits) than either Rover or Care.com currently does.

No single competitor covers Care.com's full breadth across childcare, senior care, pet care, and housekeeping in one platform. That breadth is also Care.com's biggest operational weakness: trust infrastructure that works for background-checking a nanny doesn't automatically work for vetting a live-in elder caregiver.

How to build a marketplace like Care.com

1. Define your niche within Care.com's category

You are not building a Care.com clone. Care.com's breadth (four care categories, 20+ countries) took two decades and hundreds of millions of dollars to build, and it's still struggling with basic trust execution at that scale. A new entrant wins by going narrow: special needs care, overnight and travel care for parents who travel for work, senior care with clinical coordination, or a single-employer or single-industry version of Care@Work. Pick a niche where you can build deeper vetting than a generalist platform can justify.

2. Validate demand and unit economics

Before building anything, confirm families in your niche will pay for vetted, recurring care, and that caregivers in your niche will accept your terms (background check requirements, commission, payout timing). Talk to 20-30 families and caregivers before writing a line of code. Caregiving unit economics depend heavily on retention: a family that keeps the same caregiver for two years is worth far more than one that churns through five caregivers in six months. Model your business around relationship continuity, not transaction volume.

3. Design your trust and vetting model

Decide your minimum bar before you build anything else: what background check tier is mandatory, what happens if a caregiver's record changes post-hire, how references get collected and verified, and what your incident response process looks like. This decision shapes your entire technical build, so make it early and get legal counsel involved, particularly around mandatory reporting obligations for child or elder abuse disclosures, which apply in most US states.

4. Choose your development approach

Vibe coding from scratch. AI tools like Cursor, Lovable, and Bolt can produce a working caregiver directory prototype quickly. For pressure-testing a concept or demonstrating it to early users, they're genuinely useful. For launching a platform that handles caregiving bookings and sensitive background check data, they're probably not sufficient. What vibe-coded outputs reliably don't produce is the infrastructure underneath: background check API integrations, secure storage of sensitive caregiver data, recurring booking logic, and session logging. A documented Sharetribe experiment ran 60+ hours to reach demo quality but revealed a critical checkout exploit that would have allowed any user to manipulate transaction prices via a direct API call. In a category where platform trust is the core product, that's not a risk worth taking at launch.

Custom development from scratch. Hiring developers gives you full control over every vetting and trust system. A caregiving marketplace sits at Tier 2 complexity: reviews, identity verification, background check integration, and dispute flow push it to $80,000-$200,000 over 16-28 weeks (Codica, RaftLabs). The low end assumes offshore development teams at $15-40/hr; US or Western European teams push toward the top of the range. Custom development makes sense if you need a proprietary vetting pipeline or direct integration with a state's childcare licensing database, something no off-the-shelf platform supports.

Building on a marketplace operating system like Sharetribe. You start at roughly 90% done on the standard marketplace foundation: listings, search, messaging, bookings, payments, and reviews. Your time and budget go toward the caregiving-specific trust layer instead of rebuilding infrastructure that's already solved.

• No-code builder. Configure caregiver listing types (childcare, senior care, pet care, housekeeping), care category filters, availability calendars, booking flows, and payment processing from the Console without writing code. This is the right starting point for validating demand and business model before investing in safety infrastructure.
• AI-assisted development. Connect Claude Code, Cursor, or Codex to Sharetribe's open APIs and open-source template to add a Checkr integration, certification verification fields, a recurring booking module, or session logging. Because Sharetribe already handles the marketplace infrastructure, this carries much lower risk than building the same features from scratch.
• Custom code. Build directly on the developer platform for deeper trust infrastructure like a proprietary vetting pipeline or continuous monitoring workflows, or hire from Sharetribe's Expert Marketplace.

Most founders start with the no-code builder, validate demand, and then layer in the trust infrastructure via AI-assisted development or a developer as the business grows.

5. Solve the cold start problem

Caregiving marketplaces face a sharper version of the standard chicken-and-egg problem: families won't join a platform with no vetted caregivers, and caregivers won't invest time building a profile on a platform with no families. Care.com solved this early by aggressively recruiting caregiver supply in specific metro areas before opening family-side marketing, effectively building local density one city at a time.

A new entrant should do the same at a smaller scale. Recruit and manually vet 20-50 caregivers in one neighborhood or one niche (say, special needs care in a single metro area) before opening signups broadly. Reach out to existing nanny agencies, care cooperatives, or senior center staff who may refer qualified caregivers directly. Run the first matches manually, by hand, even by phone, before automating anything. Launching narrow and tight in one geography or niche beats launching broad and thin across every category Care.com covers, because your early trust signal (a caregiver you personally vetted) is worth more than volume.

6. Build the booking and payment flow

Recurring bookings are the core mechanical difference from a generic task marketplace. Families need to book a weekly Tuesday and Thursday afternoon slot, not a single on-demand session, so your booking engine needs recurring schedule logic, modification workflows, and clear cancellation terms baked in from the start. Payment should flow through the platform, not around it, both for trust and for your commission.

7. Launch and iterate

Launch with a small, hand-vetted caregiver pool in one niche or geography. Track relationship continuity (how long a family stays with the same caregiver) as your core health metric, not just transaction volume. Add automated trust features (background check API integration, continuous monitoring) as volume justifies the engineering investment, not before.

Do you need to build everything Care.com has?

No. Care.com's current feature set is the output of 20 years and hundreds of millions of dollars, including a failed IAC ownership period and an FTC settlement. A useful V1 needs a fraction of that. What it actually requires: a caregiver listing directory with basic profile fields (care types, rate, availability), family-side search with category and location filters, direct messaging that stays on-platform, a payment mechanism, and a one-time background check at signup.

What you can defer: continuous monitoring (expensive and complex to build well), certification verification at scale (do it manually for your first cohort of caregivers), session logging (a simple form works early), automated reference verification (collect manually at first), and anything resembling the Care@Work enterprise segment.

On the "I'll just vibe-code a clone" question: you can build a working prototype with AI tools quickly, but a caregiving marketplace concentrates risk in exactly the places vibe-coded outputs are weakest, background check integrations, secure storage of sensitive personal data, and payment flow security. Starting on Sharetribe's foundation is faster even with AI tools involved, because the payment and compliance infrastructure is already built and tested. Your AI tokens go toward the caregiving-specific trust layer that actually differentiates your platform, not toward reinventing a booking engine or a payment processor.

Trust and safety for a caregiving marketplace

The minimum viable trust bar here is higher than almost any other service category, because the people receiving care are often children, elderly adults, or people with disabilities, and the caregiver typically works alone in a private home with no supervisor. A background check at signup is not optional. At minimum, run a criminal database check and sex offender registry check for every caregiver before they can be booked, and disclose clearly what the check covers and what it doesn't (juvenile records, aliases, fingerprint gaps).

Sharetribe provides the foundation: user accounts with optional identity verification, secure payment processing with the money held until a transaction completes, and structured transaction flows you can customize. What you need to add on top is category-specific: a Checkr or Persona integration for background checks, certification verification fields, a defined incident reporting workflow (who reviews reports, what triggers suspension, what triggers a police referral), and legal review of mandatory reporting obligations in the states or countries you operate in. Get counsel early on whether your platform enters HIPAA-adjacent territory if you handle medical information about care recipients; standard nanny and babysitter matching typically doesn't trigger this, but senior care with clinical coordination often does.

Running a marketplace like Care.com

Ongoing operations for a caregiving marketplace center on a few recurring tasks: reviewing incident reports, monitoring background check renewals, managing cancellation and refund disputes, and keeping subscription and cancellation flows simple and transparent. The FTC's 2024 action against Care.com specifically targeted a buried, multi-step cancellation flow, so a single-step cancellation process is both good practice and, increasingly, a regulatory expectation for any subscription-based marketplace.

Sharetribe handles the transactional plumbing automatically: payment processing, booking calendars, messaging, and review collection all run without manual intervention. That frees your team to focus on the parts that don't automate well, reviewing flagged incidents, following up on caregiver certification renewals, and checking that your visible supply (caregivers who can actually be booked, not just listed) matches what you advertise.

Development costs and timeline

Three realistic scenarios:

Vibe coding from scratch: Free or very cheap to start. A working caregiver directory prototype is buildable in days with tools like Lovable or Bolt. What you can't get from here is a production-ready caregiving platform: background check API integrations, secure storage of sensitive caregiver data, and recurring booking logic all require careful implementation that AI coding tools don't shortcut. A documented Sharetribe experiment logged 60+ hours to reach demo quality and still surfaced a critical checkout exploit. Useful for a proof of concept, not a launch path in a trust-sensitive category.

Custom development from scratch: A caregiving marketplace with background checks, identity verification, and dispute handling sits in Tier 2 complexity: $80,000-$200,000 over 16-28 weeks (Codica, RaftLabs). The low end assumes offshore teams; US or Western European teams push toward the top. Ongoing maintenance typically runs 15-25% of the build cost per year on top of hosting. Custom development makes sense when you need a proprietary vetting pipeline or state-specific licensing database integration that no existing platform supports.

Building on Sharetribe: Subscription pricing starts at $99/month on Lite, $199/month on Pro, and $299/month on Extend (all billed yearly). This covers the core marketplace foundation, listings, search, messaging, bookings, and payments, so most founders reach a live MVP in weeks rather than months. Caregiving-specific features (Checkr integration, certification verification, session logging) are added narrowly on top, via AI-assisted development or a developer, because the transaction engine and payment infrastructure are already built.

Why Sharetribe for building a marketplace like Care.com

Care.com's core marketplace mechanics, listings, search, messaging, booking, payment, are not what makes the business hard to compete with. What makes it hard is the trust infrastructure underneath: the background check pipeline, the continuous monitoring, the credential verification, the incident response process, all of which took Care.com two decades and an FTC settlement to get partly right.

Sharetribe handles the marketplace layer so that's not where your differentiation needs to come from. Your engineering time and budget go toward the trust systems that actually separate a serious caregiving marketplace from a generic services directory. A team that spends four months building a booking engine from scratch is four months behind a team that started on Sharetribe and spent those four months building a better vetting system instead. The no-code builder also gets you to a live marketplace before you've hired a developer, which matters while you're still figuring out which care categories your market needs and which background check tier your caregivers will actually accept.

Frequently asked questions

What is Care.com and how does it work?

Care.com is an online marketplace connecting families with caregivers across childcare, senior care, pet care, and housekeeping. Families subscribe (premium plans from $13-$39/month) to message caregivers and post jobs, while caregivers pay roughly $9/month for premium profile placement. Care.com also charges families a 12% transaction fee on bookings. The platform is now owned by Pacific Avenue Capital Partners after IAC sold it in March 2026.

What happened with Care.com's FTC settlement?

In August 2024, the FTC charged Care.com with two violations: inflating job counts by including postings from users who could not actually hire anyone (over half of postings), and burying subscription cancellation behind a confusing multi-step flow. Care.com settled for $8.5M without admitting wrongdoing, and the FTC distributed $8.1M to 194,207 affected consumers in June 2025. The lesson for founders: supply accuracy and cancellation flows are regulatory risks, not just product decisions.

What background check does Care.com use?

Care.com uses Checkr, covering national criminal databases, sex offender registries, and SSN trace across all 50 states. No background check is complete: juvenile records are sealed, aliases create gaps, and fingerprint checks aren't standard on consumer platforms. Care.com's CareProtect program, launched in June 2025, adds continuous monitoring that flags the platform if a caregiver's record changes after their initial check.

How does a caregiving marketplace handle trust differently than other service marketplaces?

Three factors raise the stakes: the recipients of care are often vulnerable (children, elderly people, people with disabilities), so a bad match has more severe consequences than in most service categories. Caregivers typically work alone in private homes with no external supervisor, so platform vetting is the primary protection. And caregiving relationships are recurring, so a bad match that continues is a sustained problem rather than a single bad transaction.

Who are Care.com's main competitors?

Sittercity has a large caregiver pool but requires paid membership to contact applicants. UrbanSitter uses a social graph model built on parent group recommendations. Bambino goes hyperlocal and neighborhood-based. Helpr specializes in B2B corporate backup childcare. Rover, now owned by Blackstone, dominates pet care specifically. No competitor matches Care.com's exact breadth across childcare, senior care, pet care, and housekeeping in one platform.

Do I need to worry about HIPAA compliance for a caregiving marketplace?

Standard nanny and babysitter matching typically doesn't trigger formal HIPAA obligations, but platforms handling medical information about care recipients, conditions, medications, care plans, may enter HIPAA-adjacent territory that needs legal review. This is especially relevant for senior care or special needs care platforms with clinical coordination. Get counsel before building if your platform will store or transmit health-related information about care recipients.

Can I build a niche caregiving marketplace instead of competing with Care.com directly?

Yes, and it's often the stronger strategy. Care.com covers childcare, senior care, pet care, and housekeeping across 20+ countries, which stretches its trust infrastructure thin across very different vetting needs. Niches like special needs care, overnight or travel care, corporate backup care for a specific industry, or senior in-home care with clinical coordination let you build deeper verification for one caregiver type instead of a shallow version across four.

Related guides

• How to build a website like Urbansitter
• How to build a marketplace for pet services
• How to build a marketplace for pet sitting
• How to build a home cleaning marketplace
• How to build a babysitting marketplace
• How to build a house sitting marketplace