How to test a co-founder before splitting equity

You split 50/50 equity with someone after three weeks of late-night brainstorming. A year later, you're doing all the customer calls and they're checking in every other Thursday. This is how most founding teams fall apart.

The mistake isn't that you picked the wrong person. The mistake is that you promoted excitement into partnership before testing whether they actually covered your biggest operational gap.

Before you hand someone equity, vesting schedules, and decision rights, you need to run a real test. Not a formality—a diagnostic. Here's what that looks like.

Map your risks, not your dreams

Take the next twelve to eighteen months and break them into the concrete operational risks that could kill your company. Not "competitive landscape" or "market timing." Real execution risks. Can you build the product? Sell it? Distribute it? Hire the right people? Raise money? Do you know the domain well enough to make good bets?

Rank them. Which one scares you most? Which one ends the company if it goes wrong?

That's your weakest surface area.

Notice what this reveals. It's not about vision alignment or shared excitement. Those are table stakes. It's about necessity. If your biggest risk is closing enterprise deals and your potential co-founder is also a product person who's never done sales, you don't have a co-founder match. You have two people excited about the same stuff and weak in the same places.

Founding teams collapse when everyone overlaps on enthusiasm but nobody owns the hard missing pieces.

Run a real project, not a vibe check

Give them a real project tied directly to that weak area. Not vague advisor-style intros or a few hours brainstorming. A 30 to 60 day test with a concrete outcome.

If your gap is sales, have them run five discovery calls and report what they learned. If it's fundraising, have them build the investor pipeline and make intros. If it's product, have them ship a feature end-to-end.

Judge them on a few things: Do they take full ownership, or do they need you to manage them? Do they show judgment under uncertainty, or do they need you to de-risk every decision? Are they fast? Do they recover when something breaks?

Most importantly—do they actually reduce the risk, or do they just put in effort?

Effort isn't the same as impact. You can have someone who works hard, shows up to every meeting, and still doesn't move the needle on the thing that matters. If they don't materially close your biggest gap, they're not a co-founder. They might be an advisor. They might be an early employee with meaningful equity. But they shouldn't have co-founder-level ownership or authority.

This sounds cold. It's just honest about what a co-founder actually is: someone whose absence would structurally weaken the company in a way that can't be easily replaced. If you can hire around them, they're not a co-founder.

Surface the money stuff before you talk mission

Let's say the test goes well. They crushed the project. They clearly own the weak area. Now you're ready to talk equity.

Two things matter here.

First, talk about unpaid runway before you talk about vision. Someone can be completely aligned on mission and still unable to survive six months without a salary. Personal cash constraints become company constraints if you don't surface them early. A co-founder who needs consulting gigs or side income to stay afloat will split their attention exactly when you need them most focused.

Second, have the CEO conversation now. Even if you're splitting equity equally, someone needs to be the external face and the internal tiebreaker. Deferring this decision doesn't avoid conflict—it just moves it to a worse moment when the company is under stress and speed matters.

The equity conversation also reveals how someone thinks about risk and contribution. It's not just about percentages. It exposes assumptions. Who's taking what financial risk? Who's doing what work? Who's creating what value? If those assumptions are misaligned now, they turn into resentment later.

Force the conversation. Ask what they think is fair and why. If their logic makes sense and reflects a clear view of who covers what gap, that's a good signal. If they anchor to "we're both working hard so it should be equal," that's a sign they're not thinking operationally yet.

Write the agreement while you still like each other

Put the awkward stuff in writing: roles, IP ownership, decision rights, vesting schedules, what happens if someone leaves, what happens if you need to fire them.

It feels unnecessarily formal when you're just two people in a room excited about an idea. But a co-founder agreement isn't about mistrust. It's about preserving trust under conditions that haven't happened yet.

The agreement is a circuit breaker. It stops small friction from becoming existential conflict. It makes sure that when money appears, or fatigue sets in, or someone wants out, the terms were set by past-you when everyone was optimistic and fair-minded.

Test conflict style, not just skillset

One more thing. The actual risk in co-founder relationships isn't that you'll disagree—you will disagree constantly. The risk is that you'll have incompatible ways of resolving disagreement.

One person wants to hash it out immediately. The other needs time to process. One person defaults to data. The other defaults to intuition. One person thinks being overruled is fine as long as the logic was clear. The other person experiences it as a violation of respect.

You can't discover this through conversation. You discover it by working together on something real where the stakes are unclear and you both have strong opinions. If you've already done the 60-day test project, you've probably seen some version of this. If it felt generative, proceed. If it felt like work to stay aligned, pause.

The framework

Map your risks. Identify the biggest gap. Run a real operating test. Judge on impact, not effort. Surface financial and authority constraints early. Write the agreement while everyone's still friends.

If they pass all of that, you probably have a co-founder. If they don't, you have someone valuable who belongs in a different structural role. Both are fine.

But getting the category wrong is expensive. The point isn't to be paranoid or transactional. The point is to treat co-founder selection as what it actually is: the highest-stakes operating decision you'll make in the first year of the company.