How do I start a tech startup without a technical co-founder?
By Bonaventure Ogeto, Founder and CEO, Mctaba Labs
Published
You do not need a technical co-founder to start. First prove customers want the product, then take the cheapest route to a first version: run it by hand, use no-code or AI tools, or pay a builder for a small scope. Keep accounts and code in your name or your company's, never the builder's. Seek a technical partner later.
A common way for an idea to die in Nairobi goes like this. Someone who knows an industry well, a pharmacist, a logistics clerk, a teacher, sees a problem that software could solve. They are told that a tech startup needs a technical co-founder. They spend a year at meetups asking developers to join them for equity. The developers, who have heard the pitch before, say no politely. The idea stays in a notebook.
The advice was wrong for the stage. A technical co-founder is valuable. Waiting for one before you begin is not. Almost everything that decides whether an early startup lives can be done by a person who has never written a line of code, and some of it can only be done by you.
Do I really need a technical co-founder?
Not to start. Possibly later, and by then you will be able to attract a good one.
Think about what the first months of a startup consist of. Finding out whether the problem is real. Finding the people who have it. Learning what they pay today and what they would pay you. Delivering the result to the first few, by whatever means. Collecting money. None of that is engineering.
A technical co-founder matters most when the technology itself is the hard part: a new kind of payment infrastructure, a product whose advantage is a clever algorithm, hardware. For the far more common case, a business that uses ordinary software to serve a market you understand, the hard part is the market. That is your side of the table.
There is also a practical reason to wait. Before you have customers, you are asking a skilled person to work unpaid on your guess. After you have customers, you are offering a share in something that is working. The second conversation goes very differently.
What is my job if I cannot write code?
More than half the company. Write this list down and notice that nobody can do it for you.
- Know the customer better than anyone. Their day, their workaround, what they pay and who decides.
- Sell. The first ten customers come from you, in person and on WhatsApp.
- Decide what gets built. One clear page describing what a user can do is the most valuable document in an early startup, and it contains no code.
- Run the service by hand until software is worth paying for.
- Handle the money. Pricing, M-Pesa collection, records, the business registration and tax side.
- Test like a customer. On a cheap phone, on mobile data, with real money.
- Keep the keys. Every account in your name or your company's, never the builder's.
A founder who does those seven things well is not "the non-technical one". They are the one who knows what the product is for.
What are my routes to a first product?
There are five. Move down this table one row at a time and stop at the first row that works.
| Route | Suits you when | What you give up |
|---|---|---|
| Run it by hand: WhatsApp, a spreadsheet, M-Pesa | You are still proving people will pay. Nearly always the right first step | It does not scale, which is fine at ten customers |
| Build it yourself with no-code tools | The product is forms, lists, bookings or a simple marketplace | You will meet the tool's limits, especially on payments and data |
| Build it yourself with AI tools | You are patient, the product has one flow, and you will test carefully | You cannot verify security or payment handling alone |
| Pay a freelancer or a small team for a tight scope | You have paying customers or strong proof, and savings set aside for it | Cash, and you depend on them for changes |
| Bring in a technical co-founder | The technology is the hard part, or the product is growing and needs someone full-time | A large share of the company, for good |
Two warnings about the table.
The fourth row is where a non-technical founder can lose the most money, usually by commissioning too much, too early, from someone they could not assess. Keep the scope to one flow, pay against milestones you can test on your own phone, and get advice first. Before the first payment, register a limited company if you can, so that the code and any equity sit in it. If you want to see what a small, well-scoped first build looks like, the page on MVPs for founders describes one approach.
The fifth row is the only one you cannot undo. You can cancel a tool, end a contract or rebuild an app. A co-founder with shares is with you for the life of the company.
How do I stay in control of a product I cannot read?
By owning everything that can be owned and insisting on seeing everything that can be seen. Use this checklist with any builder, whether a freelancer, a team or a friend doing you a favour.
Accounts in the company's name if it exists, otherwise in yours, with the builder added as a collaborator
- Domain name
- Hosting
- The code repository, for example on GitHub
- Payment provider, Till or Paybill
- SMS or WhatsApp messaging account
- App store developer accounts, if any
Anything opened in your own name moves to the company when it is formed.
In writing before work begins
- What will be built, as a list of things a user can do
- Milestones, dates and what you pay at each
- That the code and designs belong to your company once each milestone is paid. If the company is not registered yet, you sign in your own name, with a clause assigning everything to the company once it exists
- That the builder will hand over a short document: how to run it, where everything lives, every password changed to yours
Every week
- A working link you can open on your own phone
- A plain answer to: what is done, what is next, what is waiting on me
Before launch
- An independent developer reads the code for an hour or two and tells you what they see
If a builder resists any of the first group, find another builder. People who do good work have no reason to hold your accounts.
How do I get technical advice without a co-founder?
Ask for a small, specific favour from someone experienced, and pay for their time if they do not know you. An hour of a senior developer's opinion before you sign is the best money a non-technical founder spends.
Find them through people you already know: a former colleague, a cousin's workmate, your university's alumni WhatsApp group, a developer community meetup. Then send something like this:
Hi Halima, Kiprono from our old office suggested I ask you. I run a small service that helps pharmacies reorder stock, by hand for now, with twelve paying customers. I am about to pay a developer to build a first version and I am not technical. Could I pay you for one hour this week to look at my one-page scope and the quote I have received, and tell me what you would question? I am not looking for someone to build it.
Three things make that message work. It shows you have customers, so you are not another idea person. It asks for one bounded hour. And it says clearly that you are not fishing for free labour or a co-founder.
Bring the same three questions to the call: what is missing from this scope, what on this quote looks wrong, and what would you ask this builder before paying? Keep that person as an occasional reviewer. An adviser who looks at your product once a month gives you much of what a technical co-founder would at this stage, without the shares.
When is a technical co-founder worth it, and how do I avoid a bad deal?
When the product is working and has become the constraint: customers are paying, changes are needed every week, and waiting on an outside builder is costing you sales. At that point you need someone who wakes up thinking about the technology.
The best candidates are often already near you. The freelancer who built the first version well. The adviser who kept showing up. Work with someone on something real and paid before you discuss shares, because a few weeks of work tells you more than any number of coffees.
When you do agree terms, be careful with equity. In The Founder's Dilemmas, Noam Wasserman describes how splits made quickly and early, before anyone knows who will contribute what, are a frequent source of later conflict. Two protections are standard. Vesting means shares are earned over a period of years of continued work, so a partner who leaves after three months does not keep a full stake. A written founders' agreement records roles, time commitment and what happens if someone leaves. Have a lawyer prepare both. The fee is small beside the cost of a dispute over a company that has started to matter.
And never offer equity as a way to get a build cheaply. If what you need is an app, buy an app. Shares are for a partner.
What should I do this month?
- Talk to fifteen people who have the problem, and write down what they do about it today.
- Sell the result to five of them and deliver it by hand, taking payment on M-Pesa.
- Write the one-page scope from what those five asked for.
- Try building it yourself with a no-code or AI tool for two weekends. Even if you stop, you will brief a developer better.
- Find one experienced developer willing to review your scope for an hour.
- Only then decide between carrying on by hand, your own build, a paid build or a partner.
By the end of that list you will have customers, revenue, a scope and an adviser. That is also what makes a good technical partner want to join.
Key takeaways
- The early work of a startup is finding customers, which needs no code.
- Pick a route to the first version by what the product does, not by what feels most serious.
- Whoever builds it, the domain, hosting, payment accounts and code go in your company's name if it exists, otherwise in yours, and never in the builder's.
- Ask for a working demo every week so you can judge progress without reading code.
- Get an experienced developer to advise you for an hour before you sign or pay for a build.
- Offer equity only to someone you want beside you for years, and only with vesting.
Frequently asked questions
- Do investors fund startups without a technical co-founder?
- Some do and some will not, and it depends heavily on what you have shown. A non-technical founder with paying customers and a working product, however it was built, is in a stronger position than a complete team with neither. Expect to be asked who will own the technology as you grow.
- Should I learn to code before I start?
- No. Learning enough to build a product well takes time you should be spending with customers. Learn enough to follow a technical conversation and to read what an AI tool or a developer produced. That can happen alongside the business, not before it.
- Can I hire a developer as an employee instead of finding a co-founder?
- Yes, once the product earns enough or you have raised money to pay a salary reliably. Before that, a full-time hire is a monthly cost with no certain work to fill it. A small paid build or a part-time arrangement fits the early stage better.
- What is a CTO, and do I need one at the start?
- A chief technology officer is the person responsible for a company's technology decisions and team. At the start there is no team to lead and few decisions to make, so the title is not needed. What you need is a product that works and someone trustworthy to ask.
- How do I know whether a developer is any good if I cannot judge code?
- Judge what you can see. Ask for two live products they built and use them. Speak to those clients. Give a small paid task first and watch whether it arrives on time, works on your phone and comes with a clear explanation. Then ask your adviser to look at the code.
Sources
- The Founder's Dilemmas: Anticipating and Avoiding the Pitfalls That Can Sink a Startup, Noam Wasserman (book, 2012). Checked on 19 November 2026.
- The Lean Startup: How Today's Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses, Eric Ries (book, 2011). Checked on 19 November 2026.
- 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.
