Marketplace AB5 Compliance: Build It Right or Lose (Simply Explained)

A while back I co-founded a marketplace in California. The idea was simple: connect families with independent local providers, the kind of work where someone comes into your home and works with people you care about.

But before I wrote a single line of the booking software, I had to answer one question that could have killed the whole company. Are these providers contractors or employees?

In California, you don't always get to decide that yourself. The law decides for you. And if you get the answer wrong, you're not running a marketplace anymore. You're running an unlicensed staffing agency with a six-figure tax bill quietly piling up in the background.

Most founders treat the legal stuff as a "figure it out later" problem. That's like pouring the foundation of a house on a crack in the ground, then acting shocked when the walls split after you've moved in.

So I made the legal calls first. Then I built the product on top of them.

The Law That Trips Up Marketplaces

California has a rule called AB5. In plain English, it assumes every worker is your employee unless you can prove three things, all at once:

One, you don't control how they do the work. Two, the work is outside your company's main business. Three, the worker runs their own independent business.

Miss any one of those, and the worker is legally your employee. Full stop.

The middle one is the killer. If your business IS the service, then your providers are doing your core work by definition. A house-cleaning company can't easily argue its cleaners are doing something outside its usual business. The cleaners ARE the business.

That's the trap most marketplaces walk into without realizing it.

And regulators know marketplaces only work because they avoid paying employer costs. So they go after them. The big gig platforms have been sued and fined into the hundreds of millions over exactly this question. They had armies of lawyers and still bled.

A brand-new startup doesn't survive that. So the math isn't "we'll fight it later." The math is "we never build a model that invites the fight." That has to be answered before the product exists.

Three Decisions I Made Before Touching the Code

One: We connect people, we don't employ them.

I built the company as a true matchmaker. A venue that connects families with independent providers, not a company that delivers the service itself.

That meant providers actually ran their own businesses. They set their own rates. They chose which jobs to accept or turn down. They built their own client relationships. They worked under their own name, not ours.

Here's the honest part: you cannot fake this. If you control schedules, set fixed pay, and train people on your method, no clever paragraph in the fine print saves you. A court looks at the real relationship, not the document you made everyone sign. The structure has to live in how the business actually runs.

Two: Providers carry their own insurance.

Every provider had to bring their own liability insurance to join. We required real coverage, verified the day they signed up.

This did two things. First, it proved they were genuine independent businesses, because real businesses carry their own insurance. Second, it protected us from being the deep pocket when something went wrong. And in a service where someone enters your home and works with vulnerable people, something eventually goes wrong.

By putting the insurance on the provider, the risk sits with the person actually doing the work. If we'd carried that risk ourselves, one bad incident could have ended the company.

Three: We took a fee, not paid a wage.

This is the one founders get backwards most. We charged a 10 to 15% fee on each booking, plus listing fees. We never paid providers a wage and marked up the service.

Why does this matter? Think about how the money flows. If you collect the full payment from the customer and then pay the worker a wage, you look exactly like an employer. You're the source of their paycheck.

But if the customer pays the provider directly, and you just take a clear fee for making the connection, the picture flips. The provider is the business owner. You're the venue charging for access. No paychecks, no tax withholding, no payroll machinery anywhere in the system.

The important part: I decided the fee model BEFORE I designed the payment system. If I'd wired up the payment processing first and figured out compliance later, I'd have accidentally built a system that made us the employer. Unwinding that means rebuilding the entire financial core of the product.

Why the Order Matters

Step back and look at what happened. The booking flow, the payments, the onboarding, the insurance checks, all of it was shaped by legal decisions made up front.

If I'd built the obvious "easy" version every first-time founder sketches on a whiteboard, it would have looked great. Set the rates. Assign the best available provider. Pay them out. Clean, simple.

And secretly an unlicensed staffing agency racking up a tax bill from day one. A beautiful product sitting on a model that fails the test on every single point.

Now, the honest limits. I'm not a lawyer, and you need one for your specific situation. The law has exceptions for certain jobs, it keeps changing, and there's constant litigation over the details. What was settled last year may not be settled next year.

So I'm not telling you what your structure should be. I'm telling you the structure is a load-bearing wall, and load-bearing walls get built before the rest of the house, not after.

That's the founder's real job. Not knowing every answer. Knowing which questions hold up the building.

I've built 15 different AI and software systems across heavily regulated businesses, from health products to financial services. The pattern is identical every time. The constraint comes first. The product gets built to fit it.

The cheap version is doing it right the first time. The expensive version is finding out you did it wrong after you have revenue, providers, and a regulator paying attention.

If you're building a marketplace, a regulated service, or anything where the business model itself carries legal weight, that's exactly the kind of thing I help founders work through before they build. We pressure-test the model first, before the code locks in something you can't easily undo.

Thinking about AI for your business?

If this resonated, let's have a conversation. I do free 30-minute discovery calls where we look at your operations and find where AI could actually move the needle, not where it just sounds impressive in a board deck.

Book a Discovery Call