You have a startup idea, a validated market, maybe your first customers, and you don't code. Before you set out to find a CTO, pin down the role you want them to play. A cofounder CTO takes equity and builds the product with you for years, while a freelancer ships a tightly scoped MVP in a few weeks and moves on to the next client. This guide is for the non-technical founder looking for a technical partner: which profile fits your stage, where to find a CTO in France, how to evaluate one when you can't code, and what salary and equity to offer.
Before you start: do you actually need a CTO?
The CTO (Chief Technology Officer) owns the startup's technical strategy: they choose the architecture, make the technical trade-offs and connect business needs to the code. At early stage, they write the code themselves. Once a development team exists, they hire and manage it.
Before you type "find a CTO" into Google, make sure a CTO is really what you need.
Cofounder CTO, salaried CTO, lead dev or freelancer
Four technical profiles cover four distinct needs.
The cofounder CTO joins the project as a partner: an equity stake close to yours, often no salary at first, and an equal say on technical and strategic decisions. The salaried CTO comes later, usually after a funding round, with a salary and some BSPCE (French employee stock warrants), to execute a technical vision that's already in place. Our guide to early startup hires covers the timing and package for a first employee. The lead dev writes code and supervises a small team: they apply the technical strategy without setting it, and that profile is enough as long as your product stays simple. The technical freelancer delivers a scoped project, bills by the day, then moves on to the next client, with no long-term commitment and no equity.
Mixing up these profiles costs you months of searching. A founder who hunts for a cofounder CTO to code an MVP that a freelancer could handle will spend months persuading developers to work without pay. The reverse also happens: a founder who hires a freelancer when they need a technical partner ends up with a delivered product and nobody to maintain or evolve it.
Decision table: which profile for your stage
| Your situation | Right profile | Why |
|---|---|---|
| Unvalidated idea, no revenue | Freelancer or vibe coding | Validate the market before looking for a partner |
| Validated market, first customers | Cofounder CTO | You need a long-term commitment |
| Need senior input, no partner yet | Fractional CTO | Architecture and technical decisions a few days a week |
| Seed round closed, product in production | Salaried CTO or lead dev | You can pay a competitive salary |
| One-off project | Freelancer (Malt, platforms) | Scope it, pay for it, move on |
The no-code or vibe coding option before you hire
Many early-stage startups don't need a CTO at the start: a good developer is enough, and sometimes you need none at all. With vibe coding and no-code tools (Bubble, Webflow, Make), a non-technical founder can build a working MVP in a few weeks.
When you pitch a potential CTO, a running prototype and 20 paying customers carry far more weight than a slide deck. The first shows a project in motion, the second shows an intention.
Build your lean canvas and test your assumptions with customers before you look for your CTO.
The CTO profile: 3 archetypes for early-stage startups
The same title covers very different profiles.
The hands-on technical lead CTO
This CTO codes every day. They pick the stack, build the architecture, push to production. They get their hands dirty, which is exactly what you need when there are two of you in an apartment trying to ship an MVP. Typical profile: 5 to 10 years of experience, has taken products all the way to production, would rather code than manage. Give them a terminal and some quiet over a team of fifteen developers any day.
Upside: you move fast, with them on the code and you on sales. Risk: some excellent developers communicate poorly. If you don't understand what they're building and why, the gap between tech and business widens quickly.
The product-oriented CTO (strategy and code)
Rarer and more valuable. They code, but they think product first. They ask "do users need this?" before "what language should we build it in?". They sit in on customer interviews and refuse to build useless features.
Upside: you build the right product, beyond a merely well-coded one. Risk: they have opinions on everything, including your sales strategy, which can be an asset.
The team-builder CTO (avoid at early stage)
This profile comes from large companies. They know how to hire 50 developers, set up Agile processes and negotiate six-figure cloud contracts. The problem: you don't have 50 developers, and you don't even have a product yet. The classic mistake is hiring a "desk CTO" who draws theoretical architectures instead of shipping an MVP. They'll hand you a beautiful roadmap in Notion while you burn through your cash.
This profile suits a post-Series A startup, and fits yours today far less well.
Which archetype for which startup?
- Pre-MVP, 0 to 2 people: technical lead CTO. Someone who codes and ships.
- MVP launched, first customers: product-oriented CTO. Someone who builds the right product.
- Post-raise, 10 people or more: team-builder CTO. Someone who hires and organizes.
Hiring a team builder at pre-seed is like hiring a factory manager before you have a prototype.
Where to find a CTO in France: the channels tech profiles use
For general cofounder-matching platforms and matching programs, see the comparison in our guide to finding a cofounder. Here we focus on the places developers already spend time, then on services built specifically around technical profiles.
Engineering schools, school incubators and alumni networks
School incubators (Polytechnique's Drahi X-Novation Center, 21st by CentraleSupélec, Incubateur HEC Paris) run events where engineers curious about entrepreneurship meet business founders. Alumni networks (Polytechnique, CentraleSupélec, Mines, EPITA, Télécom Paris) have internal directories and private LinkedIn groups. A clear message there that spells out your traction along with your idea reaches engineers who are already drawn to startups.
If you come from a non-traditional background, the free Station F Fighters program gives you access to the campus, where founders and technical profiles cross paths every day.
Developer communities and GitHub
On GitHub, look at who contributes to open source projects close to your field: a contribution history shows you what someone builds and how often. French-speaking developer Discord and Slack servers, dev.to and Hacker News's monthly "Who wants to be hired?" thread let you approach people who are actively looking.
Serious candidates ignore vague posts like "seeking passionate CTO for innovative project." Describe the problem, your first customers and what you've already validated.
Hackathons and tech meetups
Hackathons are still the best proving ground: in 48 hours, you see how someone codes under pressure and how they make trade-offs. Aim for the ones that draw developers (hackathons at 42, EPITA or Epitech, Station F tech events) and for technical meetups in your city built around a language or framework. Go even if the talks go over your head: you're there for the coffee breaks.
LinkedIn: post about your project
LinkedIn works when you post about your project: your progress, your numbers, your questions. Technical people considering entrepreneurship watch you for a while before they reach out. Developers rarely answer mass cold messages.
Fractional CTOs and freelancers while you look for a partner
Finding a cofounder CTO can take several months. In the meantime, you can bring in a fractional CTO: a senior profile who works with you a few days a week, sets up the architecture and helps you make technical decisions. On Malt, freelancers offer this service under the labels "CTO à temps partagé" or "CTO as a service" and bill by the day; compare the rates shown on their profiles. You keep all of your equity.
A good fractional CTO can become your cofounder CTO, or point you to the right person in their network. To get the MVP itself built, we compare agencies, freelancers and going solo in vibe coding: agency or solo?.
Platforms and services for finding a CTO
Four services target technical profiles. Two connect a founder with a future technical partner paid in equity. The other two place an experienced CTO with you a few days a week, paid by the day. Prices and figures were taken from each service's website on October 26, 2026.
Mon Associé: free matching with tech profiles
Mon Associé (mon-associe.fr) connects founders with CTOs and developers ready to become partners. You post your project, filter talent by stack, availability, remote work and expected equity, then chat privately. The platform is free on both sides, with no paid tier.
Every registered founder can also book a free 45-minute video call with a CTO consultant to scope their MVP and equity strategy. A developer who still has a salaried job can keep their profile anonymous until a match. The pool is small: the homepage listed 41 qualified tech profiles.
Le Bon Associé: a bigger pool you can filter for tech
On Le Bon Associé, formerly cofondateurauchomage.fr, you post a project card and specify the profile you're missing, including the Tech category (CTO, developer, data). The site had 5,482 members and 3,182 available profiles across all roles.
The free plan covers the card, likes, matches and messaging with your matches. The Pro plan costs €29 per month, €69 for 3 months or €199 per year, and unlocks direct contact details and advanced filters. Our article on Le Bon Associé and the search for a cofounder walks through the platform and the discount code swanbase offers.
CO-CTO: a fractional CTO from a collective
CO-CTO (co-cto.fr) brings together a collective of 700 CTOs and places one of them with you, usually 1 to 3 days a week. The service lists a day rate of €800 to €1,500 depending on the profile and promises a start within 1 to 3 weeks, after a scoping workshop. CO-CTO also offers technical audits and permanent CTO recruitment.
CO-CTO targets startups from seed to Series A. A pre-MVP founder with no budget is better off looking for a partner on the two platforms above.
Malt: searching for "CTO à temps partagé"
On Malt, a search for "CTO à temps partagé" (fractional CTO) returned 91 freelancers. Rates on the first page of results ranged from €495 to €1,500 per day. The "experience level" filter isolates the most senior profiles: 56 reported 16 or more years of experience. First contact is free, and you keep all of your equity.
Read the client reviews on each profile and ask which startups the freelancer has taken all the way to production. A "CTO" title on a profile proves nothing, and the 5 interview questions below apply to a fractional CTO too.
trouver-un-cto.fr: a guide comparing your options
Despite its name, trouver-un-cto.fr doesn't match anyone. The site publishes a one-page guide for startups with fewer than 10 developers that compares seven options: full-time CTO, part-time interim CTO, junior developer, junior freelancer, senior freelancer, low-code expert and agency. Read it before you pick a format, then come back to the services above to find the person.
Which service for your stage
Before the MVP, with no budget, look for a technical partner on Mon Associé and on Le Bon Associé's free plan: you pay them in equity. When an architecture decision is coming up and you still don't have a partner, a fractional CTO from Malt or CO-CTO can fill the role a few days a week. For general cofounder-matching platforms and matching programs, see the comparison in the guide to finding a cofounder.
How to evaluate a CTO when you can't code
You can't read the code, but you can still judge how a candidate thinks and communicates.
5 interview questions that need no technical knowledge
Ask these questions to understand how the candidate reasons. None of them requires technical knowledge:
-
"Explain how you would build our product as if I'd never seen a line of code." A good CTO can make things simple. If they drown you in jargon, they're trying to impress you rather than explain.
-
"What's the simplest product we could launch in 4 weeks?" A good CTO shrinks the scope; a bad one adds complexity. If the answer is "impossible, it'll take 6 months," run.
-
"Tell me about a project where you had to throw out code and start over." Every developer has made bad technical calls. Anyone who denies it has never built anything serious.
-
"How do you handle a disagreement with a non-technical founder?" A CTO who hides behind technical arguments to avoid the conversation will become unmanageable.
-
"What would you do if we had three months of cash left?" You want to hear "we cut the extras and focus on what brings in revenue," rather than "we raise money."
The project test: offer a paid mini-project
Never partner with someone on the strength of interviews alone. Offer a concrete, paid mini-project lasting one or two weeks, for example: "Build a prototype of our core feature with the stack of your choice." You'll see whether they deliver on time and how they keep you posted about blockers. Look at their product sense too: did the candidate ask questions about users, or just execute the specs?
Pay for the test, every time. A senior profile who agrees to work for free "to see how it goes" is either short on work or short on the experience they claim. Good people value their time, and paying shows you respect it.
Get a technical third party to evaluate (outside opinion, CTO consultant)
If you can't assess the code yourself, hand the review to someone who can: a CTO consultant, a senior developer friend or an incubator mentor. A technical audit costs little compared with a bad partnership. You'd have a company's books checked before buying it, so apply the same logic to your future partner.
Red flags to watch for
Some signals should set off alarms, even (especially) if you're not technical. The candidate refuses to explain things simply and stacks fifteen acronyms into every answer. They want to rebuild everything from scratch, the artist-developer syndrome, when you need a pragmatist. They've never shipped anything to production: GitHub projects are nice, but a product customers use every day is better. They ask no questions about users, so they won't build the right product. And they negotiate their equity stake before they've even seen the project.
Compensation and equity for a cofounder CTO
You've found the right person and they're ready to commit. Non-technical founders often rush this step.
How much equity for a cofounder CTO
Y Combinator recommends splits close to equal between cofounders: a CTO who codes unpaid for months takes the same risk you do. In a duo, the most common split is 50/50; when contributions differ, duos often go with 55/45 or 60/40. That puts your cofounder CTO at 40 to 50% of the equity.
A CTO who joins after the MVP, once traction exists, takes less risk and usually gets a smaller stake, worked out with the same criteria of contribution, commitment and risk. A salaried CTO is a different arrangement entirely: a salary and BSPCE, like any employee.
The classic mistake is offering a token stake to someone taking as much risk as you, then being surprised when nobody accepts.
Shareholders' agreement, vesting and BSPCE for your CTO
Put vesting on your cofounder CTO's stake, usually over 4 years with a 1-year cliff: if they leave after a few months, they keep none of the shares in a company they didn't build. If your CTO draws a salary or runs the company under employee tax status, you can also grant them BSPCE: article 163 bis G of the French tax code (CGI) makes them available to joint-stock companies (SA, SAS, SCA) subject to conditions on company age, corporate tax and ownership. Have a specialized lawyer draft the shareholders' agreement, and follow our guide to splitting equity between cofounders for the details on the cliff, good and bad leaver clauses and the shareholders' agreement.
Salary or equity: the trade-offs
Until the startup raises money, the cofounder CTO usually works without pay and holds a stake close to yours. After a first round, you can pay them a small salary. A CTO who joins after the seed negotiates a near-market salary and a smaller stake, often in BSPCE.
Be wary of a candidate who demands a market salary and a partner's stake from day one: they want to have their cake and eat it too. On the flip side, no serious developer will accept zero salary and a token stake.
Align your visions before you sign
Spend 2 to 3 hours on these topics before signing:
- Ambition: profitable niche business or unicorn? The top VCs in Paris expect global ambition. If your CTO wants a profitable niche company and you want to raise €10M, the partnership won't last.
- Pace: 50 hours a week or 35? Put a number on the table.
- Exit scenarios: what happens if one of you wants to leave, or if a buyer makes an offer?
These conversations are uncomfortable. Have them before you sign, while nobody has shares to defend yet.
The most common mistakes
Looking for a CTO too early (or too late)
Too early: you haven't validated your market or talked to 30 prospects. You're looking for a CTO to code an idea with no proof of demand, when a no-code prototype would have shown you there was no market in 3 weeks.
Too late: 50 customers and a no-code product held together with duct tape. Good CTOs would rather build than repair a shaky project. The longer you wait, the more the role looks like firefighting, and the more the hire costs you.
The right time: a validated market, proven demand, and a next step that requires a product you can't build yourself.
Confusing the best developer with the right CTO
The best developer in your network may still be the wrong CTO for your startup. An excellent developer codes fast and well. A good CTO codes too, and also makes architecture choices, prioritizes features, turns down useless ones, talks to customers and makes business decisions.
For a non-technical founder, the distinction matters: you need a translator between the technical world and the business world, and a coding genius who only talks to you through pull requests won't fill that role. Test communication as much as skill.
FAQ
What is a CTO in a startup?
The CTO (Chief Technology Officer) is the head of technology: they own the technical strategy, choose the architecture and connect business needs to the code. In an early-stage startup, they write the code themselves and often join as a cofounder with an equity stake. After a funding round, they hire and manage the development team.
How much equity should you give a cofounder CTO?
In a duo, 40 to 50% of the equity: Y Combinator recommends splits close to equal between cofounders, and duos most often go 50/50, or 55/45 and 60/40 when contributions differ. A CTO who joins after the MVP usually gets less. Always set up 4-year vesting with a 1-year cliff.
How can you find a CTO for free?
"Free" is misleading: you pay in equity instead of salary. Mon Associé is entirely free, and Le Bon Associé's free plan lets you post a project card and message your matches. Hackathons, tech meetups, GitHub, LinkedIn and engineering school alumni networks cost nothing either. You mostly pay in time: expect several months of active searching.
Where can you find a CTO in France?
For a technical partner, two platforms target tech profiles: Mon Associé (free) and Le Bon Associé (free, Pro from €29 per month). For a fractional CTO, CO-CTO lists a day rate of €800 to €1,500 and Malt has 91 freelancers listed under "CTO à temps partagé." Beyond platforms, look at engineering schools, hackathons, GitHub and LinkedIn, where you should post about your project.
Cofounder CTO vs. technical contractor: which should you choose?
Choose a cofounder CTO when technology drives your value proposition and you can offer a significant equity stake. Choose a contractor when you need a specific deliverable, when tech isn't your competitive advantage, or when you haven't validated your market yet. Validate first, then bring in a partner.
How do you evaluate a CTO's technical skills if you're not a developer?
Four methods: the 5 interview questions in this guide, which test the candidate's reasoning; a paid mini-project lasting one to two weeks; an evaluation by a technical third party (CTO consultant, incubator mentor); and reference checks. The most reliable signal is a candidate who has already shipped a product customers use in production.
