Outsourced CTO or agency: which one does your product need?

What's the difference between an agency and an outsourced CTO?

The comparison looks like a choice between two vendors, but they don't sell the same thing. A development agency, or a studio, sells production capacity: a team that designs, builds, tests and ships software, usually for a scope and a price fixed in advance. An outsourced CTO sells judgement. They make the technical decisions that commit the company, check what gets delivered and answer for it to management, a few days a week and without being on the payroll. The first writes the code. The second writes very little of it, but decides what should be built, how and by whom.

So the real question isn't which one is better, but who, on your side, decides, builds and checks. When the agency holds all three roles, nobody is reviewing its work.

French market ranges in 2026, detailed in our articles on the cost of an MVP and outsourced CTO rates.

What an agency does well

A good agency is the fastest way to go from a written need to live software. It brings together, in one go, skills a young company would take months to hire: design, web and mobile development, testing, deployment. It commits to an outcome, often at a fixed price, which makes the budget predictable. And once the project ships, you don't have a team to keep busy.

The model works well under three conditions: a written, stable scope, someone on your side who can test and sign off what's delivered, and a code handover written into the contract. An agency can also bring in senior reinforcements for a specialist topic: that's how we built, alongside the team at the UPTIME agency, an offline-first app for regulatory inspections (case study).

What an agency can't do for you

An agency can't be both the one that builds and the one that checks. It isn't a question of honesty, it's a question of position. A vendor that prices the project, picks the stack it knows, builds and then tests its own work has no reason to tell you the quote is too broad, the architecture is oversized or a feature can wait. We're a studio ourselves: the point applies to us whenever we deliver a project.

Signs that nobody is checking your vendor's work:

• You can't tell whether a quote is reasonable, or compare it with another one.
• The code, the hosting or the domain name sit in the vendor's accounts.
• Every change comes with a new quote that nobody questions.
• The same bugs come back from one release to the next, with no clear explanation.
• Nobody on your side can describe the product's architecture in ten minutes.

If two of these sound familiar, the problem isn't the agency: it's the lack of technical leadership on your side.

What an outsourced CTO brings, and what they don't do

An outsourced CTO plays the role of technical director without being an employee, usually from half a day to two days a week. With an agency, they're your technical representative: they turn your goals into a scope, review quotes, approve architecture choices, check the quality of what's delivered and make sure the code, access and documentation stay yours. They can work with the agency you already have, so nothing needs to change on the development side. Without a vendor, they build up an in-house team: organisation, hiring, continuous integration, code review.

What they don't do is build your software on their own. At one or two days a week there isn't time, and it isn't what you're paying for: a CTO who spends their days coding is selling you development at a technical-leadership price. They always need someone to execute, whether that's an in-house team, a freelancer or an agency.

That's the role Adrien Le Breton, Neodev's founder, played for INTEGRALE and NOMADE (case study), between Reunion Island and Madagascar: management, business teams and outside vendors worked from the same roadmap, with shared reporting.

Should you use both?

Often, yes, as soon as nobody on your side can judge technical work. It's the most common setup for non-technical founders and for SMEs without an IT department: the agency builds, the outsourced CTO scopes and checks, and you keep the decisions that concern your business. Here's how the roles split.

Oversight stays a small share of the budget. For a B2B SaaS with a standard scope, our MVP budget simulator gives €25,000 to €31,000 at a fixed price, for 2 to 3 months of development. An outsourced CTO at half a day a week costs €1,200 to €2,000 a month, so €3,600 to €6,000 over three months. For a smaller project, a one-off review is often enough: a read of the quote before signing, then a code review halfway through.

Which format for your situation?

The table covers the cases we come across most often. Budgets are starting points, not quotes.

A fixed-price diagnostic usually takes 2 to 5 days depending on the size of the codebase. For an AI-generated prototype, see also what to check to take over an MVP built with Lovable or Bolt.

What to check before signing, in either case

• Code ownership. The contract must assign you the rights to the code produced, and the repository must be opened in your company's name from day one.
• Access. Hosting, domain name, third-party services: everything should sit in company accounts, with the vendor as a guest.
• Handover. Plan for minimal documentation (setup, architecture, deployment) and a handover period at the end of the engagement.
• The finish line. For an agency, acceptance: who signs off, and against what criteria. For a CTO, the deliverables expected each month and the exit notice.
• Independent oversight. When the same vendor builds and also holds the technical leadership, ask how decisions are documented, and have a third party review the code from time to time. That applies to us too.

Frequently asked questions: outsourced CTO or agency

Can an agency act as your CTO?

Partly. Many agencies have a technical director who gives their clients good advice. But they work for the agency: they won't recommend cutting the scope it bills for, or switching vendors. For a one-off opinion, that's fine. To steer your product over time, you need someone who answers only to you.

Can a senior lead dev replace an outsourced CTO?

To run a team day to day, often yes. A senior lead dev organises the work, reviews code and holds the quality bar. What they usually lack is the leadership side: making trade-offs with management, building a technical budget, hiring, preparing for investor due diligence. If what you mainly need is to ship faster, a Tech Lead to reinforce the team costs less than a CTO.

Can you move from an agency to an in-house team?

Yes, and it's often the natural next step after an MVP. The move needs preparing: code and access in your name, up-to-date documentation, then a first developer hired who works alongside the agency for a few weeks before it steps back. An outsourced CTO can lead that transition, from the job description to the technical interviews. Our article startup without a CTO walks through the steps for your stage.

How long should you keep an outsourced CTO?

For as long as structural decisions keep coming up. The first months are the busiest: assessment, roadmap, choice of vendors. Then the pace drops. The goal isn't to stay, it's to leave behind a team or a successor able to take over. Formats and budgets are covered in our article on outsourced CTO rates.

And at Neodev?

We do both jobs: we build products with senior engineers, and we act as an outsourced CTO, remotely, from half a day to two days a week. So this article isn't trying to sell you one over the other. On the first call, we look with you at which of the two formats fits, or whether to combine them.

If you don't know what the code you have is worth, start with a fixed-price diagnostic: 2 days and €1,130 for an express diagnostic, deducted if you carry on with us. You can read a sample express diagnostic before you decide. And for a product still to be built, our MVP development page describes how we work as a studio.