Who Should Be a Co-owner, and When?

Common Dilemma

Starting a co-op? You’re told to “share ownership.”

But with who? And when?

What if you’re just three people and still figuring it out?

The Control Trap

Some people avoid co-ops because they fear:

Losing their vision

Losing their rewards

Getting outvoted by people who weren’t there at the start

A Better Way to Structure It

Mondragon solved this by creating separate co-ops for separate domains.

Each one retains control of its own lane, but aligns through shared infrastructure.

That Sounds Great… But What If You’re Small?

You can’t form a new co-op every time you need help.

Sometimes you just need:

So When Do You Bring Someone In as a Co-owner?

Ask:

Are they co-building the core offer?

Are they investing time/energy beyond a task?

Would it weaken the mission if they left?

When is a Freelancer Better?

Use freelancers when:

You need support with a specific skill (like accounting)

You don’t have the scale yet to justify a new co-op

You’re still prototyping your model

What If They Want to Be Involved Long-term?

If they become mission-aligned and long-term…

Invite them to form a partner co-op, not join yours.

That way, they keep their domain, and you keep yours.

The Core Principle

Ownership doesn’t have to mean merging.

It can mean partnering through federation, so each person or team controls what they’ve built.

Final Thought

Start small, start practical.

Freelancers are fine.

But when it’s time to share power, do it in a way that protects everyone’s autonomy.

Share this carousel