Fractional CTO vs agency vs freelancer vs embedded engineer: which do you need?
Ask one question first: is your problem a product, or the manual work between your apps? A fractional CTO is right when you are building a product or leading developers. An agency suits a big, fixed project. A freelancer suits a small, well-defined job. An embedded engineer suits a firm whose people lose hours between disconnected tools.
| Fractional CTO | Agency | Freelancer | Embedded engineer (Forge) | |
|---|---|---|---|---|
| Typical cost, US | $4,000-10,000 a month advisory; $10,000-25,000 active | $10,000-75,000 a project; retainers $1,000-12,000 a month | $75-150 an hour | $2,000 / $3,500 / $7,500 a month, first build included |
| Typical cost, UK | Median CTO contract day rate £635 | Usually quoted per project; few published UK guides | Median developer contract day rate £525 | £1,600 / £2,800 / £6,000 a month |
| Speed to start | A few weeks to find the right person | Weeks of scoping and proposals | Days, if you find a good one | Two-week ops audit, first build live in 2-6 weeks |
| Who maintains it | Your developers (it advises, it does not build) | You, unless you buy a support contract | Whoever you can get hold of | We do, on the monthly plan |
| Best for | Product companies, firms leading a dev team | A large, clearly specified project | One small, well-defined job | People businesses with hours lost between apps and no engineer |
| Worst for | Firms with nothing to lead and nothing to architect | Small, shifting, ongoing needs | Anything that has to keep running for years | Firms building their own software product |
US ranges are typical, compiled from published rate guides: fractional CTO monthly ranges from A.Team, June 2026, agency project and retainer ranges from Codewave, August 2026, freelancer hourly rates from Layer3 Labs, September 2026. UK medians are contract day rates for the six months to October 2026 for CTOs (IT Jobs Watch, October 2026) and software developers (IT Jobs Watch, October 2026). Our prices are from our pricing page.
The four options in plain terms
All four get called "technical help", and owners searching "fractional CTO vs agency" often are not sure which one they are describing. Here is what each one actually is.
A fractional CTO
is a senior technology leader who works with you part-time. They make decisions: what to build, what to buy, how it fits together, who to hire. They do not usually write the code. Think of them as a part-time executive.
An agency
is a team you hire to deliver a project. You agree a scope, they build it, they hand it over. Some sell a support contract afterwards; many do not, or price it as an extra.
A freelancer
is one developer you hire by the hour, day or job. Good freelancers are fast and good value. The risk is that everything lives in one person's head, and they have other clients.
An embedded engineer
works inside your business on an ongoing basis, finding where your people lose time and building and running the tools that give it back. That is what we do at Forge. We work with people businesses: businesses that sell their people's expertise and time, such as agencies, accountants, lawyers and consultants.
The test: a product problem or a between-apps problem?
Most of the confusion goes away with one question.
A product problem means software is what you sell, or is about to be. You need architecture, a hiring plan, someone to lead developers and keep them honest, and decisions that will shape the next five years. That needs senior judgement, which is what a fractional CTO is for.
A between-apps problem means your software is fine on its own, but nothing talks to anything else. Your account managers copy client updates from the project tool into emails. Someone rekeys hours from timesheets into the invoicing app. The Friday report gets rebuilt by hand every week. Nobody needs a five-year technology strategy for that. They need the fix built, connected to the apps they already use, and kept running when one of those apps changes.
Here is a quick way to tell which one you have. Write down the three things that annoy your team most about your tools. If the list says "we need to choose a platform for our new app" or "our developers need direction", it is a product problem. If it says "I copy this from here to there", "nobody knows the latest version" or "the report takes all Friday", it is a between-apps problem.
Most 10-60 person people businesses we talk to have a between-apps problem. Many of them searched "cto as a service" first, because that was the only name they had for "someone technical".
Pick a fractional CTO if...
- You are building a software product, or about to, and need someone to own the architecture.
- You already have developers (in-house or outsourced) and nobody senior to lead them.
- You are about to choose a platform that will be hard to leave, and you want an expert to make that call with you.
- You are raising money and investors want a named technical leader.
- You need help hiring your first engineers and judging whether they are any good.
In those situations, a few days a month of senior judgement is worth the money, and we would tell you to hire one rather than us. A good fractional CTO stops expensive mistakes before they happen. Advisory engagements typically run $4,000-10,000 a month in the US for 10-15 hours, rising to $10,000-25,000 for 20-40 hours (A.Team, June 2026). In the UK, the median CTO contract day rate is £635 (IT Jobs Watch, October 2026). Our fractional CTO cost guide goes into the detail.
What you will not get is working tools. A fractional CTO for a between-apps problem often produces an excellent document and a recommendation to hire a developer.
Pick an agency if...
- You have one large, clearly specified project - a client-facing app, a big migration, a rebuild of your website and booking system.
- The scope will not change much once it is agreed.
- You have someone in-house who can own the result afterwards, or you are happy to buy a support contract.
- You want a team, not one person, because the work has design, front-end and back-end parts happening at once.
Agencies are good at delivering a defined thing on a defined date. Project fees typically run $10,000-75,000 depending on scope, and retainers for smaller firms $1,000-3,500 a month (Codewave, August 2026). Where agencies struggle is small, shifting work. Every change becomes a change request, and the meter starts again. The other risk is the hand-off: the project ends, the team moves on, and six months later an app you rely on changes and nobody is watching.
Pick a freelancer if...
- The job is small, well-defined and one-off: a single integration, a form, a script that moves data once.
- You, or someone on your team, can describe exactly what "done" looks like.
- It does not matter much if the freelancer is busy with another client next month.
- You have a way to check the work, or a trusted referral.
A good freelancer is often the best-value option for a single job. In the US, freelance rates typically run $75-150 an hour (Layer3 Labs, September 2026). In the UK, the median software developer contract day rate is £525 (IT Jobs Watch, October 2026). The catch is the bus factor - if that one person disappears, so does the knowledge of how your tool works. For anything your team will rely on every day for years, that matters more than the hourly rate.
Pick an embedded engineer if...
- Your team loses hours every week to work between apps: copying, chasing, rekeying, rebuilding reports.
- You do not have an engineer, and you do not want your ops lead to become one.
- You want the tools to keep working after they are built, without anyone on your team looking after them.
- You would rather pay a known monthly price than scope and re-scope projects.
That is our model. A two-week ops audit ($2,500 / £2,000, credited to your first month) maps your apps and counts the hours your team loses. Then a monthly plan - $2,000, $3,500 or $7,500 (£1,600 / £2,800 / £6,000) - includes your first build and covers looking after it: watching it, fixing it when one of your apps changes, and building what you ask for next. Monthly plans have a 3-month minimum. The software runs on your own accounts, so you own it, and you pay those tool costs directly. It works in four steps - scope, build, roll out, improve - and rolling out means training your team so people actually use the tool. More on how it works on our custom software for small business page.
What we are not: a substitute for a fractional CTO if you are building a product. We do not lead your developers or plan your engineering hiring.
Our recommendation: how we'd decide for a 20-person firm
Picture a 20-person agency or accounting firm with eight to twelve apps, an office manager, and no engineer. Here is how we would decide, in order.
- Run the test. Write down the three most annoying things about your tools. If they are all manual work between apps (copying, chasing, rekeying), skip the fractional CTO for now. You have nothing for one to lead.
- If it is one small job, try a freelancer. A single integration between two apps, done once, rarely needs more. Get a referral, agree what "done" means in writing, and keep a copy of everything they build.
- If it is one big, fixed project, get agency quotes. Ask every agency the same question: "What happens in month seven when one of the apps changes?" The answer tells you who will look after it.
- If it is several small problems that keep coming, embed someone. This is the most common pattern in people businesses. The problems change as the firm grows, and the tools need looking after. A monthly plan fits that shape better than a string of projects.
- If you are building a product, hire the fractional CTO first. Then hire builders under them. We would happily point you to one.
Being honest: for a 20-person firm with one annoying task and a tight budget, a good freelancer at a few thousand dollars is usually the right answer, not us. Our plans make sense when there is more than one problem, or when the thing has to keep running.
Worked example: a client portal, four ways
Take one real job: a client portal, one branded home per client where every deliverable, brief and sign-off lives. Our custom software cost guide puts the typical market cost of a client portal at $8,000-18,000 in the US or £6,000-14,000 in the UK, taking 2-6 weeks (typical, compiled from published rate guides). At Fame, it meant producers stopped hunting through Drive folders and answering "where is the latest version?" emails.
With a fractional CTO
They would help you choose between building it and buying a portal product, write a specification, and probably recommend an agency or a developer to build it. At $4,000-10,000 a month for advisory work, a month or two of their time is a sensible spend if the portal is part of a bigger product strategy. For a portal on its own, you have paid for a decision, and you still need a builder.
With an agency
You would expect a quote somewhere in that $8,000-18,000 (£6,000-14,000) range for a portal like this, delivered in 2-6 weeks. Then ask about support. If your project tool or Drive structure changes next year, someone has to update the portal, and that is usually a new piece of work.
With a freelancer
Possibly the lower end of the range, depending on their rate and how much of the build they have done before. Make sure the code and accounts are in your name from day one, and agree how changes will be handled after launch.
With Forge
The ops audit ($2,500 / £2,000) is credited to month one, and the portal is the first build included in your plan. On the $2,000 / £1,600 plan with the 3-month minimum, the first three months cost $6,000 / £4,800 in total, and we keep looking after the portal after that, fixing it when an app changes. If the portal is the only thing you will ever need and nothing will change, a one-off build from an agency or freelancer may well cost you less over three years. Our plan is cheaper when there is a second and third problem waiting behind the first.
We built this portal, and others like it, for our own podcast agency, Fame. Across all of Fame's tools, the team got back 5,460 hours as of 14 October 2026.
The question underneath "cto as a service"
When people search for CTO as a service, they are usually asking for one of two things. Some want a technical leader without a full-time salary: that is a fractional CTO, and it is a good model for product companies. Others want "a technical person who sorts out our tools": that is a builder who stays, whatever you call them. The titles matter less than the question we started with. If your people are losing hours between apps, hire someone who will build the fix and keep it running.
Questions, answered plainly
What is the difference between a fractional CTO and an agency?
A fractional CTO is a part-time senior leader who makes technology decisions and leads developers; they do not usually build. An agency is a team that builds a defined project and hands it over. Hire a fractional CTO for decisions, an agency for a fixed build.
How much does a fractional CTO make?
Typical US rates run $4,000-10,000 a month for advisory work of 10-15 hours, and $10,000-25,000 a month for 20-40 hours. In the UK, the median CTO contract day rate is £635.
Is fractional CTO a thing?
Yes. It is a common model for startups and product companies that need senior technology leadership but not a full-time executive. Engagements usually last months, often until the company hires a permanent CTO.
Should I hire a fractional CTO or a freelancer?
Hire a fractional CTO if you need decisions, architecture and leadership of developers. Hire a freelancer if you have one small, well-defined job to build. If you have several ongoing tool problems and no engineer, consider an embedded engineer who builds and looks after the fixes.
What is CTO as a service?
It usually means a fractional CTO: senior technology leadership on a part-time or monthly basis. Some firms use the phrase for any outsourced technical help, so check whether you are buying advice or people who build.