From first match to Y-tunnus: what the path to co-founding actually looks like

The gap between a first interesting match on a cofounder platform and a registered company is longer than most founders expect, shorter than it should be if it's going well, and full of specific decision moments that either accelerate the path or quietly end it. Nobody warns you about the shape of this journey before you start. Everybody who has been through it remembers the stages clearly afterwards.

This piece is a realistic walkthrough of what that path actually looks like, written from enough of our own and our users' experience to be useful rather than generic. The destination is a Y-tunnus, the Finnish business ID, which is the concrete moment a founding team becomes a company. Everything between the first match and that registration is where companies either form or fail to.

Week zero: the first surfaced match

You sign up. You connect your sources. The platform generates a fingerprint you only half-expected. A ranked list of potential cofounders appears. You open the first profile and read it.

The first match feeling is recognizable: a mixture of curiosity and mild suspicion. The profile on the other side looks genuinely complementary. Their strengths fill your gaps. Their gaps look like yours in reverse. The shared brief describes a founding pair that would make sense. You wonder if this is real, or if the algorithm is flattering both of you.

The correct response at this stage is to not over-index on one match. Send a message. Browse three or four other strong matches. The first match sometimes works out. The strongest match is often the second or third one, because by then you've calibrated what you're actually responding to. A founder who commits to the first interesting profile without comparison tends to end up in a team they will regret two months later.

Typical duration: days to a week.

Weeks one to three: the first conversations

The first conversation is almost always a call or a coffee, not more messaging. Messaging is a medium for scheduling. It is not a medium for deciding whether to spend the next decade with someone.

The first call is deceptively easy. You describe your background, they describe theirs. You discover you share three references and two opinions. It feels promising. This is true of almost every first cofounder conversation. It is a terrible predictor of whether the partnership will work.

The second and third conversations are where the signal starts. These should be specifically structured. One conversation should be about the problem you're each drawn to: why this one, what have you tried, what have you learned that a stranger wouldn't know. Another should be about working style: how you make decisions, what you are bad at, what you need to be told directly. A third should be about the commercial and personal shape of the next two years: how much runway each of you has, what your family and partner know about your plans, what your walk-away conditions would be.

If the first three conversations are all upbeat and nobody has disagreed about anything, the conversations are not real yet. Useful founder conversations produce small disagreements. Small disagreements you resolve constructively are the best available signal that you can handle the bigger ones that come later.

Typical duration: two to four weeks.

Weeks three to eight: working on something real together

This is the stage most founding teams skip and the one that produces the most signal. Before either of you commits to anything, you work on something concrete together.

The "something concrete" should be small enough to finish in two to four weeks and real enough that you have to make actual decisions together. Common formats:

• A week of customer discovery where you each run five interviews and compare notes.
• A two-week technical prototype you build together, one person on backend, one on the use case framing.
• A short sales experiment: an outbound campaign with a concrete landing page, a specific offer, and measurable results.
• A structured teardown of a competitor product or a market, with written output at the end.

The goal is not to validate the idea. The idea will change. The goal is to observe each other in operating mode. Do they respond to messages within a day? Do they ship what they promised by Friday? Do they argue constructively, or do they go quiet when disagreeing? Are they as strong in practice as their profile suggested?

About half of founding pairs that reach this stage decide not to continue. That is a healthy ratio. Far more painful to discover these incompatibilities six months into a registered company than six weeks into an unofficial project.

Typical duration: three to six weeks.

Weeks eight to twelve: the commitment conversation

If the concrete work goes well, there's a conversation about making it official. This is the stage where most founders realize how much they don't know about what "official" means.

A proper commitment conversation covers, at minimum:

Equity split. Rarely exactly 50/50. Depends on who brought the idea, who brought the network, who is taking more financial risk, and who is going full-time when. Almost everyone finds this conversation uncomfortable. Do it anyway. Written down, agreed on, revisited if the situation changes.

Vesting. Four years with a one-year cliff is the standard reflex, and it's the standard reflex because it usually works. Without vesting, a cofounder who leaves in month eight takes their stake with them and creates a cap-table problem the remaining founders can't solve without paying them off. With vesting, the problem self-corrects.

IP assignment. Anything either of you built before the company has to be clearly owned by the individual or assigned to the company with explicit scope. Anything you build after the company is formed should be assigned to the company automatically. Without this, future investors will require it, and retroactive IP cleanups are expensive.

Roles and decision rights. Not org chart. Decision rights. Who has the final call on product direction, on hiring, on spending, on partnerships. Reasonable answers include "the technical cofounder has final call on architecture, the commercial cofounder has final call on pricing, joint calls on everything strategic". Unreasonable answers include "we'll figure it out as we go".

What happens if one of us wants to leave. Not a fun topic. The people who skip it regret it most.

What happens if we disagree and can't resolve it. An agreed escalation path (a board member, an advisor, a mediator) beats the alternative, which is a silent standoff that kills the company from the inside.

Most of this goes into a shareholders' agreement (osakassopimus in Finnish), which should be drafted by a lawyer, even if you pay for a simple template version. Do not skip this step. The Finnish legal market has several startup-focused firms that handle this economically.

Typical duration: two to four weeks.

Weeks twelve to sixteen: actually registering

Once the commitment is real, registering the company is the easiest part of the entire journey. You file the paperwork with PRH (the Finnish Patent and Registration Office), pay the registration fee, and a few days later you have a Y-tunnus, the business ID that makes your company a real legal entity.

The boring steps that surround this:

• Open a business bank account. In 2026 in Finland, Nordea, OP, and Holvi are the three most common options for startup OY registrations. Holvi is fast and designed for small teams; Nordea and OP are more traditional and better for teams that expect to take on larger financing.
• Register for VAT if your revenue will exceed the threshold (or voluntarily, to claim input VAT on purchases).
• Set up bookkeeping. Even if your revenue is zero, you have bookkeeping obligations from day one. Fiverr-level outsourcing does not cut it; find a real accountant with startup experience.
• Consider startup-specific insurance. Liability, cyber, and YEL (the self-employed pension system) are the most common first-year decisions. Insurance partners working with Finnish startups can often bundle these.

The actual Y-tunnus registration takes days. The paperwork around it takes a couple of weeks if you haven't done it before. None of this is difficult. It just has a volume of small decisions that is larger than first-time founders expect.

Months four and beyond: what a registered company looks like

The Y-tunnus is not the end of the journey. It's the beginning of a specific different phase.

In the first three months of a registered company with two or three cofounders, the patterns that predict long-term success are mundane rather than exciting.

Regular one-on-ones between cofounders, scheduled and protected, produce better outcomes than ad-hoc check-ins. The cadence is usually weekly.

Written decisions. Not meeting notes. Decisions that someone writes up, everyone agrees on, and anyone can find later. The discipline here is small and the compounding is large.

Monthly reviews of financial runway. Even if you have no revenue. Especially if you have no revenue. The founders who know exactly how many months of runway they have left make better decisions about when to raise, when to hire, and when to slow down.

Genuine separation of operational roles. If both founders are trying to do everything, neither will do any of it well. The specialization you negotiated in the commitment conversation has to actually happen in the operating rhythm.

Some founders share updates with investors or advisors monthly from day one, even without a formal round. The discipline of having to explain what you did last month to a non-participant sharpens decision-making in ways that few other habits do.

The failure modes, named honestly

A full piece on the founder journey has to name the failure modes that actually show up. The three most common:

The "too fast" team. Matched in week one, committed in week three, registered in week six, broken up by month nine. Usually a result of skipping the concrete-work stage. Fixable by insisting on the four-to-six-week working period before commitment.

The "too slow" team. Strong match, strong early conversations, stuck for six months in "let me finish my current thing first". Usually the person with less optionality registers the company; the other drifts away. Fixable by setting an explicit decision date and holding it.

The "commercial-cofounder-never-really-joined" team. A technical founder registers the company with a commercial cofounder who is "officially on board" but still part-time, waiting for a raise, or waiting for proof. Company grows, technical founder does everything, commercial cofounder has equity but no operational role, eventually either leaves or sits as a passive stakeholder. Fixable by requiring full-time commitment before registration, not after.

Avoiding these three covers most of the risk.

What the path actually takes

In total, from first meaningful match to Y-tunnus, the realistic timeline is three to six months for teams that move well, and nine to twelve for teams that drift. Faster than three months is usually a warning sign. Longer than twelve is usually a slow fade.

What determines which band a team falls into is rarely the match itself. It's the discipline of working through the specific stages honestly. The platforms and tools can only surface you to the right person. The hard part is always the middle: the concrete work, the commitment conversation, the boring paperwork, the operational rhythm. Nothing in that sequence is exotic. All of it is where companies are actually made.

The Y-tunnus is the moment you become a company on paper. The months around it are the moments you become a company in practice. The two are less aligned than most first-time founders expect, and the founders who succeed are usually the ones who gave the practical part the weight it deserves.