A fractional chief technology officer (CTO) is a part-time technology leader: a senior person who makes and owns your technology decisions for a few hours or days a month, without the salary of a full-time hire. A development partner is the team that builds what's been decided and looks after it. Most small businesses need a development partner all the time and CTO-level judgment only in bursts, when there's a decision they can't judge on their own. So if your project is scoped and you trust the people building it, you likely don't need a fractional CTO at all.
We do both kinds of work, advising and building, so we see the question from both sides. Nearly every guide on it is written for venture-backed startups. This one is for an established business, say a law practice or a flooring store, that's trying to work out who should decide what gets built, and who should build it.
What does a fractional CTO do?
A fractional CTO makes the technology decisions a business would otherwise make by guesswork: what to build and in what order, which platform and vendors to use, whether to fix a system or replace it, and when to hire. They work part-time, often for several companies, and they answer for those decisions. Most don't build the product themselves.
You'll also see the role sold as a part-time CTO or a virtual CTO, and some agencies call it CTO as a service. They're pretty much the same thing under different names, though "virtual" often means the work happens remotely. An interim CTO is a different arrangement: a full-time stand-in for a set period, typically while a company looks for a permanent one. The difference from a full-time CTO is mostly availability, since you get the same kind of person for part of the week, not someone in the building every day.
For a small or mid-sized business, the work tends to fall into a few areas:
- Technology strategy and a technology roadmap. What the business should build or buy over the next year or two, and what can safely wait.
- Vendor selection and vendor management. Reading quotes, choosing a development agency or a platform, and then keeping an eye on whether the work is going where it should.
- Architecture. How your systems fit together, where the data lives, what it all costs to run, and how much technical debt (old shortcuts that make every later change slower) you're carrying.
- Technical hiring. When you're ready for developers of your own, writing the job descriptions and sitting in on the interviews.
What a development partner does instead
A development partner builds what's been decided, then keeps it running. A good one gives advice as it goes, and will push back on an idea it thinks is a mistake, though what it's accountable for is the delivered work: the site or app running properly, on time and within the agreed scope.
That's most of what we do day to day on web application projects. Once the decision is made and the scope is clear, a business mostly needs people who can build the thing well and keep it running, and another layer of management on top rarely helps.
The two roles blur because good partners do advise. The difference is in what each one is on the hook for. Your developers are on the hook for the app working. Whether it was the right app to build in the first place, and at a fair price, is a different question, and that one belongs to the CTO.
Do you need a fractional CTO or a development agency?
If the project is scoped and you trust the team building it, you need a development partner. If you're facing a decision you can't judge yet, like two quotes that are far apart or a build that has stalled, get CTO-level judgment first and build second. That's usually the moment to hire a fractional CTO, even if only for a single review.
| Where you are | What you need first |
|---|---|
| A clear, scoped project and a builder you trust | A development partner |
| Two or three quotes for the same project that are far apart | A review of the quotes before you sign |
| A build that stalled, or a codebase someone else wrote | An architecture review, then a plan |
| A platform choice that's expensive to undo (custom or off the shelf, which cloud) | A decision from someone who'll stand behind it |
| A plan to add artificial intelligence (AI) to a workflow | A decision on whether it's worth building, and on which model |
| A product with its own developers | A fractional CTO over that team |
| Technology decisions every week, not every quarter | A full-time CTO or your own technical lead |
Quotes that are far apart are pretty easy to spot, though they're also an easy place to pick wrong. The obvious move is to take the lower one, but two agencies can price "the same" app differently because they've scoped different things, and if nobody on your side can read the scopes, you end up choosing on price or on who seemed nicer in the meeting. Our post on what drives a web app's cost helps with the reading part; a fractional CTO's job is to go a step further and tell you which scope is right.
A stalled build is probably where outside judgment pays for itself fastest. We took over Stormwind Studios after another team had designed the architecture and run out of budget before it was finished, and in that situation the first question isn't who writes the next line of code, it's whether the existing design is worth finishing at all.
With an AI plan, whether an AI feature is worth building at all comes before any quote for the build. So does the model: we usually recommend Claude, though we decide case by case, and a smaller, less expensive model often does the job as well as the biggest one.
A fractional arrangement also has a natural end, since it only works while the business doesn't need a senior technical person every day. These are the signs we look for before we tell a client it's time for a full-time CTO or a technical lead of their own:
- Decisions come every day. Technical, security, architecture or vendor calls come up daily instead of weekly, and code reviews or design decisions sit waiting for someone who's only there part of the week.
- The team has grown past four or five engineers. At that size a weekly review is too slow for sprint planning, bug triage and leading people day to day.
- You ship something new every month. Releases that often need someone watching delivery and reliability all the time, not once a week.
- The software carries the revenue and the risk. Customers judge you on uptime, speed, integrations or how safely you handle their data and AI, or investors expect a permanent executive in the seat.
- Engineering has drifted from the business. Features ship without a clear link to business goals, or the systems are struggling to scale with nobody accountable for them every day.
How much does a fractional CTO cost compared with a full-time CTO?
A full-time CTO means an executive salary. The median wage for computer and information systems managers, the occupation that includes CTOs, was $175,140 a year in May 2025, according to the Bureau of Labor Statistics (BLS). A fractional CTO is paid an hourly rate or a monthly retainer instead, so the cost depends on how many hours you actually need.
That BLS figure likely understates what a CTO earns. The BLS occupation profile covers everyone from information technology (IT) managers up to CTOs, and it says senior managers like CTOs usually need many years of experience in the field before they're considered for the job, so a CTO's pay probably sits above that median. Even at the median, that's about $14,600 a month in wages alone, before benefits and the cost of recruiting someone. For comparison, the median for software developers, the people who do the building, was $135,980 in the same May 2025 data.
So the useful question is how many hours of senior judgment your business needs in a month, not the hourly rate. A company that needs one big decision a quarter and a monthly look at its agency's work needs a handful of hours. One with its own developers who need direction every week needs a lot more. Ours typically run up to 10 hours a month, built around a weekly video call, and time on site is something we agree case by case. Some are ongoing, with no set end date. Others are sized to one project and wrap up when it does.
Fractional CTO rates published online vary several-fold from one site to the next, and we wouldn't read much into any of them, because they're pricing different things. A monthly advisory call isn't the same service as two days a week of accountable leadership. That's why we estimate this kind of work from what a business needs instead of publishing a rate.
What should a fractional CTO hand you?
Written decisions you can act on. For a small business that usually means an architecture review, a review of the vendor or quotes in front of you, a roadmap with the minimum viable product (MVP) cut out of it, and a hiring plan once you're ready for a team of your own. If all you've got after three months is a calendar full of calls, something's off.
Architecture review. The Amazon Web Services (AWS) Well-Architected Framework is a good structure for one even if not everything you run is on AWS. It looks at a system through six pillars: operational excellence, security, reliability, performance efficiency, cost optimization and sustainability. AWS describes the review as a conversation about architectural decisions rather than an audit, which is the right spirit for it. The Well-Architected Tool itself is free, so what you're paying for is someone who knows which of those questions matter for a business your size.
Quote or vendor review. What each proposal actually includes and leaves out, and which of the risks stay with you.
Roadmap and MVP. A plan for the next year or two, with the first release cut down to its core. We do that cut the way our web app cost post describes, starting from the full product and working back.
Hiring plan. When the business will need developers of its own, this makes sure the first hire is someone who can work without a lead and the next ones fit around them.
This is the kind of work our consulting service covers, either as a one-off review or as an ongoing fractional CTO role.
Before anyone builds more, check you own your technology
Start by checking that the business owns what it already has. Under US copyright law, code an outside developer writes generally belongs to them (or to their agency) unless a signed written agreement transfers it to you, and custom software generally can't become a "work made for hire" just because the contract says so. Your development contract needs a written assignment of the code.
Copyright belongs first to the work's author, and a transfer of ownership is only valid in writing, signed by the owner. The U.S. Copyright Office's circular on works made for hire says a work is made for hire, and owned by the employer or the party that commissioned it, in only two situations. One is an employee creating it as part of their regular job. The other is commissioned work that falls into one of nine specific categories, such as a translation or an atlas, with a written agreement signed by both sides saying it's made for hire. Custom software usually isn't any of those nine, so for code from an agency or a freelancer, a made-for-hire clause on its own may not do what it says.
Now, owning the code doesn't help much if someone else holds the keys to the accounts. The domain registrar, the hosting, the code repositories, your analytics and your customer relationship management (CRM) system should all be in the business's name, with you holding the admin login, even if a developer has access. When a site is moving, that same inventory of accounts and access is the first step of a website migration too.
This is general information, not legal advice. Have a lawyer read your development contract, especially the parts on intellectual property (IP) and code ownership.
When one company is your adviser and your builder
It can work well, and it's common, as long as the two roles are kept apart on purpose. The adviser who can also bid for the build has an interest in the answer. So ask for the recommendation in writing before you see any build quote, and make sure you're free to take that plan to another builder.
Several of the companies ranking for "fractional CTO" also sell development, and few of them say how they handle it. We'd rather just say it: we do both, so the two have to be kept apart. When a client hires us as their fractional CTO, we tell them up front that we also build, and then the choice is theirs. We can build it, or we can find an outside development team for them to bring on board. In that case the team works for the client directly, so the relationship carries on after our engagement ends. We're happy to work either way, and that's the point: the recommendation should be something you could hand to any capable development team, and when the adviser reviews another team's code, it should be reviewed on the same terms as their own.
When you don't need a fractional CTO
A well-scoped website or web app, built by a partner who explains its decisions, doesn't need a CTO on top of it. Neither does a one-off question, such as which platform to pick or whether a quote is fair. An adviser can answer that as a one-off review, with no monthly retainer.
If you're a founder looking for a fractional CTO for a startup, it's a different case. When a founder is building a first product with no technical co-founder, the product is the technology, and nearly every early decision is a CTO decision. An established business is usually in the opposite position: the technology supports the business, and the hard decisions come along every so often.
If you're not sure which camp you're in, write down the decision you're stuck on and what it would cost to get it wrong. Then tell us about it, and we'll say plainly whether it needs a review, a build or neither.


