Guide · EasyCofounder

How to pitch your project to a future co-founder

Convincing a future partner is not the same as convincing an investor: it is not just about proving the market is big, but about making someone want to spend several years of their life on the project, alongside you. This guide offers a simple structure and practical advice.

Updated on 5 min readBy the EasyCofounder team

In short

To win over a future co-founder, spend a few minutes presenting the problem and who it matters to, the evidence you already have, what you bring, the role you are offering them and what you offer in return. A co-founder is looking for a problem that interests them, a reliable partner and a role that matches their ambitions: your pitch must address all three, then open the door to a trial collaboration.

Contents
  1. How does a pitch to a co-founder differ from an investor pitch?
  2. How should you structure your pitch?
  3. What does a future co-founder want to know?
  4. Which questions should you anticipate?
  5. Which mistakes should you avoid?
  6. Where can you present your project to potential co-founders?
  7. How do you tailor your pitch to the profile you want?
  8. What should you do after the pitch?
  9. Frequently asked questions
  10. About this guide

How does a pitch to a co-founder differ from an investor pitch?

A pitch to a future co-founder is a short presentation of the project designed to make someone want to partner with you. Unlike an investor, the other person is committing their time, their career and often their income: they are judging the project, but above all the working relationship and the role on offer.

Investor or co-founder: different expectations
InvestorFuture co-founder
What they commitMoneyTheir time and career
What they assess firstMarket, traction, potential returnProblem, team, role on offer
What convinces themGrowth potentialPurpose, trust, autonomy
Expected next stepNegotiating termsTrial collaboration, then partnership

How should you structure your pitch?

  1. 1The problem: who has it, how it shows up, why it matters.
  2. 2The evidence: interviews conducted, first users, sales, concrete feedback.
  3. 3The solution you have in mind and what already exists (mock-ups, prototype).
  4. 4What you bring: skills, network, time, funding.
  5. 5The role on offer: responsibilities, autonomy, expected commitment.
  6. 6What you offer: co-founder status, an equity stake to be discussed, starting conditions.
  7. 7Next steps: a trial collaboration on a concrete goal.

Keep it honest and concrete: a future co-founder will be more convinced by three specific pieces of customer feedback than by ambitious projections.

What does a future co-founder want to know?

  • Is the problem real, and is it interesting to them?
  • Why you, and why now?
  • What role will they really have, and with how much autonomy?
  • How will decisions be made and equity be split?
  • How will the project be funded over the coming months?
Example of a short pitch

“Architecture practices lose a huge amount of time tracking their building sites by email. I was an architect for eight years and I’ve interviewed about twenty practices: they all describe this problem. Three of them are ready to test a tool as soon as it exists. I take care of customers and the functional side of the product; I’m looking for a technical partner to build the tool, with a real CTO role and a significant equity stake. I suggest we build a first prototype together over six weeks to see whether we work well together.”

Which questions should you anticipate?

Prepare honest answers, including when the answer is “I don’t know yet”:

  • How long can you fund the project without income?
  • Who else have you approached, and why didn’t it work out?
  • Are you prepared to rethink the idea if customers say something different?
  • How do you see the equity split?
  • What happens if one of us wants to stop?

To structure your answers on equity: splitting equity between co-founders.

Which mistakes should you avoid?

  • Talking only about market size without showing the problem real customers experience.
  • Offering an executor’s role (“you code, I decide”) to someone you want as a co-founder.
  • Being vague about what you offer, hoping to settle equity “later”.
  • Overselling your progress: lost trust is hard to win back.
  • Demanding full commitment straight away instead of offering a trial period.

Where can you present your project to potential co-founders?

Your pitch is useful in every encounter: startup events, your personal network, incubators. On EasyCofounder, it becomes the basis of your project listing, read by talented people looking to co-found. See also the guide to finding a co-founder and, if you are looking for a technical profile, how to find a technical co-founder (CTO).

How do you tailor your pitch to the profile you want?

The same project is not presented in the same way to a developer, a salesperson or an industry expert. Highlight what matters to each:

Tailoring your pitch to the future co-founder
Target profileWhat interests themWhat to highlight
Technical (CTO)An interesting problem to solve, freedom over technical choicesEvidence of customer demand, decision-making role on the product
Business / salesA sellable product, an accessible marketPrototype, first users, a precise target market
Product / designUsers to understand, an impact on the experienceUser interviews, journeys to improve
Industry expertA problem they know well, a credible opportunityUnderstanding of the industry, potential partners

What should you do after the pitch?

A successful first conversation is only the start. The next step must be concrete and time-limited:

  1. 1Send a short written summary: the problem, what exists, the role on offer.
  2. 2Propose a shared goal over a few weeks (prototype, customer interviews, first sales).
  3. 3Set up a regular check-in to take stock together.
  4. 4At the end of the period, decide together what comes next: partnership, adjusted roles or stopping.

Frequently asked questions

How long should a pitch to a future partner last?

A few minutes are enough to cover the essentials. What matters most is the conversation that follows: questions, answers, discussion about roles and next steps.

Do I need a pitch deck?

It is not mandatory. A few mock-ups, a prototype or customer feedback are often more convincing than a long presentation.

Should I talk about equity in the first conversation?

It is useful to say from the start that this is a co-founder role with an equity stake, then discuss the details once interest is confirmed, ideally after a period of working together.

How do I present a project that is still at the idea stage?

Highlight the problem, the interviews you have already done and your motivation. Be transparent about what still needs validating and offer to validate it together.

How do I convince a co-founder who already has a job?

Show a concrete project and evidence of demand, offer a role that matches their experience and a trial period compatible with their current job. Be clear about when a full-time commitment will become necessary.

Should I ask for a non-disclosure agreement before pitching?

When looking for a partner, many founders share their idea without a prior agreement, as the value lies mainly in execution. If sensitive information is involved, an NDA may be justified: seek advice.

Publish my project

Your pitch becomes your listing, read by people ready to co-found

Further reading

About this guide

This guide was written by the EasyCofounder team — a platform that connects founders, talents and startups (a service by IRPEA) — and was last updated on November 4, 2026. It draws on common startup practice and on the questions our members ask.

It provides general guidance and is not legal, tax or financial advice. For your own situation, consult a qualified professional (lawyer, accountant) and the official resources available in your country.