How to validate your startup idea before finding a co-founder

Why validate your idea before looking for a co-founder?

Good co-founders choose projects as much as people. An idea backed by real conversations with customers, a few early sign-ups or a first payment is far more convincing than a slide deck built on assumptions.

Validation also protects you: it is much cheaper to discover that a problem is not painful enough after three weeks of interviews than after a year of development with a partner who has given up their job.

Once you have evidence, presenting the project becomes much easier: see how to pitch your project to a future co-founder.

How do you check that the problem is real?

Start with the problem, not the solution. Write down who has the problem, in what situation, and what it costs them today (time, money, stress, risk). Then go and talk to those people.

• ✓Who exactly has the problem? Be specific: job, company size, context.
• ✓How do they solve it today? Spreadsheets, a competitor, a workaround, nothing at all?
• ✓How often does it happen and how painful is it?
• ✓Have they already spent money or time trying to fix it?
• ✓Who decides and who pays for a solution?

How do you run customer discovery interviews?

Customer interviews are the cheapest validation tool. The goal is to learn about people’s past behaviour, not to collect compliments on your idea.

1. 1List 30 or more people matching your target and reach out through your network, LinkedIn, online communities or industry events.
2. 2Book 20–30 minute conversations and present them as research, not as a sales call.
3. 3Ask about the last time the problem occurred: what happened, what they did, what it cost them.
4. 4Avoid describing your solution until the end, and never ask “would you use this?”.
5. 5Take notes and look for patterns after each batch of five to ten interviews.

How can you test demand before building a product?

Once interviews confirm the problem, test whether people will act. Several low-cost techniques exist:

• Landing page: describe the promise, add a sign-up or “request access” button and send targeted traffic to it.
• Pre-sales or deposits: ask early customers to commit financially before the product exists.
• Concierge test: deliver the service manually to a handful of customers to learn what they really need.
• Wizard of Oz test: show a product interface while the work is done by hand behind the scenes.
• Letters of intent: in B2B, a signed intention to buy or pilot is a meaningful signal.

What should your MVP look like?

An MVP (minimum viable product) is the smallest thing that lets you learn whether customers get value. It is not a stripped-down version of the final product; it is an experiment.

Depending on the case, an MVP can be a no-code prototype, a spreadsheet, a clickable mock-up or a manual service. Building real software is only worth it when simpler versions have stopped teaching you anything new.

If you are not technical, there are many ways to get a first version out: see starting a startup as a non-technical founder.

How do you know if your idea is validated?

There is no universal threshold, but you can set your own criteria before running each test, so the results are not interpreted after the fact.

If the signals are weak, change one variable — the target customer, the problem or the offer — and test again rather than pushing ahead unchanged. Stopping an idea early is a valid, useful outcome.

When should you start looking for a co-founder?

You don’t need a finished product to look for a partner, but you should be able to show what you have learned. Many founders start searching once they have a clear problem, interview notes and a first demand signal.

Some prefer to validate together with their future co-founder: running interviews side by side is also an excellent way to test how you work as a team. Either way, see how to find a co-founder for the next steps.