How to choose a freelance CTO: criteria, questions and red flags

A good freelance CTO has already led teams and products in production, can explain their choices to a non-technical founder, and leaves you owning the code and the accounts. Before you start looking, write down the decisions you expect them to make and how much time you can give them. Then check their track record, ask precise questions and start with a short engagement.

If what you mainly need is code produced against a clear scope, an agency may be a better fit. If the need goes beyond three days a week for several years, hiring a CTO makes more sense. This article helps you decide, then choose the right person.

Freelance CTO, agency or full-time CTO: what do you need?

These three options do not sell the same thing.

• A fractional freelance CTO (an external technical leader, available from a few hours to a few days a week) brings decisions and direction: roadmap, technical choices, hiring, oversight of the team or the providers.
• A development agency brings production capacity: a team that designs and builds a defined scope. It works well when you know what you want to build. The question to settle is who, on your side, approves the technical choices and checks what is delivered.
• A full-time CTO brings a daily presence and a long-term commitment, sometimes with equity. It is the logical choice when technology is the heart of your product and the need is daily. It costs a salary and employer contributions, takes months to hire, and a hiring mistake can surface late: in France, the probation period for an executive on a permanent contract lasts up to 4 months, renewable once under conditions, according to Service-public.gouv.fr.

Freelance CTO, agency or full-time CTO

Criterion	Fractional freelance CTO	Development agency	Full-time CTO
What you buy	Decisions and direction	Production capacity	One person, full time
Who owns technical choices	The CTO, with you	The agency, within its quote	The CTO, in-house
Volume	A few hours to several days a week	Depends on the project	Full time
Start	After a call and a scoping session	After a quote and a schedule	After hiring and notice
Cost	The time booked	The project or the time spent	Salary, contributions and hiring
Main risk	Limited availability	Dependence on the provider	A hiring mistake
Best when	You need direction without a full-time hire	The scope to build is clear	The need is daily and long-term

For a detailed cost comparison with a worked example, read what a freelance CTO costs.

How do you define your need before searching?

Choosing a freelance CTO goes wrong when the need stays vague. Answer four questions in writing before the first interview:

1. Which decisions must be made in the next three months? For example: choosing a technology, hiring a first developer, taking over an app built by an agency, preparing a fundraise.
2. How much time per week or per month? A few hours to make calls, one or two days a week to lead a team.
3. For how long? A one-off engagement, a few months, or an ongoing need.
4. Who on your side will work with them? A founder alone, an in-house team, an agency, freelancers.

Your answers to questions 2 and 3 place you in the matrix below.

Which format fits the time and duration of your need

A few weeksDuration of the needSeveral years

One-off engagementShort, intensive supportFractional CTOHire a CTOChoose a technologyAudit before a fundraiseLaunch a first versionOversee an agencyHire the first developersLead a team day to day

A few hoursTime needed per weekSeveral days

Which criteria matter when choosing a freelance CTO?

1. A verifiable track record in technical leadership. Ask for company names, roles, dates and links. A CTO who has shipped products and managed teams can show it. Be wary of numbers you cannot check.
2. Experience close to your situation. Mobile app or SaaS, consumers or businesses, regulated sector or not: the CTO does not need to have built your exact product, but they must know its constraints.
3. The ability to explain. You should understand every recommendation: what it costs, what it risks, what it rules out. If the answers stay buried in jargon, working together will be hard.
4. Independence. Ask whether they sell anything besides their time: development, hosting, licences. That is not a problem in itself, as long as it is disclosed and their recommendations stay reasoned.
5. Real availability. The hours or days booked, the usual response time, how urgent issues are handled. A CTO stretched across too many clients will struggle to follow your team.
6. Ownership and handover. The code, the accounts (hosting, database, domain name, app stores) and the documentation must be in your name, and the end of the engagement must include a handover.

Which questions should you ask in the interview?

Good questions force the candidate to give facts. Here are the ones I recommend, with what a good answer contains.

• “Which companies or products have you led, in what role, over what period?” Names, dates and links you can verify.
• “Tell me about a hard technical trade-off you had to make.” The options considered, the cost of each, why they chose, and what they would do differently.
• “What would you do in your first 30 days with us?” Understand the existing product and team before changing anything, then propose priorities.
• “How much time can you give us, and how quickly do you reply?” Precise numbers, consistent with their other engagements.
• “Do you sell anything besides your time?” A clear, direct answer.
• “Who will own the code, the accounts and the documentation?” You, in writing, in the contract.
• “How does the engagement end?” A handover, up-to-date documentation, access removed.
• “Can you explain [a topic from your product] as you would to an investor?” A short explanation without jargon, one you could repeat.

Which red flags should worry you?

• No verifiable references: no company names, no roles, no dates.
• A technology or tool proposed before they understand your need.
• A firm deadline or price promised before any scoping.
• Accounts, a code repository or a domain name opened in their name instead of yours.
• A refusal to put the scope, the volume and code ownership in writing.
• A guaranteed result, instead of commitments on deliverables and time.
• Technical terms they do not explain when you ask.

What should you check in the contract before signing?

One legal point deserves attention. Under French law, software created by an employee as part of their duties belongs to the employer (Article L113-9 of the Intellectual Property Code, in French). That rule covers employees. With a contractor, rights to the code pass by contract, and that contract must be in writing (Article L131-2 of the same code, in French). So include a clause assigning the rights to the code and documentation, and have the contract reviewed by your lawyer. If your company is outside France, check the equivalent rule where you operate.

• Scope and deliverablesWhat is expected, and what is excluded.
• Volume and rateHours or days booked, price excluding VAT.
• Time reportingA regular statement, with overruns approved in advance.
• Assignment of rightsCode and documentation assigned to you in writing.
• Accounts in your nameHosting, code repository, domain and app stores.
• ConfidentialityAn agreement as soon as you share sensitive data.
• End of engagementNotice period, handover and access removal.

Then start with a short engagement: a few days to produce an assessment and a roadmap, or a fixed-price audit of your app. You judge the person on a concrete deliverable before committing to regular support.

My take as a CTO

I am CTO in companies where I am also a partner. I co-founded Welco in 2019, built its technical team (developers, designers, DevOps and QA) and designed the architecture. I have been a partner and CTO at Jo’s Burger since February 2024. At Resilience Care, I managed 10 people across two teams for 8 months, in a regulated medical environment. What I advise founders is to judge a CTO on facts they can check, like the ones on my About page: companies, roles, dates, numbers. Also expect compared options: at Axiome Avocats, I compared several scenarios, with their costs and risks, before proposing a roadmap. With me, the code, the accounts and the documentation are in your name, and I hand them over at the end.

Frequently asked questions

What is the difference between a freelance CTO and a freelance developer? A CTO owns the technical vision, the investments and how the team is organised. They can write code when it helps, but the core of the role is analysis, decisions and management. A freelance developer builds features.

Can a freelance CTO work with our agency or our team? Yes. The goal is to clarify direction and collaboration without replacing the people in place: the CTO writes the brief, reviews deliveries and makes the trade-offs. Roles and communication are agreed from the start.

How much time should you book? A few hours a month is enough for key decisions. Leading a team takes more like one or two days a week. The cost details are in the rates guide.

How can you test a freelance CTO before committing? Give them a short engagement with a precise deliverable: an assessment, a roadmap, a documented decision. You judge the work itself, then decide on ongoing support.

Who owns the code a freelance CTO writes? In France, without a written assignment, the rights in principle stay with the contractor who wrote the code. Require a clause assigning the rights in the contract, and accounts opened in your name.

Next step

Before choosing between a freelance CTO and a hire, run the numbers with the calculator Freelance or full-time CTO: what does it really cost? (in French).

If a fractional CTO fits your need, the fractional CTO offer explains what I take on, how an engagement runs and the rate. You can also book a 15-minute call to ask me the questions in this article.

Sources

• Légifrance, Article L113-9 of the French Intellectual Property Code (rights in software created by employees), in French.
• Légifrance, Article L131-2 of the French Intellectual Property Code (copyright assignments must be in writing), in French.
• Service-public.gouv.fr, Probation period of an employee, in French, page checked on 12 August 2026.
• Techvisor, fractional CTO offer and About page.