How to find a technical co-founder (and keep one)

You have the idea, maybe the first customers, and a spreadsheet of everything the product should do. What you don't have is the person who can build it. So you post in a founders' group, ask around, and send a few messages to engineers you admire. Most of it goes nowhere.

This isn't because good engineers don't want to start companies. It's because most searches for a technical co-founder are pitched in a way that gives an engineer no reason to say yes. Here is how to do it differently.

Start with what you bring, not the idea

Engineers who are worth building with hear a lot of ideas. An idea on its own is the least scarce part of a startup, and the pitch "I have the vision, I just need someone to build it" quietly says that you expect them to do most of the work.

What an engineer actually weighs is what you add. Be concrete about it:

Customers or a waiting list. Ten people who have said they would pay is worth more than any deck.
Distribution. An audience, a community, a sales background, relationships in the industry you're building for.
Domain knowledge. You've worked in the problem for years and know where the money and the pain are.
Skills they don't have. Design, product, marketing, fundraising, operations.

Write these down before you look for anyone. If the list is short, spend a few weeks making it longer: talk to customers, build a landing page, collect sign-ups. It is the single best thing you can do for your search.

Be specific about the role

"Technical co-founder" covers very different people. Someone who builds iOS apps, someone who runs backend infrastructure and someone who trains machine-learning models are not interchangeable, and a vague ask attracts vague answers.

Before you start, decide:

What has to be built first? A mobile app, a web product, a data pipeline, hardware.
Which stack, if it matters? If you have a prototype in React Native, say so.
How much time you need from them. Evenings and weekends to start, or full time from day one.
What you are offering. Equity, a salary once you raise, or both. You don't need final numbers, but you need an honest starting point.

Being specific narrows the field, and that is the point. You want the five people who are a strong fit, not fifty who are a weak one.

Look where engineers already are

Group chats and generic founder forums are full of people looking for engineers, and short of engineers looking for founders. Go where engineers spend time and where your specific skills are rare:

Your own network, two steps out. Ask friends who work in tech for introductions to engineers who have talked about wanting to start something. A warm introduction changes the whole first conversation.
Hackathons and build weekends. You see how someone works under pressure in two days, which tells you more than a month of coffee chats.
Open-source and side-project communities. People who build things for fun are often the ones who will build something with you.
Collaboration platforms built around mutual fit. On Collaborators you say what you bring and what you need, and you're shown engineers who need what you bring as well as bringing what you need. A conversation only opens when you both say yes, so nobody gets a cold pitch.

Wherever you look, lead with what you bring and the specific role. "Founder with 200 people on a waiting list for a scheduling app for physiotherapists, looking for an iOS engineer to build the first version with me" will get replies that "looking for a technical co-founder, equity only" never will.

Work together before you decide

The most common mistake is agreeing to be co-founders after a few good conversations. You're choosing someone to make hard decisions with for years. Test it first.

Pick a small, real piece of work you can finish together in two to four weeks: a prototype of the core feature, a landing page with a working sign-up flow, a scrappy version you can put in front of five customers. Then pay attention to:

How they handle ambiguity. Do they ask good questions, or wait to be told exactly what to do?
How you disagree. You will. What matters is whether you can get to a decision and move on.
Pace and reliability. Do they do what they said, when they said? Do you?
Whether they care about the problem. You want someone who starts talking to customers too, not only someone who closes tickets.

If it goes well, you'll both know. If it doesn't, you've lost a few weeks instead of a few years.

The best co-founder needs you as much as you need them. If the relationship only works in one direction, it won't survive the first hard month.

Talk about equity early, and write it down

Money conversations feel awkward when everyone is excited. Have them anyway, before you start the trial project and again before you commit.

A few things worth agreeing on, in writing:

How equity will be split, and the reasoning behind it. Many co-founding teams split close to equally because both people will carry the company. Others weight it by who started earlier or who is putting in money. Whatever you choose, make sure you can both explain why it is fair.
Vesting. Equity that is earned over time (often four years, with nothing earned in the first year) protects both of you if one person leaves early.
Who owns the work you produce during the trial, and what happens to it if you don't go ahead.
Roles and decisions. Who has the final call on product, on technology, on hiring.

None of this needs a lawyer on day one, but it does need to be on paper. A shared document you both agree to is far better than nothing, and you can formalise it when you incorporate.

Red flags on both sides

Walk away, or slow down, if you see:

Someone who asks for money, fees or personal details before you have worked together.
Pressure to commit before a trial, or to sign something you haven't had time to read.
A founder who wants an engineer but won't share customer conversations or decisions.
An engineer who wants to rebuild everything from scratch before anyone has used the first version.
Vagueness about time. "I'll fit it in" usually means it won't happen.

Meeting in person? Start somewhere public, and see our safety tips for working with someone new.

A simple plan for the next month

Week one: write down what you bring, the role you need and what you can offer. Talk to five potential customers.
Week two: ask for introductions, go to one event, and put your profile where engineers will see it.
Week three: have first conversations with the people who are a strong fit. Pick one or two to try a small project with.
Week four: do the project. Then talk honestly about whether you want to keep going, and if you do, agree the terms in writing.

Finding a technical co-founder is less about luck than about making it easy for the right engineer to say yes. Show what you bring, be specific about what you need, and build something small together before you build something big.

If you want to start now, say what you bring and what you need on Collaborators. It's free, and you'll be shown the engineers whose needs mirror yours.