Hiring a fractional CTO, an agency, or a freelancer: which one do you actually need
The three options overlap enough to cause confusion, but they're solving different problems. Here's how to think through the decision based on what you're actually trying to do.
The three options get conflated because they all provide technical help from outside your organisation. But they're structured to solve different problems, and choosing the wrong one is an expensive lesson.
What each one actually is
A freelancer is an individual delivering defined work for a defined period. Best at: a specific known scope with a clear output — build this feature, fix this bug, implement this integration. The risk is scope creep and knowledge retention when they leave. The advantage is flexibility and speed to start.
An agency is a team delivering a project or retainer, typically at a managed level of abstraction. You describe what you want; they figure out how to build it. Best at: full builds, defined projects, and ongoing execution where you don't want to manage individual engineers. The risk is communication overhead, margin stacking, and junior staff on your work. The advantage is breadth of resource and a single point of accountability.
A fractional CTO is a senior engineer providing strategic and technical leadership on a part-time basis. Best at: judgment calls that require experience — architecture decisions, vendor selection, team oversight, technical due diligence. Not at: delivering code volume. The advantage is that you get 20 years of experience for 2 days a month. The risk is that without enough engagement hours, the context doesn't build properly.
The signals that point toward each
You probably need a freelancer if:
- You have a specific, well-defined technical task with a clear outcome
- Your internal team has the capacity to manage the work but not to do it
- The task is bounded enough that knowledge handoff at the end is manageable
- You want flexibility — start quickly, stop when it's done
Common use cases: build a specific app integration, implement a design system, migrate a data set, add a feature to an existing codebase.
The failure mode: using a freelancer for open-ended, architectural work. "Help us improve the site" is too loose. "Implement the Klaviyo integration using these spec docs" is the right shape of engagement.
You probably need an agency if:
- You have a significant build to deliver and you don't want to manage individual contributors
- You need multiple disciplines in one engagement (design, development, QA)
- The project has a defined end state that can be contracted
- You want a managed service with accountability at the relationship level, not the individual level
Common use cases: full site rebuilds, complex platform migrations, product launches that require coordinated execution.
The failure mode: using an agency for ongoing strategic decisions. Agencies execute well; they don't always tell you when the brief is wrong. If you need someone to push back on your own assumptions, an agency structure can work against you.
You probably need a fractional CTO if:
- You're making significant technical decisions regularly (platform choices, architecture, build vs buy) and you don't have a senior engineer on staff to validate them
- You have a dev team (internal or agency) that needs a technical oversight layer
- You're spending money on engineering and you're not sure whether you're spending it right
- You want one senior person accountable for the technical direction of your business without the overhead of a full-time hire
Common use cases: scaling DTC brands without a technical co-founder, brands with a junior in-house dev team, businesses buying or selling a technical asset that needs due diligence.
The failure mode: expecting a fractional CTO to deliver code volume. The fractional model is optimised for judgment and oversight. If you need engineering output, you need a freelancer or agency doing the implementation with the fractional CTO overseeing it.
The combination that actually works at scale
For most eCommerce brands in the £1m-£10m range, the effective setup is:
Fractional senior engineer/CTO for strategy, architecture decisions, vendor management, and quality oversight — 2-4 days per month.
A small number of trusted freelancers for specific execution work, managed or reviewed by the senior layer.
This beats an agency relationship for most ongoing technical work because:
- The judgment layer is the same person every time, building real context
- You're not paying agency margin on execution work
- You can flex execution resource up and down without renegotiating a retainer
The agency model makes more sense for defined, bounded projects — a new platform build, a Hydrogen migration — where project management and delivery accountability matter more than ongoing relationship continuity.
The honest question to ask first
Before deciding between the three, answer this: what decision are you trying to make or what outcome are you trying to achieve?
If the answer is "I have a specific technical task to complete" — freelancer.
If the answer is "I have a project to deliver" — agency.
If the answer is "I need to know whether we're doing the right things technically" — fractional CTO.
If the answer is all three — you need a fractional senior layer overseeing a mix of freelancers and/or an agency on execution. Which is actually the most common answer for growing eCommerce operations.