What a business model actually is
Short answer: no, you do not need a finished business model before finding a co-founder.
But you do need something almost as important: a clear problem, some evidence you are serious, and an honest way to talk about the money question.
Founders often stall here.
They wait for a perfect plan before they start talking to potential partners, and the waiting costs them months.
This guide explains what you need before co-founder conversations.
It also covers what to say when your business model is unresolved, and how a small trial project tests the partnership itself.
A business model is simply the answer to one question: how does this work make money?
Who pays, for what, and why does the math hold up?
It is not a forty-page plan.
It is a working hypothesis you can state in a sentence or two, test, revise, and share honestly while it is still unfinished.
If that definition feels fuzzy, the business model glossary entry breaks the concept down further.
Why waiting for a finished model slows you down
There are two reasons the wait-and-perfect approach backfires.
First, co-founder search is already slow.
Y Combinator built a co-founder matching platform because finding a compatible partner is hard.
They encourage matched founders to work together on a time-boxed trial project before committing Y Combinator's co-founder matching announcement.
If the search itself takes time, adding a prerequisite of a polished model only extends it.
Second, a business model built alone, before you have a partner challenging your assumptions, is usually weaker.
A co-founder with different experience will poke holes in your pricing idea or question who the customer really is.
That friction is valuable.
You want it early, not after you have fallen in love with a plan.
What you do need before the conversation
While you do not need a finished model, showing up with nothing is also a mistake.
Potential co-founders want signals that you are serious and that working with you will be productive.
Here is a practical checklist.
- A specific problem. Not a vague market, but a concrete problem you can describe in plain language, ideally one you understand from personal experience or conversations with people who have it.
- Some evidence of progress. A few customer conversations, a rough prototype, a landing page, or even a well-documented set of notes. Progress matters more than genius. Y Combinator partner Michael Seibel writes that he is much more interested in progress than in clever ideas Michael Seibel's YC pitch advice.
- A unique insight, even a small one. Seibel describes a unique insight as something you know about the problem that others do not, usually built from customer conversations, analysis of existing products, or personal experience. It does not need to be grand. It needs to be specific.
- An honest answer about money. You can say the model is unresolved. You cannot dodge the question.
- Clarity about what you want. Are you looking for a full-time partner, a technical co-founder, or someone for a specific trial project? Say it directly.
If you are earlier than this checklist assumes, start with validation work instead.
The guide on how to validate a business idea before building covers the first evidence-gathering steps.
Then testing demand before you launch shows how to check whether anyone wants the thing.
How to say your business model is unresolved
This is the part founders dread, and it is easier than it looks.
Seibel notes there are two types of startups: those that know how they will make money and those that have not figured it out yet.
The second group is not disqualified.
His advice for that group is to avoid pretending otherwise and to avoid offering a potpourri of possible models.
Pick the most likely simple answer and own it Michael Seibel's YC pitch advice.
In practice, that means your answer to a potential co-founder can sound like this:
'We know teachers pay out of pocket for classroom tools today. Our working assumption is a low monthly subscription, but we have not validated pricing yet. That is one of the first things I want to test with a partner.'
Notice what this does.
It names who pays today, states a simple hypothesis, admits what is unproven, and turns the gap into a shared task.
That is far more attractive than either a fake certainty or a shrug.
What to avoid:
- Listing five possible revenue streams as if variety were a strength. Seibel calls this a potpourri of business models and describes it as a mistake from his own experience at Justin.tv.
- Hiding the question entirely. A co-founder will ask eventually, and discovering you avoided it damages trust.
- Dressing up uncertainty in jargon. Seibel's broader advice applies: eliminate jargon and marketing speak, and aim to be clear rather than to sound impressive.
What to tell a potential co-founder about revenue
When the revenue conversation comes up, structure it around three honest statements:
- Who has the problem and who might pay. Even without a model, you can usually name the person feeling the pain and whether they already pay for alternatives.
- Your current best guess. One simple hypothesis, stated as a hypothesis. A subscription, a single purchase, service fees, whatever fits your space. Seibel points out that most unresolved startups eventually either copy the predominant model in their space or grow and turn on advertising, so starting from the obvious candidate is reasonable.
- How you plan to find out. A short list of next tests: customer interviews, a paid pilot, a pre-order attempt. This shows the gap is on your roadmap, not a blind spot.
A co-founder hearing this learns two useful things: you are honest under pressure, and you know how to turn unknowns into experiments.
Both are better signals than a memorized revenue slide.
Use a small project instead of a big promise
Once the conversation goes well, resist the urge to ask someone to commit to a company on the spot.
Y Combinator explicitly encourages matched founders to work together on a time-boxed trial project before deciding.
The trial should have clear expectations and goals, per Y Combinator's co-founder matching announcement.
A trial project lets both of you observe how the other actually works: how they communicate, handle setbacks, and make decisions when the plan meets reality.
A good trial project is small, real, and short.
It should produce something a customer or user could react to, not just internal planning.
If you are unsure how to scope it, the guide on choosing the right small project before you commit helps pick something sized for a first collaboration.
The proof sprint guide shows what a tight timeline looks like in practice.
Here is the useful twist: the trial project can also be your business model test.
If your unresolved question is whether customers will pay, design the trial so it produces an answer.
A pre-order attempt, a paid pilot, or a simple offer to a handful of real prospects turns the partnership trial and the revenue test into the same exercise.
You learn about your partner and your pricing at once.
Tradeoffs to weigh
Searching before the model is finished has real costs too, and it is fair to name them.
- You may attract partners who disagree on monetization. If one of you assumes advertising and the other assumes subscriptions, better to surface that in the first conversations than after equity is discussed.
- An unresolved model makes some conversations harder. Certain experienced operators will want more certainty before engaging. That is a filter, not a failure; it tells you who is a fit for this stage.
- Waiting has its own cost. Momentum and morale matter in early work. Y Combinator reports that building with a co-founder helps with productivity and morale, and that only four of the top 100 YC companies came to YC without a co-founder Y Combinator's co-founder matching announcement. Stalling the search to perfect a plan trades that advantage for an illusion of readiness.
On balance, the evidence points one way: clarity about the problem and honesty about the unknowns beat a polished plan nobody has stress-tested.
A simple sequence you can follow
- Write your problem statement and your unique insight in two plain sentences. Test them with the email trick Seibel describes: send them to a smart friend and ask them to explain it back. If they ask clarifying questions, revise.
- State one simple revenue hypothesis and label it as unproven.
- Start co-founder conversations with that honest package: problem, insight, progress so far, open money question, and a clear ask.
- Propose a time-boxed trial project that doubles as a revenue test.
- Let the results of the trial refine both the partnership and the model.
For background on shaping the underlying idea first, see the article on generating business ideas that actually work.
The piece on turning everyday problems into business ideas is also a useful starting point.
The bottom line
You do not need a finished business model to find a co-founder.
You need a specific problem, a small amount of real progress, a unique insight you can state plainly, and the honesty to say the money question is still open.
Pair that with a short trial project.
You give a potential partner everything needed to decide whether to build with you, while giving your business model its first real test.
Take the next step with Ideoreto. Use the ideas in this guide as a starting point for your next project.
Register for Ideoreto to get started.