How to ask someone to be your cofounder, step by step, with example messages

Most people picture asking someone to be their cofounder as one big moment, like a proposal. In practice it works better as a series of smaller asks, each one easy to say yes or no to. You ask for a conversation. Then for a second one. Then for a few weeks of work on something real. By the time you ask the actual question, you both have most of the answer.

Gloria Lin, describing her own cofounder search to First Round Review, said she "dated" six potential cofounders over the course of a year, and spent four months working with the person she chose before committing (First Round Review). That's slower than most people expect, and it's a useful benchmark.

How to ask someone to be your cofounder: the short version

1. Know what you bring. Write down what you've done so far and what you'll keep doing. 2. Know what you're asking for. The role, the hours, the timeline and what you can't offer yet. 3. Check they're in a position to say yes. A new parent in a new job is a different conversation from a friend who just left theirs. 4. Send a short first message that asks for a conversation, not a commitment. 5. Use the first call to learn, not to pitch. Find out what they want. 6. Work together for two to four weeks on something with a result you can both judge. 7. Ask the real question, give them time, and agree a date to decide.

Step 1: Know what you bring

Good people have options. Before you ask anyone to give up evenings, a job or other projects, be clear about why working with you is worth it. The MaRS guide to recruiting a cofounder makes "understand what you bring to the table" one of its first steps, before you start approaching anyone (MaRS).

Useful things to have, roughly in order of how much they persuade:

• Customers or users. Even a handful of people who pay or use something weekly changes every conversation.
• Conversations with the people who'd pay. Notes from 20 or 30 calls show you've tested the problem with real people.
• Something built. A prototype, a landing page with sign-ups, a spreadsheet that people actually use.
• Knowledge of the field. Years in the industry you're building for, or a clear account of how buyers decide.
• Your own commitment. How many hours you work on this now, and when you'll go full-time if you haven't already.

If you have none of these yet, say so honestly and ask for something smaller. "I want to explore this problem with someone for a month" is an easier yes than "be my cofounder".

Step 2: Know what you're asking for

Vague asks get vague answers. Write down:

• The role. What they'd own: building the product, selling, design, operations, research.
• The hours. What you need now, and what you'd need in six months.
• The timeline. When you hope to be working on this full-time, if that's the plan.
• Where. Same city, remote, or a mix.
• What you can't offer yet. If there's no salary for the first months, say so before it becomes a surprise.

Titles, who leads, and how you'd split ownership and other terms come later, once you've worked together and both want to continue. Raising them in the first message makes the ask feel like a contract.

Put all of this on half a page. MaRS suggests a cofounder profile of no more than half a page, covering the main role, ideal experience, minimum skills and top traits. You'll use it to write messages, and you can send it after the first call.

Step 3: Check they're in a position to say yes

The best person you know may not be able to say yes right now. Before you ask, think about what you know of their situation:

• Their job. Did they just start, or are they a year in and restless? Are they waiting for a bonus or a promotion?
• Money. How long could they live on savings? Do they support anyone?
• Life events. A new baby, a move, a wedding, a visa that depends on an employer.
• Other projects. Are they already building something of their own?

None of this means you shouldn't ask. It changes what you ask for. Someone who can't leave a job for a year might still give eight hours a week to a trial, and that's worth knowing.

Step 4: Write the first message

The first message has one job: to get a conversation. It shouldn't ask anyone to be your cofounder.

What works:

• Short. Five to eight sentences. Long messages tend to get saved for later and forgotten.
• Specific about them. Say why you're writing to this person in particular: something they built, wrote, said or did.
• Specific about you. One or two lines on what you're working on and what you've done so far.
• A small, clear ask. Thirty minutes, a call next week, coffee after the event.
• An easy out. "If it's not for you, no problem" makes it easier for them to reply honestly.

What not to put in a first message

• "Want to be my cofounder?" It's too big a question to answer from a message.
• Long descriptions of the idea. Two sentences are enough to judge whether it's interesting.
• Pressure. "I need an answer by Friday" or "this is a once-in-a-lifetime chance" ends conversations.
• Ownership or titles. These belong much later, once you've both decided to continue.
• Flattery without detail. "You're amazing" says nothing. "Your post on X changed how I think about Y" says you read it.

Example messages to a potential cofounder

The messages below are examples we wrote for this guide. They're not quotes from real people. Change the details so they're true for you.

Asking a friend

I've been working on the scheduling problem I keep complaining about at dinner, and I've now spoken to 25 clinic managers who have it too. I'd like to talk it through with you properly, because you think about operations better than anyone I know. Could we get a proper hour this week, not over drinks? I'm not asking you to quit anything. I want your honest view on whether it's worth doing, and whether it's something you'd ever want to do together. Saying "not for me" is a completely fine answer.

Why it works: it separates the friendship from the ask, says why them, and gives a clear, low-pressure next step.

Approaching a former colleague

We worked together on the billing migration in 2023, and I still think about how you handled the vendor that kept missing deadlines. I've left to build a tool for small logistics firms that automates customs paperwork, and four firms are now testing it. I need someone who can sell to operations managers, which is what you did so well. Would you have 30 minutes in the next two weeks? I'd like to show you what I have and hear what you think.

Why it works: shared history is the strongest evidence you have, so lead with it. Name a specific thing they did.

Messaging someone you don't know online

I read your thread on why procurement software fails in mid-sized manufacturers, especially the point about approvals living in email. I'm building something aimed at exactly that, and I've had 18 conversations with plant managers so far. I'm a backend engineer and I'm looking for someone who knows this world from the inside. Would you be open to a 20-minute call to tell me what I've got wrong? If it goes well, I'd love to talk about working on it together, but a call is all I'm asking for now.

Why it works: it proves you read their work, asks for their expertise first, and is honest that you're looking for a partner without making that the ask.

Following up with someone you met at an event

We talked at Saturday's hackathon about the food waste data from student kitchens, and I've been thinking about your idea of starting with one canteen instead of a whole campus. I tried it: I spoke to the manager at my college's canteen on Monday, and she'd let us test something next month. Would you want to meet this week and plan what we'd build? It would be about four weeks of evenings.

Why it works: it follows up quickly, shows you acted on what they said, and asks for something with a clear size and end.

Writing to someone you matched with

Thanks for the match. Our compatibility breakdown shows we line up on most of how we like to work and differ in a couple of places, which seem worth talking about early. I'm working on software for independent pharmacies and I've been full-time on it for two months. Your experience in retail operations is exactly the gap I have. Could we book 30 minutes this week?

Why it works: when you've both opted in to looking, you can be more direct. Using what you already know about each other gives the first call a starting point.

Asking to join someone else's startup

I've used your invoicing tool since the beta and I've sent you three bug reports, so you may know my name. I saw on your site that you're working alone and looking for help with growth. I've run paid acquisition for two consumer apps, and I have ideas about why your sign-up page loses people on mobile. Would you be open to a call? I'd be glad to do a small piece of work first so you can see how I think.

Why it works: if you want to join someone as a cofounder, show what you'd add and offer to prove it. Founders get many vague offers of help and very few specific ones.

Step 5: Run the first conversation

The first call is for learning, not selling. Aim for 30 to 45 minutes and leave them talking for more than half of it.

A simple shape:

1. Their story first. What are they working on, what do they enjoy, what are they looking for next? 2. Your half page. What you're building, what you've done, what you need. 3. What each of you wants. Lin's question works well here: "In an ideal world, what are you imagining?" It invites an honest answer without asking for a decision. 4. Time and timing. How much time could they give, and when? What would have to be true for them to go full-time? 5. A next step. Another call, a meeting with a customer, or a small piece of work together.

Keep the bigger questions about money, conflict and long-term goals for the second or third conversation. Our questions to ask a potential cofounder has 20 of them, grouped by topic, with what to listen for.

After the call, send a short thank-you with whatever you promised: the notes, the deck, the customer contact. Following through on small things in the first week is the cheapest proof you can give of how you'll behave later.

Step 6: Work together before the real ask

Conversations show you how someone talks. Work shows you how they work. Before you ask anyone to be your cofounder, do something real together with a result you can both judge.

Lin suggests timeboxing this exploratory period to about two weeks, to learn fast and move quickly. Good trial projects have an end date and a result that someone outside the two of you can see:

• Twenty customer interviews and a one-page summary of what you heard.
• A working prototype that five target users try.
• Ten booked sales calls from cold outreach.
• A landing page with a clear offer and a sign-up target.

Agree the goal, the end date and a call to review it before you start. During the trial, notice how they handle the dull tasks, the disagreements and the deadline. Our guide to cofounder green flags lists the signals worth looking for, and the red flags guide covers what should make you stop.

Step 7: Make the actual ask

If the trial went well and you both want more, ask directly. By now it shouldn't be a surprise. Say what you saw, what you'd like and what happens next:

These four weeks went better than I hoped. You booked more calls than I could have, and you changed my mind about who our first customer should be. I'd like us to build this company together, with you leading sales and me leading the product. I don't need an answer today. Could we each think about it for a week, write down what we'd need to make it work, and meet next Thursday to decide?

That's another example of ours. The structure matters more than the words: what you saw, what you're proposing, and a date.

Give them time. A yes given on the spot under pressure is weaker than a yes given after a week of thinking. Lin said she most appreciated it when there was a clear go or no-go date.

How to handle a no

A no is useful information, and it ends cleanly if you let it.

• Thank them, and mean it. They gave you time.
• Ask one question. "Is there anything that would have changed your answer?" Sometimes the answer is timing, and timing changes.
• Ask for one introduction. "Is there anyone you think I should talk to?" People who say no often know someone who'd say yes.
• Don't argue. Trying to talk someone out of a no rarely works, and even when it does, you've started a partnership with someone you had to persuade.
• Keep in touch. Send a short update in three months. Some of the best cofounders said no the first time.

How to handle a maybe

A maybe usually means one of three things: the timing is wrong, something specific is worrying them, or they're being polite. Find out which.

Ask: "What would make this a clear yes, and what would make it a clear no?" If the answer is specific, such as "I need to see ten paying customers" or "I can't leave until my project ends in March", you have a plan. Agree on a date to talk again and what you'll each have done by then.

If the answer is vague and the maybe repeats for months, treat it as a no and keep looking. You can stay friendly and keep them updated.

What if they don't reply?

People are busy and messages get buried. Send one follow-up after about a week, shorter than the first message: "Just bringing this back to the top of your inbox. No worries if the timing's wrong." If there's still no reply, let it go.

If someone goes silent partway through a trial, ask directly whether they want to continue. Lin described being ghosted once by a potential cofounder, and her advice was to "have the courage to talk about these potential partnerships directly, especially when it's not a fit." Hold yourself to the same standard: if you decide not to continue, tell them.

How to ask a friend to be your cofounder

Friends are the easiest people to ask and the hardest to hear no from. They also carry a particular risk. Adam Grant, writing in Psychology Today about Noam Wasserman's research on nearly 10,000 founders of technology and life sciences startups, reported that "the least stable founding teams were friends" and that each friendship in a founding team increased the rate of founder turnover by 28.6% (Psychology Today).

That doesn't mean you shouldn't start a company with a friend. It means you should test it like any other partnership:

• Separate the friendship from the ask. Say out loud that the friendship matters more than the company and that no is a fine answer.
• Make the ask in a work setting. A scheduled call or a meeting, not the end of a party.
• Run a trial anyway. Friends often skip it because they think they know each other. You know each other socially, which is different.
• Have the hard conversations early. Money, hours, roles and what happens if one of you wants to stop are harder to raise with a friend, so raise them sooner.

Your friend may say no to protect the friendship. Jason Lemkin of SaaStr, answering a question about how to turn down a friend's request to become a cofounder, suggested telling the friend that you want to stay friends and that working together would wreck that (SaaStr). If you hear it, take it at face value.

When is the right time to ask someone to be your cofounder?

Not in the first conversation, and not after six months of vague meetings. A few signs the time is right:

• You've worked on something real together and both want more.
• You've talked about the hard topics: time, money, goals, what happens when you disagree.
• They're asking about next steps before you raise them.
• Something in their life is about to change: a job is ending, they're deciding on an offer, a project is wrapping up. If you're serious, ask before they commit elsewhere.

If you're unsure whether you need a cofounder at all, our post on solo founder vs cofounder is a good place to start.

Where Foundinity fits

The hardest part of asking is often finding someone worth asking. Your network may not include anyone with the skills you need, and strangers online have no way to tell if you're serious.

On Foundinity, everyone you match with is also looking, so the first message doesn't have to explain why you're writing. You state what you need in a cofounder, and answer an assessment about how you work: commitment, working style, ambition, personality, goals, values, alongside your skills and interests. A multi-trait algorithm built on established psychological compatibility models ranks the people you see.

• A compatibility breakdown on every match shows where the two of you align and where you differ, which gives your first message and first call something specific to talk about.
• A 10-day clock on each match keeps conversations from stalling, and you book the intro call in the app.
• Your profile isn't public. Only compatible members can see it, and an "exploring" status lets you look before you commit.
• Pricing: free to get started; Plus is $5 a week or $15 a month. See how it works.

FAQ

How do you ask someone to be your cofounder?

In stages. Send a short message asking for a conversation, use the first call to learn what they want, work together on something real for two to four weeks, and then ask directly, with a date to decide. Say clearly what you bring and what you're asking for.

How do you approach a potential cofounder you don't know?

Write a short, specific message: why you're writing to them in particular, what you're working on and what you've done so far, and a small ask such as a 20-minute call. Don't ask them to be your cofounder in the first message.

How do you convince someone to be your cofounder?

Show evidence rather than persuade: users, customer conversations, something built, and your own commitment. If you have to work hard to convince someone, that tells you something too. The best partnerships usually start with both people wanting it.

What should I say in a message to a potential cofounder?

Who you are, why them, what you're working on in one or two sentences, what you've done so far, and a small request with an easy way to say no. Five to eight sentences is enough.

Should I ask my best friend to be my cofounder?

You can, but treat it like any other partnership: ask in a work setting, separate the friendship from the ask, run a trial project and have the hard conversations early. Research reported by Adam Grant found founding teams of friends were the least stable.

How long should I know someone before asking them to be my cofounder?

Long enough to have worked on something real together. A two to four week trial is a reasonable minimum. Many founders take several months; Gloria Lin worked with her eventual cofounder for four months before committing.

What if a potential cofounder says maybe?

Ask what would make it a clear yes and what would make it a clear no. If the answer is specific, agree a date and a goal. If the maybe stays vague for months, treat it as a no and keep looking.

Should I talk about titles or ownership in the first conversation?

No. Those come later, once you've worked together and both want to continue. Bringing them up early makes the conversation feel like a negotiation before you know whether you want to work together.

How do I ask someone to join my startup as a cofounder rather than an employee?

Be clear about the difference: a cofounder shares the risk, owns a part of the company's direction and often works without a salary at first. Say which you're offering, what they'd own and what you can't offer yet, then run a trial like any other.

What if someone asks me to be their cofounder?

Use the same steps from the other side: ask what they've done so far, what they need, how much time they expect, and suggest a short project together before either of you decides. Our questions to ask a potential cofounder work both ways.

Sources

• "The Founder Dating Playbook: Here's the Process I Used to Find My Co-Founder", interview with Gloria Lin, First Round Review, 30 September 2019, checked 11 November 2026.
• Jon E. Worren, "MaRS Guide: Recruiting your co-founder", MaRS Discovery District, checked 11 November 2026.
• Adam Grant, "Don't Start a Company with Your Friends", Psychology Today, 16 October 2014, reporting research by Noam Wasserman, checked 11 November 2026.
• Jason Lemkin, "How do I reject a friend's request to become co-founder with him without spoiling the friendship?", SaaStr, checked 11 November 2026.
• Foundinity pricing and features from foundinity.com, checked 11 November 2026.