En
Fr
De
It
Es
Uk
Fractional CTO, agency or in-house team: which should you pick?
A fractional CTO gives you senior technical judgment for one or two days a week, commonly $5,000 to $15,000 a month in the US, but rarely writes most of the code. An agency builds the product for a fixed scope; with Lytvynov Production an MVP costs $10,000 to $50,000, and most land at $10,000 to $20,000. An in-house team costs the most per month and pays off once the product has traction and a steady roadmap.
For most non-technical founders the answer changes with the stage of the company. Before launch, buy a build and some independent oversight. After traction, start owning the team. The rest of this guide shows the numbers behind that advice and the combinations that work.
What does each option actually give you?
The three options are often compared as if they were interchangeable. They are not: each one buys a different thing.
| Fractional CTO | Agency | In-house team | |
|---|---|---|---|
| What you buy | Judgment, plans, oversight, hiring help | A designed, built and launched product for a scope | Ongoing capacity and long-term ownership |
| Time commitment | 1 to 2 days a week, often less | Full team for the project | Full time |
| Writes code | Usually a little or none | Yes, all of it | Yes |
| Typical cost | $5,000 to $15,000 a month (US) | MVP $10,000 to $50,000 with us; US/UK agencies 2.5 to 4 times more | $150,000 to $250,000 a year per senior US engineer, fully loaded |
| Time to start | 1 to 3 weeks | 1 to 3 weeks after scoping | 2 to 4 months per hire |
| Main risk | Advice without anyone to execute it | Scope creep and dependence on the vendor | Slow hiring, key-person risk, cost before traction |
The in-house figure is the full cost of a senior engineer in a major US market: salary, taxes, benefits, equipment and tools. A full-time CTO with equity usually costs more. These are ranges commonly seen in 2026, not quotes, and they vary a lot by city and seniority.
What does a fractional CTO do, and what does it not do?
A fractional CTO is a senior engineer or former CTO who works for several companies part time. For a non-technical founder, a good one does this:
- Turns the product idea into a technical plan: what to build first, what to buy, what to leave out.
- Chooses the stack and hosting with your future hiring in mind.
- Reviews agency proposals and estimates, and asks the questions you would not know to ask.
- Reviews code, architecture and security at milestones.
- Sets up the basics: repositories in your accounts, backups, access control, a release process.
- Prepares you for technical due diligence from investors.
- Writes job descriptions and interviews your first engineers.
What a fractional CTO usually does not do is build the product. One or two days a week is not enough to write an MVP, so you still need developers. Be careful with fractional CTOs who also resell development services: an advisor who earns a margin on the build is no longer an independent check on it. Ask directly whether they receive anything from the vendors they recommend.
Which option fits which stage?
The right mix depends on what your company needs to learn next.
| Stage | What you need | Recommended setup |
|---|---|---|
| Idea, no product yet | A first working product to test with real users | Agency with a written scope and fixed quote, plus a few hours of independent technical review |
| MVP live, first users | Fast iteration on what users do, stable releases | The same agency on a monthly plan or dedicated team, fractional CTO 2 to 4 days a month |
| Paying customers, steady roadmap | Ownership of the product and a team that stays | First 1 to 2 in-house engineers, fractional CTO or agency for capacity and handover |
| Raising a priced round | Credible technical leadership and diligence readiness | Fractional CTO who can step in for diligence, or a full-time CTO hire |
| Product is the business, 10+ engineers | A full engineering organization | Full-time CTO and in-house team, agency for specific projects |
The most expensive mistake we see is hiring an in-house team before the product has been tested with users. Recruiting takes months, and if the first version teaches you that the product should be different, you have a team built for the wrong product. The second most expensive is the reverse: staying with an outside vendor for years without anyone on your side who can read the code.
What do the options cost over the first year?
Here is an illustrative first year for a founder who needs an MVP and then nine months of improvements. Every number below is an assumption for comparison, not a quote and not our price list.
| First-year setup (illustrative) | Months 1 to 3 | Months 4 to 12 | First-year total |
|---|---|---|---|
| Agency only | MVP at an assumed $20,000 | Improvements at an assumed $5,000 a month | about $65,000 |
| Agency plus part-time fractional CTO | MVP at an assumed $20,000, CTO review at $3,000 a month | Agency as above, CTO at $3,000 a month | about $101,000 |
| Fractional CTO plus freelancers | Freelancers at an assumed $25,000, CTO at $6,000 a month | CTO at $6,000 a month, freelancers at $3,000 a month | about $124,000 |
| Two in-house engineers | Hiring takes 2 to 4 months, little gets built | Two senior US engineers at about $180,000 a year each, fully loaded | about $270,000 for 9 months of work |
The agency-only path is the cheapest and fastest to a product, and it carries the risk that nobody independent checks the work. A few thousand dollars a month of fractional oversight is often worth it on a build that the company will depend on. For a closer look at build budgets, our MVP development cost guide has ranges by scope.
How do you vet a fractional CTO?
Ask for things you can check, not opinions about technology:
- Which products did you lead from idea to production, and can I speak to one founder you worked with?
- How many companies do you work with right now, and how many hours a month do I get?
- Do you receive any commission or margin from vendors you recommend?
- What will you deliver in the first 30 days?
- How do you review an agency's code, and how often?
- Have you hired engineers before, and how did those hires work out?
- What happens when you leave: what documentation and access remain with us?
A good answer to question 4 is concrete: a technical plan, an architecture sketch, a list of risks, vendor recommendations and a review checklist for the build.
How do you vet an agency as a non-technical founder?
Without a technical background the safest protection is process, not trust. Our guide on how to choose a custom software development company has 12 questions to ask before signing. The four that matter most for a non-technical founder:
- A written scope with acceptance criteria, so you can tell whether a milestone is done.
- Weekly demos on a staging server you can click through yourself.
- Accounts in your name: repositories, hosting, domain, app stores and third-party services.
- A contract that assigns all intellectual property to you, with documentation good enough for another team to take over.
Fixed price works well for a first product when the scope is written down; our guide comparing dedicated team, fixed price and time and materials explains when each model fits.
What combinations work best?
Three combinations work well for companies with a non-technical founder:
- Agency plus advisor. The agency builds; an independent advisor or fractional CTO reviews the scope before you sign and the code at two or three milestones. Cheapest setup with a real safety net.
- Agency plus first in-house engineer. After launch you hire one engineer who joins the agency team, learns the code and gradually takes ownership. The agency keeps capacity for bigger features.
- Fractional CTO plus dedicated team. For a longer roadmap without the budget for a full in-house team: the fractional CTO sets priorities and reviews, a dedicated team works full time on the product.
The setup that rarely works: a fractional CTO plus a rotating set of freelancers with nobody responsible for the whole product. The coordination cost lands on the founder, which is exactly what you were trying to avoid.
How we work with non-technical founders
We are a software development company founded in 2020. A large part of our work is first products for founders who do not write code themselves, alongside internal systems for established companies. Every project starts with a written scope and a fixed quote after a short scoping call, and runs in milestones with weekly demos on a staging server you can open yourself.
A senior lead on each project explains technical trade-offs in plain language, and the code, accounts and documentation are set up so that your first in-house engineer, or an independent fractional CTO, can review or take over the work at any time. We built our own AI SaaS, AI Resume Master, in three months and grew it to 50,000 monthly active users, so we know the founder side of the table too. See our MVP development page for how a first build runs, or our AI consulting page if you first need a plan for where AI fits in your product.
