You need someone to build the product. That does not automatically mean you need a co-founder.
A co-founder is a person with whom you will make difficult decisions when the money is tight and the original plan has become embarrassing. Coding ability is part of that assessment. It is not the entire assessment.
The short answer: define the founding responsibility you need, find candidates through relevant networks, and assess compatibility through a small, properly agreed piece of work. Look for a partner in decisions, not an unpaid substitute for a development budget.
Decide whether the gap is founding or delivery
A contractor can build a defined scope. A fractional CTO can provide technical leadership. A technical co-founder takes a continuing role in the venture’s direction, risks and responsibilities.
If you need a prototype and have not yet tested customer demand, a bounded build may answer the immediate question. If the product depends on continuous technical judgement and you want a partner shaping the business, the co-founder role may be appropriate.
Write the expected responsibilities before searching. Include product decisions, customer discovery, hiring, delivery, operations and fundraising support where relevant. Do not hide a full company-building role behind “help with the app”.
Search where relevant people can assess you too
Use trusted professional introductions, technical communities, founder networks and people whose work you can inspect. Explain the problem, evidence of demand, current stage and what you bring to the venture.
Y Combinator’s co-founder matching is one available introduction route. It is not a substitute for assessment or a guarantee of fit. The important part is the evidence you build after meeting.
Strong candidates will assess your judgement, commitment and ability to work with customers. Have something more concrete to offer than an idea and a promise that the equity will be worth a fortune.
Use a working session with a real decision
Choose a small, bounded exercise: explore the riskiest product assumption, review a proposed architecture or prototype one narrow interaction. Agree time, payment where appropriate, confidentiality and ownership before work starts.
Watch how the person asks questions, handles uncertainty and explains trade-offs. Do they seek evidence? Can they propose a simpler route? Do they change their mind when the facts change?
Avoid extracting substantial unpaid production work under the label of an interview. The exercise should be fair and proportionate, and both parties should know what it is for.
Assess more than technical fluency
| Dimension | What to observe |
|---|---|
| Problem understanding | Connects technical choices to customer needs |
| Judgement | Explains trade-offs without pretending certainty |
| Delivery | Completes a bounded commitment and exposes blockers |
| Communication | Makes decisions understandable to non-specialists |
| Collaboration | Handles disagreement without contempt or avoidance |
| Commitment | Has a realistic plan for time, income and competing obligations |
| Ownership | Willing to clarify responsibilities and difficult scenarios |
Discuss the awkward subjects early
Talk about time commitment, cash needs, decision rights, roles, equity expectations, vesting, IP and what happens if one person leaves. Have the legal arrangements prepared for the actual jurisdictions and circumstances involved.
For a UK–Dubai founding team, location affects working overlap, travel and the practical arrangement. It does not remove the need to resolve entity, employment, tax and ownership questions with appropriate advisers.
Do not settle the relationship solely through a percentage discussion. Two people can agree an equity split while holding incompatible expectations about who makes product decisions or how quickly revenue must arrive.
Make the decision gradually, but explicitly
Use a sequence of conversations and bounded collaboration. Ask for relevant references and inspect work with permission. Record what remains uncertain and what evidence would resolve it.
A trial period should have a clear purpose and endpoint. Endless ambiguity can be as damaging as a rushed commitment, especially if one person believes they are already a founder and the other thinks they are still interviewing.
Choose someone you can disagree with productively. The architecture will change. The ability to make sensible decisions together will be needed for rather longer.
Sources and scope
Reviewed 1 November 2026. The examples and worksheets are my suggested working methods, not measured client results or official standards.
