You have the business, you need the builder: finding a technical cofounder in Finland as a non-technical founder

You have customers who want the thing, or at least conversations that say they would. You can sell it, price it, and explain it in two sentences. What you cannot do is build it, and every developer you know has a salary, a mortgage and three side projects. This is the most common position in the Finnish directory, and it is solvable. It is just not solvable by posting "looking for a CTO" and waiting.

Who is available in Finland right now

Start with the size of the pool, because it changes how you should behave. There are 12 technical cofounders listed today on Trusted Cofounder: people who have said, in their own words and on a public page, that they want to build with someone. Most are in Oulu and Helsinki, a smaller group in Tampere and Espoo. Some have a product idea of their own and want a commercial partner; that is the mirror of your situation, covered in the post for technical founders who need someone to sell. Others are explicitly open to joining an idea that is not theirs.

That number is small enough that you can read every profile in an evening, and large enough that at least a few will fit. Browse them at /talent, filtered to technical cofounders. Each profile says what the person has built, what they are looking for, and when they were last active. Writing to someone is one message. If they accept, you have a conversation. Nothing is scored or ranked; you are reading and deciding, the same as they are.

If you have not yet decided whether you need a cofounder at all, or whether an agency would do, the next two sections are for you. If you have, skip to how to write the ask.

Why the "looking for a CTO" post fails

Every developer in Finland has seen the post. It appears in a Telegram group, a university Slack, a LinkedIn feed: a founder with an idea, a deck, sometimes a domain name, looking for "a CTO" to "build the MVP" for "equity". It gets no serious reply, and the founder concludes that developers are unreachable.

Read it from the other side. The developer sees a request for six to twelve months of unpaid work on a product they did not choose, for a share of something that does not exist yet, from someone who cannot evaluate whether the work is any good. They also see that the post could have been sent to fifty people, because it was. The word "CTO" makes it worse: it promises a title in place of a plan.

What a developer is actually asking, silently, is three questions. Has this person done anything yet that I cannot do? Will they carry their half, or am I the whole company? And if I say yes, do I get to make the technical decisions, or will I be arguing about React versus Vue with someone who has never opened a terminal?

The rest of this post is about answering those three questions before you send anything, so that the message you send is one a developer wants to receive.

Cofounder, outsourced CTO, freelancer or no-code: what each costs in Finland

Before you look for a person, be honest about whether you need one. Four options exist, and the right one depends on what stage you are at and what you can afford. The figures below are ranges from public Finnish rate guides and widely used equity guidance, not quotes; a real quote depends on the work.

Option	What you pay	What you get	When it fits
Technical cofounder	Equity, typically with four-year vesting and a one-year cliff; no cash	Someone who owns the product for years, makes the architecture decisions, and stays through the hard part	You are pre-revenue, the product is the company, and you want a partner, not a supplier
Outsourced CTO or agency	Consulting rates: in Finland roughly 80 to 150 euros per hour for mid to senior developers, more for specialists (Duuna's 2026 IT consultant pricing guide)	A built first version, on a schedule, with no ownership of the outcome	You have funding or revenue, a clear specification, and you accept that you will need someone in-house later
Freelancer	Same rate band, usually lower for junior work; often project-priced	A specific piece built, then gone	A prototype for validation, a landing page, an integration
No-code or low-code	Tool subscriptions; your own time	A working prototype you can change yourself	Validating demand before you have anything to offer a cofounder

Three things the table does not say.

First, the outsourced option looks affordable per hour and rarely is per product. A modest first version is hundreds of hours, and the moment it needs changing, which is the moment a customer touches it, you are back on the meter. Many Finnish founders who start with an agency end up looking for a technical cofounder a year later, now with a codebase the cofounder did not write and does not want.

Second, the public grant that used to soften this decision is gone. Business Finland's innovation voucher (innovaatioseteli), which paid 75% of purchased expert services up to 4,500 euros, closed to new applications on 17 October 2024, as Business Finland shifted toward funding research and development projects. If a page you are reading still recommends it for your first prototype, the page is out of date.

Third, "outsourced CTO" and "technology lead" services exist in Finland and are legitimate for a company that already has engineers and needs direction. For a company with no product and no engineers, what they sell is advice about work nobody is doing. The searcher who types "cto ulkoistus" usually needs the first column, not the second.

If you cannot pay consulting rates and you cannot yet offer a cofounder anything but the idea, the answer is the fourth column: build the ugliest possible version yourself, prove somebody wants it, and come back to this post with evidence. That evidence is what the next section is about.

What a technical cofounder wants to see from you before replying

The developers in the directory are not short of ideas. They are short of people who will do the non-technical half properly. Before you write to anyone, be able to show four things.

Evidence of customers, not opinions about a market. Ten conversations with people who have the problem, with notes. Three who said they would pay and what they would pay. One who is using your no-code prototype or your spreadsheet version today. A developer can build almost anything; what they cannot do alone is know whether it should exist.

Evidence that you have already done work. A landing page with sign-ups. A pitch you have given to strangers. A pilot agreement, even an informal one. A list of the first twenty target accounts with names. The point is not the artefact, it is the proof that you execute without being told to.

Your own commitment, stated plainly. Full time or not, and if not, when. What you are living on. Whether you have put your own money in. A developer is being asked to bet years; they want to know what you are betting.

Why this person, not the next one. If your message could be sent to anyone with a GitHub account, it will be read as if it was. Say what you saw on their profile that made you write: the domain, the stack, the sentence in their description that sounded like your problem.

None of this requires technical knowledge. It requires having started.

Where technical cofounders are in Finland

Finland's technical talent is concentrated around four university faculties and one very large employer, and it is worth knowing which is which, because each produces a different kind of cofounder.

Oulu. The Faculty of Information Technology and Electrical Engineering at the University of Oulu has around 60 professors and 600 researchers across wireless communications, electronics, computer science and software engineering, and hosts the national 6G research flagship. Next to it, Nokia's Oulu campus employs around 3,000 people on radio research, design and manufacturing (Nokia, September 2025). The result is a city of embedded, wireless and hardware engineers who have shipped products at scale, many of whom have lived through a Nokia restructuring and think about a second act. The guides to 5G and wireless cofounders in Oulu, hardware and wearables cofounders in Oulu and Oulu's technical cofounder scene go deeper, and the OAMK guide covers the applied-sciences side. Oulu is also where most of the directory lives.

Espoo and Helsinki. Aalto's Department of Computer Science is the largest computer science unit in Finland, and Otaniemi has the densest student-startup culture in the country; the Aalto guide explains how to approach it without being a tourist. The University of Helsinki's Department of Computer Science at Kumpula has over 2,300 students and a strong data science and AI bent. Helsinki has the most software-as-a-service and fintech experience per square kilometre; the Helsinki technical cofounder guide covers where to stand.

Tampere. Tampere University's Computing Sciences sits on the Hervanta campus alongside signal processing, machine vision and industrial automation research, which is why Tampere's technical cofounders skew toward industrial and physical products. See the Tampere University guide.

The directory. Every one of the people above is a person you would have to find, approach cold and persuade to talk. The people listed on /talent have already said they want the conversation. Start there, and use the universities and meetups for the person you could not find.

How to write the ask

Two pieces of writing decide whether you get a reply: the description on your own profile, and the first message you send. Both should be specific enough that they could only have come from you. Here is a worked example of each, invented for this post; borrow the shape, not the words.

A description that works (this goes in your profile's "Looking for" field, which takes 30 to 1,500 characters):

I run procurement for a mid-sized Finnish food wholesaler and have spent two years watching small restaurants order by phone and WhatsApp because the ordering tools are built for chains. I have 14 restaurant owners in Helsinki who have told me what they would pay for something simpler, and four using a Google Form version today. I am looking for a technical cofounder to own the product: web first, mobile later, integrations with the two wholesalers that cover most of the market. I am full time from January, self-funded for a year, and I want a partner who makes the technical calls. Equal footing, vesting for both of us, and a shareholders' agreement before we write a line. Helsinki or remote within Finland.

A first message that works (sent to one person, after reading their profile):

Hi. I read your profile because you mentioned building ordering integrations for a logistics client, which is exactly the unglamorous problem I am trying to solve for small restaurants. Short version: 14 owners interviewed, four on a spreadsheet version, two wholesalers willing to test an API. I am not looking for someone to build my idea for free; I am looking for someone to own the product as a cofounder with equal equity and proper vesting. I can show you the interview notes and the form data before you decide anything. Would a 30-minute call next week make sense? If the answer is no, no hard feelings, and thank you for reading.

Notice what both do: they name the evidence, they state the terms, they name the person's own work, and they make the next step small.

Equity and vesting when the technical person joins after the idea

The commonest mistake is to treat the idea as most of the value. It is not; execution over the next four years is. Y Combinator's standing advice is that cofounder splits should be equal or close to it, because a cofounder who feels underpaid at the start is a cofounder who leaves. Widely cited guidance puts a technical cofounder who joins before there is a product at 40 to 50%, and one who joins after a working MVP exists at somewhere between 15 and 30%, rising with how much of the future work is theirs.

Whatever the split, two mechanics matter more than the number. Vesting: shares are earned over four years with nothing vesting in the first year (the cliff), so that if either of you leaves at month eight, the company is not half-owned by someone who is gone. The shareholders' agreement: in Finland this is the osakassopimus, a private contract between founders that sits alongside the public articles of association and covers vesting, what happens on departure, IP assignment, and how deadlocks are broken. The Finnish equity split guide walks through the numbers; the osakassopimus guide (in Finnish) covers the agreement itself. Sign both before the first commit, not after the first argument.

Red flags in both directions

You are evaluating them; they are evaluating you. The full list of cofounder red flags applies to everyone, but three are specific to this pairing.

From the technical side: someone who wants to rebuild everything in their favourite stack before talking to a customer; someone who cannot explain a technical choice in plain language; someone who has never shipped anything that another person used.

From your side, the flags they are watching for: a founder who guards the idea like a secret and wants an NDA before a conversation; a founder who says "you just need to build it" as if the building were the small part; a founder with no evidence that any customer exists.

If you recognise yourself in the second list, fix that first. It costs nothing and it is the difference between silence and a reply.

Frequently asked questions

Do I need to learn to code first? No. You need to learn enough to have a conversation: what an API is, why "just add a feature" is rarely just, how a database differs from a spreadsheet. A weekend with a beginner's course is plenty, and it signals respect.

Should I offer a salary as well as equity? If you can, a small one changes the conversation entirely, because it removes the "unpaid work for a stranger" objection. If you cannot, say so and be specific about when that changes.

Is it realistic to find someone outside Helsinki? Yes. Most of the directory is in Oulu, and Finnish teams work across cities more than founders expect. Remote within Finland is normal; the remote versus local guide covers the trade-offs.

How long does it take? Founders who have the evidence in the section above and write ten specific messages usually have real conversations within weeks. Founders who post a general call and wait usually have nothing within months. The variable is you, not the market.

What if someone says yes but wants to stay part time? Common and workable at the start, if the vesting reflects it and the date for going full time is written down. Vague part-time cofounder arrangements are where most founding teams quietly die.

The complete picture of how founders find each other here, every channel ranked, is in how to find a cofounder in Finland. If you are the technical half reading this, the mirror post is yours.