How do I find a technical co-founder in Kenya?

By Bonaventure Ogeto, Founder and CEO, Mctaba Labs
Published

The short answer

Look where technical people already spend their time: former colleagues, university tech clubs, developer meetups, hackathons and open-source projects. Arrive with proof that customers want the product, not only an idea. Then run a paid trial project of two to four weeks before you discuss equity, and put any shares on a vesting schedule.

A good software engineer in Nairobi hears the same pitch several times a year. "I have an idea. I just need someone to build it. I can offer you 10%." The engineer is polite, says it sounds interesting, and never replies to the follow-up message.

The pitch fails because of what it asks. The engineer is being invited to give up paid evenings, for months, on the strength of something the founder has not yet tested. From their side of the table, the idea is the cheap part and the build is the expensive part.

So the search for a technical co-founder is less about where to look and more about what you are holding when you get there. This guide covers both, then shows you how to test the partnership before any shares change hands.

What do I need before I go looking?

You need evidence that the business is real without them. Strong engineers have options. They pick the founder who has reduced the risk.

Three things change the conversation:

  • Customers. Ten people who have paid a deposit on M-Pesa, or a business that has signed a letter saying it will pilot the product. This is the strongest thing you can bring.
  • A manual version. If you are already delivering the service by hand, with phone calls and a paper order book, you can show exactly what the software must replace.
  • Your own unfair share of the work. Industry contacts, a distribution channel, a licence, years inside the sector. Something the engineer could not get by going alone.

If you have none of these, pause the search and get them. It is a few weeks of work and it will do more for you than fifty coffees.

Where are technical people in Kenya?

They are in five kinds of places. Work through them in this order, because trust falls as you go down the list.

1. People who have worked with you. Former colleagues, classmates, the engineer at your current employer who always ships on time. They already know whether you keep your word. This is the safest place to begin.

2. One introduction away. Ask every engineer you know one question: "Who is the best builder you have worked with who is restless?" A warm introduction from another engineer carries weight that a cold message never will.

3. University tech clubs. Many university computing departments have a student developer club, and some run project showcases at the end of a semester. Final year students and recent graduates have time, energy and a need for real projects. They have less experience, so the trial project below matters even more.

4. Developer meetups and hackathons. The larger towns have developer gatherings built around a programming language, a cloud platform or a weekend build challenge. Search for the ones near you. Go to listen. Watch who finishes what they demo and who helps others. Hackathons are especially useful because you see people work under pressure.

5. Open-source and online developer communities. Engineers who contribute to public projects leave a visible record: you can see their code, how they respond to criticism, and whether they finish. Kenyan developer groups on WhatsApp, Telegram and Discord are active, but read for a while before you post. A "looking for a CTO" message dropped into a group on day one is ignored.

Wherever you meet people, do not pitch on the first meeting. Ask what they are building and what they would build if money were not the issue. You are looking for someone who cares about your problem, and you cannot hear that while you are talking.

What should I say when I approach someone?

Lead with the evidence and ask for something small. Here is a message that works:

Hi Nekesa, Mutua suggested I talk to you. I run deliveries for 14 agrovets around Kisumu using WhatsApp and a spreadsheet, and they pay me every week on M-Pesa. I have reached the limit of what I can do by hand. I am not asking you to build anything yet. Could I show you how it works for 30 minutes and get your view on what the first version should be?

It names real customers, shows you have done the work, and asks for advice instead of a commitment. Engineers like being asked how they would solve a problem. Some will say "I would love to build that", and that sentence is where a co-founder conversation begins.

How do I test working together before splitting equity?

Run a paid trial project. Two to four weeks, a small piece of the real product, a fixed fee, and a written one-page brief. You pay because paid work is taken seriously and because it leaves no confusion about who owns the result.

Use this template:

Item What to write
The outcome One working thing a customer can use. For example: "A shop owner can place an order from a link and I see it on a list."
Time Two to four weeks, with a fixed end date
Fee A fixed amount you both agree is fair for part-time work. Say, KES 30,000 for the whole project
Check-ins Two short calls a week, on fixed days
Ownership You own the code and the accounts, whatever happens next
The demo On the last day, they show it working to a real customer with you present
What happens next A conversation, with no promise from either side

The software is the least important thing you get from the trial. Watch for these instead:

  • Did they ask about the customer, or only about the features?
  • When something was unclear, did they ask you or guess?
  • When they were going to be late, did you hear it from them first?
  • Did they push back on your ideas with reasons?
  • After a hard conversation, did the work continue?
  • Did you look forward to the calls?

If the answers are mostly yes, you have found something rare. If the trial was painful, you have lost a few weeks and a modest fee, which is the cheapest way this story can end.

What should I offer a technical co-founder?

Offer ownership that is earned over time, a clear role, and honesty about money.

Vesting. Shares should vest, meaning they are earned month by month. A common pattern is four years with a one year cliff: nothing is earned in the first year, a quarter is earned on the first anniversary, and the remainder is earned monthly after that. If someone leaves after five months, they leave with nothing and the company is not stuck with an absent owner. This only works if the agreement says how unvested shares come back to the company, because shares already issued stay with their holder unless the paperwork says otherwise. Have an advocate draft that part. Vesting should apply to you as well.

A split you can explain. Equal splits are simple and feel fair on day one. They are harder to defend when one person has worked on the business for a year and the other joined last month. Talk through who has put in what, who is going full time and when, and who is giving up a salary. Agree a number you could both explain to a stranger without embarrassment.

Decision rights. Write down who has the final say on product, on technology, on money and on hiring. Two founders with a veto on everything will stall.

Pay. If you can afford a small stipend, say so. If you cannot, say that too, and agree what revenue or funding triggers salaries. Surprises about money end more partnerships than disagreements about code.

Put all of it in a founders' agreement before the real work begins, and have an advocate look at it. A few pages now is far cheaper than a dispute later.

What are the warning signs?

Stop and reconsider if you see any of these.

  • Shares before work. They want equity agreed before they have built anything with you.
  • No vesting. They refuse a vesting schedule or call it a sign of mistrust.
  • Hidden code. The code lives in their personal account and you cannot see it.
  • Rebuilds without reasons. They want to throw away what exists and begin again, and cannot explain why in plain language.
  • Technology first. They are excited about the tools and bored by the customer.
  • Silence. They go quiet for days when work is late.
  • Too many projects. They are a "co-founder" in three other ventures.

One sign is a conversation. Two or more is an answer.

What if I cannot find one?

Then do not wait. Three months is a reasonable limit for an active search. After that, the delay costs more than the alternative.

The alternative is to pay for a small first version, keep full ownership of the code, and put it in front of customers. A live product with paying users is the best recruiting tool a non-technical founder can have. The engineer who was polite last year will look at revenue and real usage very differently, and you will be offering a seat in a moving vehicle instead of a drawing of one.

Key takeaways

  • Bring evidence, not an idea. Paying customers or deposits are what make a good engineer listen.
  • Start with people who have seen you work, then widen to clubs, meetups, hackathons and open-source communities.
  • Run a paid trial project of two to four weeks before any talk of shares.
  • Offer equity that vests over years, with a one year cliff, written down and signed.
  • Walk away from anyone who wants shares before doing any work, or who will not show you the code.
  • If the search takes longer than three months, pay for a first version and keep looking with a live product in hand.

Frequently asked questions

Do I need a technical co-founder at all?
Not always. If the technology is ordinary, such as bookings, payments and a dashboard, you can pay for a first version and hire later. You need a technical co-founder when the technology itself is the hard part of the business, or when the product will need daily engineering decisions for years.
How much equity should a technical co-founder get?
There is no standard figure. It depends on when they join, what they give up, and how much of the risk is already gone. Someone who joins before any customers and works unpaid carries far more risk than someone who joins a product with revenue. Whatever the number, make it vest over time.
Can a developer who is still employed be my co-founder?
Yes, and many begin that way. Agree in writing how many hours a week they will give, what must be true for them to go full time, and check that their employment contract does not give their employer rights over work done outside office hours.
What is the difference between a CTO and a technical co-founder?
A co-founder is an owner who shares the risk from the early days and is usually paid mostly in shares. A CTO is a role. You can hire a CTO later on a salary with a small share grant. Early on, the title matters far less than who owns what and who decides what.
Should I learn to code instead?
Learn enough to follow a conversation and read a simple project plan. That takes weeks and makes you a better partner. Learning to build a production system alone takes far longer, and during those months nobody is selling.

Sources

  1. The Founder's Dilemmas: Anticipating and Avoiding the Pitfalls That Can Sink a Startup, Noam Wasserman (book, 2012). Checked on 19 November 2026.
  2. The Mom Test: How to Talk to Customers and Learn If Your Business Is a Good Idea When Everyone Is Lying to You, Rob Fitzpatrick (book, 2013). Checked on 19 November 2026.