How to ask a co-founder about runway early

Your co-founder just said yes. You're both pumped. You start sketching equity splits on a napkin.

Stop.

You need to know if this person can afford to do this—not in some motivational "all in" sense, but in the rent-is-due-in-30-days sense.

Most founders skip this part. They treat personal financial details like they're invasive. So they trade the awkward conversation for vague assurances about commitment. Then six months later, someone taps out because they can't cover groceries.

What you're actually asking: Can we both realistically commit under the same time horizon? That's not rude. That's operational.

The chemistry conversation is easy

You're both excited. You both believe in the vision. You both want to build something that matters.

The money conversation feels like you're questioning their commitment. Like you're implying they're not serious enough.

Except commitment doesn't override cash constraints. Someone can be completely aligned on the mission and still unable to survive twelve months unpaid. That's not a character flaw. It just means the timing is wrong or the structure needs to change.

Avoiding the conversation doesn't eliminate the risk. It guarantees you'll discover the mismatch too late.

What you're actually testing

When you ask about runway, you're not testing loyalty. You're surfacing three things:

Realistic commitment windows. Can this person work unpaid for three months? Six? Twelve? If they need income at month four and you're planning for a twelve-month build, that's a structural misalignment you can design around now—or discover catastrophically later.

Risk tolerance and incentive design. If someone needs income soon, they may push for customer revenue when you need to build infrastructure. Or they may want to raise capital fast when bootstrapping longer would preserve control. Neither preference is wrong, but the clash will create friction unless you acknowledge it early.

External stability. Runway isn't just savings. It includes family obligations, health costs, visa constraints, mortgage payments, or dependents. These factors shape decision-making under pressure. You want to know what pressures exist before the pressure arrives.

How to ask without being weird about it

Frame it as mutual planning, not interrogation.

Share yours first. "I have about six months of runway before I need income. What does your situation look like?" That flips the dynamic from interrogation to reciprocal transparency.

Ask in ranges, not exact numbers. "Do you have closer to three months, six months, or a year where you could go unpaid?" This keeps it practical without demanding bank statements.

Tie it to company milestones. "What funding level or revenue milestone would you need to hit before you could go full-time?" This shifts the frame from personal finance to company planning.

Normalize constraints upfront. "Personal limits are real. I'd rather design around them than pretend they don't exist." This signals you're not judging their situation; you're trying to plan responsibly.

Test for flexibility, not just duration. "If cash gets tight at month four, would you consider part-time contract work, or do you need to step back entirely?" The answer tells you whether constraints are negotiable or binary.

What to do with the answers

If your runways align, great. Move forward.

If they don't, you have three options:

Option one: Adjust the timeline. Maybe you both need part-time contract work for the first six months. Maybe you build nights and weekends until you hit a revenue threshold. Slower is fine if both people can sustain it.

Option two: Adjust the structure. Maybe this person is better as an advisor with equity and a small retainer, or an early employee with a generous option grant, rather than a co-founder with equal ownership but misaligned incentives.

Option three: Acknowledge the timing is wrong. If someone needs income now and you need someone full-time unpaid, no amount of passion fixes that gap. Better to find that out in conversation than in a resignation letter.

The part nobody talks about

This conversation isn't just about financial runway. It's also a test of how someone handles uncomfortable operational questions.

If they dodge the question, get defensive, or treat it as a loyalty test, that tells you something about how they handle other hard conversations—investor pressure, co-founder conflict, tough customer feedback.

If they answer directly, ask clarifying questions, and propose practical solutions, that tells you they can separate emotional commitment from operational reality.

Co-founder relationships fail when people confuse alignment on vision with alignment on constraints.

Write it down

Once you have the answers, document them. Not in a formal contract yet, but in a shared working agreement.

"Both of us can commit unpaid through month six. After that, we need $X monthly or a funding milestone. If we hit neither, we'll reevaluate structure or timing."

This isn't pessimism. It's planning.

The goal isn't to eliminate personal financial risk. The goal is to make sure both people are taking the same risk knowingly, rather than discovering halfway through that one person thought this was a three-month sprint and the other thought it was a two-year marathon.

Ask early, ask directly

Ask the question. Early. Directly. Without apology.

Not because you mistrust the person. Because you want the partnership to survive the financial reality of building a company.

The best co-founder conversations aren't the ones that feel easy. They're the ones that surface hard truths while everyone still likes each other enough to design around them.