← All writing

How to find a tech cofounder through your existing network

Learn how to find a tech cofounder through your network, with an intro template, a practical trial and clear ownership checks.

Two adults discuss technical ownership beside a simple office table with notebooks and blank pages.

You want to find a tech cofounder because nobody owns the technical side of your SaaS. Maybe a contractor built the product, a developer left or you are a technical founder stretched across shipping, sales and fundraising. Your existing network gives you a place to start, provided you can explain the partnership you actually need.

Decide whether you need a partner or technical ownership

A cofounder takes responsibility for the company beyond the next release. That includes uncomfortable decisions about the roadmap, spending, customer commitments and whether the product should change direction. They will reasonably expect authority over decisions they are responsible for.

Write down what you want to stop carrying yourself. Is it choosing what to ship, reviewing a contractor’s work, handling incidents or deciding whether the codebase can support the next product change? Those are different responsibilities. “Someone technical” leaves all of them unresolved.

Some of that work may belong with a first engineer or an accountable outside engineer rather than a cofounder. Agentic engineering gives another way to organize delivery: one accountable engineer directs coding, test, security and documentation agents and reviews their output. Agents do the work. You make the decisions.

That arrangement still needs technical judgment, clear acceptance criteria and someone responsible when something breaks. A coding agent alone does not fill the ownership gap.

Before you try to find a tech cofounder, decide whether you want someone to share company-level decisions or someone to own delivery against priorities you set. Your introduction request should reflect that choice.

Write a role that your contacts can forward

Prepare a short note that explains the product, what exists today and what responsibility you want to share. Include evidence you actually have, such as a working product, customer conversations or current usage. Label a scoped v1 as a plan, not a shipped product.

Adapt this template:

I’m developing [product] for [specific users]. Today we have [what exists and evidence of demand]. I’m looking for a technical cofounder to own [responsibilities], while I own [responsibilities]. The current product uses [known stack or builder], with [known limitations or unknowns]. I’m looking for [location or working-overlap needs], with [current commitment and transition expectations]. Are you comfortable asking someone you’ve worked with whether they would welcome an introduction?

Keep confidential customer details and credentials out of anything that might be forwarded.

If a developer’s departure triggered the search, establish company ownership after the handoff before presenting the product to candidates. Be candid about what you control and what remains unverified.

Ask your network to help you find a tech cofounder

Start with people who have seen you work. They can explain how you handle disagreement, follow through and make decisions. That context gives a potential partner more to assess than a product description alone.

Build a small map of existing relationships rather than sending the same message to every contact.

Person you already knowConnection worth asking about
A former colleagueSomeone whose technical judgment they have worked with directly
A founder peerAn engineer they would choose to work with again
A trusted contractorSomeone who has owned a product beyond an individual assignment
An adviser or investor you already knowSomeone whose interests and current plans fit your stage

Ask for a specific introduction, not access to someone’s entire network. “Who have you worked with who might want responsibility for an early-stage SaaS?” gives your contact a clearer search than “Do you know any developers?”

Use a double opt-in introduction: your contact checks whether the other person wants to connect before sharing contact details. Send the forwardable note so they do not have to write your pitch.

A declined introduction is useful information. Ask whether the mismatch was the role, the product stage or the person’s current commitments. Do not ask your contact to keep persuading someone who has declined.

Evaluate ownership through specific work

A warm introduction can help you find a tech cofounder, but it does not establish that you can run a company together. Your connector may know someone as a colleague without knowing how they handle an ambiguous roadmap or a failing release.

Ask about a product they owned. What decisions were theirs? What did they choose not to develop? What broke after release, and what changed afterward? Look for a clear account of trade-offs and responsibility, including mistakes.

Then discuss your product. Give them enough context to explain what they would investigate first. Someone who immediately promises a rewrite without understanding the product, users or constraints has not yet given you a usable recommendation.

For a non-engineer founder, an independent engineer can help review a candidate’s technical reasoning. Keep that review bounded and relevant to the work ahead. For a technical founder, focus on whether the person can take ownership without needing you to supervise every decision.

Request references with the candidate’s permission. Speak with someone who saw them ship and maintain a product. Ask how they communicated bad news, handled disagreements and left work for others to maintain.

Evaluate yourself in the same conversation. A candidate needs to know whether you can set priorities, explain customer needs and accept technical constraints without changing the agreement after work begins.

Use a bounded collaboration before discussing a permanent commitment

You can find a tech cofounder whose background looks right and still disagree about what should ship. A small working trial gives both people something concrete to assess before sharing long-term ownership.

Choose a real, limited deliverable. For an existing product, that might be improving one user flow or investigating a recurring failure. For a scoped v1, it could be a narrow prototype that tests a disputed product assumption. Label a prototype clearly so nobody mistakes it for a production release.

Write down what completion means before work starts. Include the expected behavior, failure cases, evidence of testing and the explanation you need to accept the result. Agree on compensation, confidentiality and ownership before anyone contributes work to the company.

Use a company-controlled repository and a test environment. Limit access to what the trial requires. If the change calls a model or another paid API, include usage and cost telemetry so you can see what a completed action consumes.

At the review, discuss the work and the process. Did they raise uncertainty early? Did you provide decisions when needed? Could another engineer understand what changed? Were disagreements resolved or merely postponed?

Accepting a deliverable is separate from agreeing to become cofounders. Leave room for either person to conclude that the collaboration was useful but the partnership is wrong.

Three blank cards on a table show a simple trial flow for a tech cofounder discussion.

Discuss commitments and working boundaries directly

Talk about current obligations, the conditions for joining and what each person can reliably own. Do not interpret enthusiasm as an agreed commitment. Someone may like your product and still be unable to take responsibility for it.

Discuss ordinary working situations: an urgent customer issue, a missed deliverable, a disagreement about spending or one person being unavailable. Agree on how you will communicate and which decisions can proceed without both people present.

Keep the conversation about work commitments rather than asking for private explanations. You need to understand what someone can take on, not inspect their personal life.

Pay attention to your own wellbeing during the search, too. If stress is affecting you, free physical and mental health screening quizzes offer indicative results that may help you decide whether to seek professional advice. They are not diagnoses and should never become part of candidate evaluation.

The aim is to find a tech cofounder whose commitments fit yours, with enough candor to discuss changes before they become missed promises. A working agreement needs room for both people to raise a problem.

Resolve equity, authority and intellectual property together

Discuss equity alongside responsibility, current contribution, cash needs and the risk each person is taking. A title alone does not answer any of those questions. Neither does a general claim that one person brings the idea and the other brings the code.

Explain what the company already owns. If contractors developed the product, establish what their agreements say about intellectual property. Identify third-party code, licenses and any restrictions that need review. A new partner should understand what they are joining before agreeing to ownership terms.

Have qualified legal counsel document the arrangement for your jurisdiction. That includes equity issuance, vesting, intellectual property assignment, departure provisions and how disagreements or deadlocks will be handled. Get advice before signing or issuing equity.

Authority deserves its own conversation. Who decides the product roadmap? Who controls technical spending? What requires joint approval? If you expect final say on every consequential decision, disclose that expectation rather than leaving it inside the word “cofounder.”

These conversations can expose a mismatch even after a good trial. It is better to address it now than to find a tech cofounder and discover later that you meant different things by shared ownership.

Keep the search moving without putting the roadmap on hold

Maintain a private record of introductions, conversations, open questions and the next agreed action. Record facts rather than labels such as “great engineer” or “bad fit.” “Cannot join under the current commitment” is more useful and fairer than a vague judgment.

Close the loop with people who introduce you. Thank them and explain whether the connection was relevant without sharing private reference comments or negotiation details. A short update helps them understand what another useful introduction would look like.

Keep shipping something small while the search continues. A clearer product, a resolved technical unknown or a documented customer problem gives the next candidate better evidence to assess. Avoid postponing every technical decision until a future partner arrives.

If nobody suitable emerges, revisit the role. You may need a narrower first hire, outside delivery ownership or more evidence of demand before someone wants to share responsibility for the company.

Frequently asked questions

Can I find a tech cofounder without knowing how to code? Yes. You can evaluate communication, judgment and follow-through through specific work and references. Use an independent engineer to help assess technical reasoning, and define product acceptance in terms you can verify.

Who should I ask first in my existing network? Start with former colleagues and founder peers who know how you work. Ask for someone they have worked with directly and would trust with product ownership. Their firsthand context matters more than the size of their contact list.

How much equity should a technical cofounder receive? There is no percentage that answers every situation. Discuss responsibility, contribution, commitment and risk together, then have counsel document equity, vesting and departure terms. Avoid making an ownership promise just to secure an introduction or begin a trial.

Should I use a development company while I search? That can be an option if responsibility and ownership are clear. Before choosing a SaaS development company ahead of your first hire, establish who makes technical decisions, how you accept work and how another engineer could take over.

This week, define the role and send a specific request

Write the forwardable note, identify a small set of contacts who know your work and ask for double opt-in introductions. Prepare the same product context for every candidate so you can compare their reasoning against the same facts.

Choose a bounded trial you could offer if a conversation progresses. Define the deliverable, acceptance evidence and ownership terms before asking anyone to begin. You can keep working to find a tech cofounder while resolving a technical unknown or shipping a smaller product change.

Archer Scaling AI helps early-stage SaaS become AI-native. It builds and runs the systems that develop, market and sell the SaaS so the founder’s time goes to the decisions. If you are deciding what technical ownership should look like in your company, book a free intro call about your company.