Co-founder guide

How to Find a Co-Founder in Europe Without Getting Stuck in Perpetual Coffee Chats

Use this to find stronger matches and avoid splitting equity with someone who only sounds good in theory.

Europe-wide guide•9 min read

A practical guide to finding, testing, and formalizing a co-founder relationship in European startup hubs without mistaking chemistry for company-building fit.

Best if you are actively matching, testing, or sanity-checking a founder partnership

Action checkpoints

Start with these sections when you want the practical moves before reading the full guide.

Make the right person self-selectWrite the ask like a working briefName the problem, customer, and wedge in plain language.Do work before romanceRun a 14-day trial sprintPick one real customer problem and one measurable output: prototype, user calls, landing page, demo, or technical spike.Use the same ruler twiceScore the trial, not the charismaSpeed: did they move the work forward without needing constant prompting?A good sprint earns a more realistic oneExtend the test before you formalizeStay close to real users or customers and create a demand signal that goes beyond a polished demo.

Repeat contact beats perfect matching

The real advantage Europe has

Europe is underrated for co-founder search because many of the best cities are compact. You can run into the same people across a hacker house, a university lab, a niche meetup, a coworking space, and a weekend event. That repeated overlap is useful. It lets you watch how people think, build, recover, and behave when nobody is pitching.

You are not looking for the most impressive profile. You are looking for someone you can trust in motion.

Context beats random matching

Where to look if you are serious

The best places are the ones where you can observe work, not just biography. Programs like Entrepreneur First and Antler create founder-matching pressure on purpose. Hacker houses, technical communities, university labs, and repeat meetups create it more organically. Online matching can work too, but only if it turns into a real trial quickly.

Look in programs that force people to build, not just describe themselves.
Look in technical communities where people ship and help publicly.
Look in repeat rooms: coworking hubs, hacker houses, demo nights, lab communities, small meetups.
If you post online, name the problem, the stage, and the gap you want to close.

Make the right person self-select

Write the ask like a working brief

A vague co-founder post attracts vague coffee chats. A useful ask gives the right person enough signal to opt in and the wrong person enough clarity to opt out. Write it like the first version of a working agreement, not like a personal brand announcement.

01Name the problem, customer, and wedge in plain language.
02Say what already exists: research, prototype, users, revenue, funding, domain access, or nothing yet.
03Name the missing owner clearly: technical, product, sales, design, operations, science, or category expertise.
04State the next short test you want to run together, with a deadline and a visible output.
05Be honest about geography, time commitment, cash runway, and whether relocation is on the table.

Do work before romance

Run a 14-day trial sprint

A good co-founder trial is not 'let's vibe for two weeks.' It has a scope, a calendar, and a definition of done. You want enough pressure to see speed, taste, conflict, ownership, and follow-through.

Before you begin, agree what happens to the work if you stop. Write down who owns any pre-existing IP, who can use the prototype, code, research, accounts, and data created during the trial, and what each person must return or delete.

01Pick one real customer problem and one measurable output: prototype, user calls, landing page, demo, or technical spike.
02Work side by side for at least one long block, not only asynchronous messages.
03Decide who owns product, customers, engineering, design, or operations during the test.
04End with a review: what worked, what felt hard, what each person avoided, and whether energy went up or down.
05Do not finalize equity based on chemistry alone. Discuss expectations early, then make the final decision after you have worked together.

Use the same ruler twice

Score the trial, not the charisma

At the end of a trial sprint, write the scorecard before the post-call glow or disappointment rewrites your memory. You are looking for evidence of how the person works, not whether the conversation felt exciting.

01Speed: did they move the work forward without needing constant prompting?
02Ownership: did they take responsibility for an outcome, not just a task?
03Truthfulness: did they say what was uncertain, broken, boring, or risky?
04Conflict: did disagreement make the work clearer or just more careful?
05Taste: did their decisions make the product, customer insight, or technical path sharper?
06Energy: after two weeks, did you want to build the next sprint with them?

A good sprint earns a more realistic one

Extend the test before you formalize

A strong short sprint earns a more realistic test. Before titles, incorporation, or a final equity split, spend another two to four weeks on work that looks more like the company you may actually build.

01Stay close to real users or customers and create a demand signal that goes beyond a polished demo.
02Watch what happens after the exciting first burst, especially when work is repetitive, uncertain, or unassigned.
03Make at least one difficult decision together and see whether you can resolve the disagreement without losing momentum.
04Speak with former collaborators about follow-through, conflict, and how each person behaves when a project becomes difficult.
05End on a set date with a clear continue, extend, redefine, or stop decision.

Alignment is specific

Questions before equity

Chemistry is helpful. It is not enough. You need alignment on pace, ambition, money, conflict, geography, and what kind of company you are actually trying to build.

01Intensity: are you both building a company, not a side project with startup language?
02Risk: how long can each person work before salary, and what personal constraints matter?
03Decision style: who decides when you disagree and the answer is not obvious?
04Geography: are you actually willing to co-locate or travel enough for early-stage speed?
05Outcome: are you aligned on venture-scale ambition, bootstrapping, acquisition, or something else?

Trust is not a substitute for paper

Get the legal basics right early

Once the match is real, write the boring stuff down. Founder agreements, vesting, IP assignment, role expectations, decision rights, leaver terms, and incorporation are not signs of distrust. They protect the relationship from preventable ambiguity.

The correct documents and mechanisms depend on where the company is incorporated. A template or legal tool built for one jurisdiction may not work in another, so use startup counsel or tooling that explicitly supports the law governing your company.

Choose the incorporation jurisdiction before copying a founder template.
Confirm how founder vesting, leaver terms, and IP assignment work under that jurisdiction.
Make sure the company receives the IP it needs, including any trial work the founders agreed to contribute.
Document who owns which decisions before stress decides for you.
Keep the cap table and founder commitments clear before you raise.
Do not invent legal documents in a chat thread. Use qualified local counsel or jurisdiction-aware startup tooling.

Early weirdness scales

Red flags worth believing

Most bad co-founder outcomes were visible early. People explained them away because the upside was exciting. Do not do that. Early weirdness becomes expensive weirdness once equity, customers, and investors are involved.

They love strategy conversations and avoid shipping.
They want founder status without founder risk.
They dodge money, roles, ownership, or conflict conversations.
They blame every previous collaborator.
You keep writing private excuses for public patterns.