If you are a non-technical founder with a software idea, you will have been told to find a technical co-founder. It is the standard advice, given confidently, usually by people who are not offering to be one.
I have been the technical half of that arrangement several times over twenty-five years, and I have advised founders on both sides of it. The advice is not wrong, exactly. It is just far less precise than the situation requires, and following it without thinking costs founders either a great deal of equity or a great deal of time.
What the role actually is
Strip away the title and a technical co-founder does four distinct things.
They decide what to build and in what order, which is mostly a product judgement rather than an engineering one. They build it, or lead the people who do. They own the technical risk — the architecture choices, the security posture, the things that will be examined if you ever raise or sell. And they represent the technology commercially, in front of customers, partners and investors who want to know the product is in competent hands.
Those four are usually bundled together because they often sit in one person. They are not the same job, and this matters, because you may only need one or two of them right now.
Outcome: you can name which of the four you are actually short of.
The equity question, honestly
A co-founder gets a co-founder’s share. Depending on timing and contribution that is anywhere from fifteen to fifty per cent of your company, usually vesting over four years.
That is the correct price for someone who joins at the beginning, takes no salary, shares the risk and stays for years. It is a very high price for someone who builds your first version and loses interest in eighteen months, which happens more often than the ecosystem admits. The failure mode is brutal: a departed co-founder holding a large vested stake, a product only they understood, and a cap table that makes you difficult to invest in.
Before you offer equity, ask what the person is actually taking on. Are they leaving a job? Are they taking no salary? Are they committing for years, in writing, with vesting and a cliff? If the answer to those is no, you are not looking at a co-founder, you are looking at a contractor asking for a co-founder’s price.
Outcome: equity that reflects risk taken, not enthusiasm expressed.
The three situations you might be in
Most non-technical founders fall into one of three, and each has a different answer.
You have an idea and nothing else. You do not need a technical co-founder. You need customers, and finding out whether anyone wants this does not require any software at all. Bringing on a technical co-founder at this stage is asking someone to take enormous risk on an unvalidated idea, which is why the good ones say no, and why the ones who say yes are often not the ones you want. Come back to this question when you have evidence.
You have demand and need a first version built. This is the situation where the advice gets applied most often and fits worst. You have a defined, finite piece of work with a clear brief. That is a build, and you can buy a build. What you need alongside it is not a co-founder but senior judgement — someone who will tell you when a request is expensive, when the simpler option is better, and what you are storing up for later. That can be bought by the day.
You have a growing product, customers who depend on it, and technical decisions arriving faster than you can assess them. Now you need someone who owns this permanently. Whether that is a co-founder or a first senior hire depends mainly on whether you can afford a salary. If you can, hire. Equity is the most expensive currency you have and you should spend it last, not first.
Outcome: you match the solution to the stage rather than to the advice.
The failure mode nobody warns you about
The worst outcome is not failing to find a technical co-founder. It is finding the wrong one and being unable to undo it.
I have seen this several times and it looks the same each time. The founder, feeling the pressure of the standard advice, brings in the first credible technical person who says yes. There is enthusiasm and no paperwork. Six or nine months in, the relationship reveals itself — different expectations about hours, about direction, about whether this is a job or a company. By then a meaningful stake has vested, the codebase is in their account, and the conversation about unwinding it is one neither party wants.
If you take nothing else from this: vesting schedules, a cliff, and everything the company owns held in the company’s accounts. Have that conversation early, when it is easy, because it is impossible later. Anyone who is genuinely a good partner will expect it. Reluctance to sign is itself the answer.
What I would actually do
If I were starting again as a non-technical founder, I would sell before building, buy the first version rather than trading equity for it, and pay for senior technical judgement by the day while I did — someone with no stake in making the project bigger than it needs to be.
Then, once there were customers depending on the product and real decisions to make, I would look for the permanent technical partner. From that position you are choosing rather than persuading, which is a far better place to be, and the people worth having are much more interested in a business with customers than an idea with a deck.
If you need senior technical judgement without hiring for it yet, that is precisely what we do. Get in touch for a free introductory call.