Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

I cannot find a technical cofounder and my product needs one

Short answer

A technical cofounder does three jobs: decides what to build and how, builds it, and is accountable for it working. You can split those. A part-time senior engineer can make the technical decisions and be accountable, while developers or the same engineer build. Pay for the role instead of giving equity, and keep ownership of the code.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • I have an idea or a customer but no one to build and own the technology.
  • Every possible cofounder wants equity I am not ready to give.
  • I hired freelancers and nobody is making the technical decisions.
  • I cannot tell whether what I am being told is good advice or not.
  • I am afraid to hand my product to a stranger.

Why does this happen?

  1. The role is bigger than writing code

    A cofounder is expected to choose the technology, hire, set priorities and answer for outages. Few people want all of that for an early company.

  2. Good engineers have other options

    Skilled people are in demand and look for secure work or a large share of a company that is already moving.

  3. Founders confuse the job with the title

    Many companies only need technical direction and accountability for a period, not a lifelong partner in the company.

  4. Freelancers build what they are told

    A freelance developer is good at a defined task. Without a technical lead, nobody tells you whether the task is the right one.

What can I do about it today?

  1. Write what you need in three linesWhat the product must do in the next few months, who will use it, and what must not go wrong. This is the brief any technical person will ask for.
  2. Separate the three jobsDecisions, building and accountability. Decide which you need first. Many early products only need the first and third part time.
  3. Keep ownership clear from day oneThe code, the cloud and store accounts and the domain should belong to your company. That keeps every later option open, equity or not.
  4. Do not give equity to the first person who offersA large share given in a hurry is hard to undo. If someone is a real partner, agree a vesting period and put it in writing with a lawyer.
  5. Start small and test the working relationshipA short paid engagement with a clear outcome shows quickly how someone works and communicates.

When should I bring someone in?

  • You are about to hire or sign a developer and cannot judge the plan or the quote.
  • An existing product has no technical owner.
  • An investor or partner has asked who is responsible for the technology.

How do I handle it?

  1. Start with your goals, not a stackI ask what the product has to prove first and choose the simplest technology that gets there and that a later hire can maintain.
  2. Lead part time on a written scopeI plan the work in short sprints, review the code and answer technical questions. I can also build when it is the quickest way.
  3. Keep everything in your nameCode, accounts and servers sit with your company from the start, with notes so another engineer can take over.
  4. Help you hire when you are readyWhen the product justifies a full-time person, I help you describe the role and judge candidates, and I hand over cleanly.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Is this the same as hiring a CTO?

It covers part of what a CTO does, on a part-time basis. You get technical direction and accountability without a full-time salary or an equity stake.

Do I still need a cofounder later?

Perhaps, and perhaps not. If you meet someone who is a real partner, nothing here blocks it. The point is that your product does not wait for that.

Do you take equity?

I work as a paid engineer or lead on a written scope. If you ever want to talk about something else, that would be a separate conversation.

How was this page made?

I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.