Decide what kind of partner you need
A co-founder shares responsibility for building the business over time. That is different from hiring someone to deliver a fixed task, finding a mentor for advice or meeting a potential customer. Write the decision or responsibility you want to share before choosing a role label.
“I need a developer” can mean a prototype, a technical product decision or a partner who will own engineering for years. Those are different searches. If you mainly need one clearly scoped deliverable, discuss that honestly rather than promising a co-founder relationship to solve a short-term capacity problem.
“I have interviewed independent retailers about stock errors. I bring customer access and operations experience. I am looking for an engineering co-founder to test a simple inventory prototype with three shops. I can commit evenings and a Saturday for the next month.”
What should you look for in a co-founder?
Start with complementary contribution, realistic time, interest in the customer problem and a way of working you can test together. A shared job title or enthusiasm for startups is not enough. Write your requirements as observable behaviours rather than a list of impressive credentials.
| What matters | What to ask or try |
|---|---|
| Contribution | Which responsibility can each of us own? Ask for one concrete example of similar work and agree your first deliverable. |
| Customer curiosity | What have we learned from potential users, and what evidence would make us change the idea? Compare your responses to the same customer feedback. |
| Time and availability | How many hours and which working windows can we actually commit? Put a small project and check-in on the calendar before discussing full-time plans. |
| Communication | How will we share progress, flag a missed commitment and handle disagreement? Observe this during a bounded trial, not only in an interview. |
| Decisions | Who owns the next product, customer or delivery decision? Try a small decision together and explain the trade-offs each of you sees. |
| Practical expectations | Discuss location, remote work, income needs and the resources each person can realistically contribute. Do not assume another person has the same runway or obligations. |
| Trust and boundaries | Check claims with context and consent. Agree what can be shared, avoid exchanging credentials, and keep early work small enough to review before making a larger commitment. |
A technical co-founder search may focus on engineering ownership; a business co-founder search may focus on customer discovery, sales or operations. The same working questions apply to both. Use the twelve-question fit worksheet to record differences, then plan a small working trial. The aim is a reasoned next decision, not a compatibility score.
Choose your starting point
I have an idea
Bring what you have learned, the next assumption to test and evidence you are ready to do your part. Explain which decisions remain open.
I want to join a startup
Explain the problems you care about, the work you can own and the conditions under which you could commit. You can contribute without arriving with a polished idea.
I am exploring
Say that plainly. Suggest a short discovery project rather than asking someone to commit to an undefined company.
Turn a vague search into useful filters
On Aspair, create a Co-founders profile and add your LinkedIn profile link. Complete the existing fields manually: your strengths, skills, desired contribution, startup sectors, specialisms, location, stage and commitment. Use a headline that says what you bring.
Start Discover with the skill you need, then add one meaningful sector or commitment filter. Add a city only if meeting locally matters. Too many filters can hide potentially relevant people in an early community. The swipe view is another way to explore; it is not a substitute for reading a profile.
Our matching guide explains which fields support discovery and the Match signals shown in founder profiles. A shared sector starts a conversation; it does not establish trust, availability or the right working relationship.
Send an introduction someone can answer
A useful opening has three parts: one specific reason you read their profile, the contribution you need and a small next step. Avoid sending the same generic pitch to everyone.
“Your operations experience stood out. I am testing a farm logistics idea and can build the prototype. Would you be interested in a short conversation about how you would test demand?”
Aspair opens chat after a mutual connection. Another member can decline or choose not to respond. Keep confidential customer information and credentials out of your introduction.
Use a ten-day search cycle
- Days 1–2: sharpen the brief. Identify one responsibility to share and the evidence you can bring.
- Days 3–5: explore deliberately. Read relevant profiles and send a small number of personal, specific requests.
- Days 6–7: compare expectations. Discuss time, contribution, location and how you would work together.
- Days 8–10: choose a small trial. Agree an output, a check-in and a review date. Decide whether another step makes sense.
This is a planning suggestion, not a promise that a partner will appear in ten days. Use the trial-project guide to make the working test useful even if you decide not to continue.