What a Fractional CTO Does for a Small Company

The Short Answer

A fractional CTO is a senior technology leader who works for your company part time, on a standing arrangement rather than a single project, and owns the technical decisions a small company cannot afford to get wrong: architecture, build versus buy, vendor and hiring choices, security basics, and the roadmap that ties them to the business plan. Fractional CTO services make sense when technical decisions arrive faster than anyone in the company can judge them, but there is not yet enough work, or budget, for a full-time executive. A good one leaves you faster at deciding and less dependent on any single person, including them.

I sell this service myself, so weigh what follows with that in mind. It is written to be just as useful if you hire someone else, or nobody yet.

What "Fractional CTO" Actually Means

"Fractional" means you buy a share of a role, not a block of hours. The person carries the responsibilities of a chief technology officer, so they are accountable for technical direction, but they spread their working time across a small number of companies. That accountability is what separates the role from the people it is usually confused with.

• Fractional CTO. Works for you, for a fixed slice of time each month, and is accountable for technical direction across the company. Best when decisions outpace your expertise but the work is not yet full-time. Main risk: becoming a bottleneck, or a part-time opinion.
• Full-time CTO. Works for you with all of their time, accountable for technical direction and the team. Best when the team and product need daily leadership. Main risk: under-used and expensive at small scale.
• Project consultant. Works for you on one deliverable, until the project ends. Best when you need one question answered well. Main risk: leaving before the consequences show.
• Agency tech lead. Works for the agency, accountable for delivering the agency's scope. Best when you have bought a build and need it delivered. Main risk: recommending what the agency sells.

The last of these matters more than it looks. An agency's technical lead can be excellent, but their job is to deliver their employer's contract. A fractional CTO sits on your side of the table: reading that contract, questioning that estimate, and deciding whether that agency is the right one at all.

What the Role Owns at a Small Company

At a small company, often one without an engineering team of its own, the job is less about managing engineers and more about making, recording and defending a handful of decisions that are expensive to reverse. In practice it covers eight areas.

1. Turning the business plan into a technology roadmap

The roadmap answers what gets built, bought or configured, in what order, and, just as important, what does not get built this year. Without one, technical work follows whoever asked last and loudest.

2. Making architecture decisions and writing them down

Which systems hold which data, how they talk to each other, and where the single source of truth for customers, stock and money lives. Each significant decision belongs in a short decision note: the problem, the options considered, the choice and the reason. A decision that only exists in someone's head gets argued again every time a new person joins.

3. Build, buy or configure

In my view, small companies waste more money building what they could have bought than in any other way. My default order is: configure a standard product first, extend it with a maintained module or integration second, and write custom code only where the process is a genuine differentiator. Part of a fractional CTO's job is to hold that line when a developer or vendor finds custom work more interesting.

4. Choosing vendors and holding them to account

ERP, hosting, agencies, SaaS tools. That means comparing proposals on total cost and exit cost rather than day rate, checking that estimates come from discovery rather than guesswork, and reading contracts for who owns the code, the data and the accounts. If an ERP selection is on your list, my ERP comparison sets out the criteria I would start from.

5. Hiring, including their own replacement

Writing the first engineering job specifications, running technical interviews, onboarding the first hires and, eventually, helping recruit a full-time technical leader. A fractional CTO who is not working towards making the role either unnecessary or full-time is building dependence.

6. Security, access and continuity

This is the least glamorous part and often the most urgent. Who owns the domain, the cloud account, the code repository, the app-store listings and the payment gateway? Are they registered to the company, or to a person: a founder's personal email, an employee who has since left, an agency? Do backups exist, and has anyone actually restored one? The first weeks of an engagement should produce a plain list of these answers and a plan to close the gaps.

7. How changes reach production

Code review, a staging environment, a repeatable deploy and a way to roll back. You do not need a heavy process, but you need one that does not depend on a single careful person. The DORA software delivery metrics (checked 13 October 2026) are a sensible yardstick: change lead time, deployment frequency and failed deployment recovery time for throughput; change fail rate and deployment rework rate for instability. Even a rough baseline tells you whether things are getting better or worse.

8. Translating between technology and the business

Explaining technical risk to an owner or board in terms of money and time, answering a security questionnaire from an investor or a large customer, and preparing the technical side of due diligence.

What a Fractional CTO Is Not

• Not a cheap senior developer. If most of their time goes into writing code, nobody is doing the CTO part.
• Not a project manager. They should set direction and check delivery, not chase tickets.
• Not a rubber stamp. If you have already made the decision and only want it confirmed, save the fee.
• Not a permanent fixture by design. The healthiest engagements end in a full-time hire, a stable system that needs little attention, or a smaller retainer.

Signs You Need One, and Signs You Don't

You probably need one if two or more of these are true:

• You are about to sign a large technology contract, such as an ERP implementation, a platform rebuild or a long agency retainer, and nobody inside the company can judge the proposal.
• Your developers or your agency keep asking you to make technical decisions you cannot evaluate.
• Releases slip, estimates are routinely wrong, or each release breaks something that used to work.
• One person, inside or outside the company, holds most of the access and most of the knowledge.
• Investors, acquirers or large customers are asking architecture or security questions you cannot answer.
• You are about to hire your first engineers and do not know how to assess them.

You probably do not need one if:

• You need one decision, once. A defined question (which platform, whether an architecture will hold up, whether a vendor proposal is sound) is better served by a one-off architecture review than by a monthly retainer.
• You need building capacity, not judgment. Hire a developer or an agency, and pay for an independent review at the milestones that matter.
• Your systems are standard, working, and nothing significant is planned. Configured off-the-shelf software with no integrations and no roadmap rarely needs a CTO of any kind.
• Nobody with authority will make time for it. The role fails if the person who signs the contracts will not meet the CTO regularly and act on what they hear.

Fractional or Full-Time: The Cost Question

A full-time CTO is a large fixed commitment for a small company. The US Bureau of Labor Statistics puts the median annual wage for computer and information systems managers, the occupation that includes the CTO title, at $175,140 in May 2025 (BLS Occupational Outlook Handbook). Wages are not the whole cost of an employee either: across US private industry, wages and salaries made up 70.0 percent of employer compensation costs in June 2026, and benefits the remaining 30.0 percent (BLS Employer Costs for Employee Compensation); both BLS pages were checked on 13 October 2026. Recruiting time, equity and the risk of a wrong hire come on top.

The bigger question is not the salary but utilization. My opinion is that most small companies do not have a full-time CTO's worth of decisions every week. What they have is a few expensive decisions a quarter, some hiring, a vendor or two to manage and a backlog of hygiene. A fractional arrangement lets you pay for judgment roughly in proportion to how many decisions you are actually making. What my own engagement includes, and how it starts, is on the fractional CTO service page.

Fractional stops making sense when:

• the engineering team has grown to the point that it needs daily leadership, one-to-ones and career management;
• technology is the product, and the CTO's judgment is the competitive edge;
• the fractional CTO keeps becoming the bottleneck because there is more work than their slice of time.

At that point the right move is a full-time hire, and a good fractional CTO will tell you so and help run the search.

How to Scope a Fractional CTO Engagement

1. Name the decisions and problems for the next 90 days. Three is a good number. "Choose and contract the ERP vendor", "move every company account out of personal ownership" and "hire the first two developers" are scopes; "help with tech" is not.
2. Agree the time slice and the cadence. A standing weekly call plus asynchronous access is a common shape. Write down how quickly questions get answered and what counts as urgent.
3. Define authority. What can they decide alone, what do they recommend, and what needs the owner's sign-off? Vendor signatures and spending should normally stay with you.
4. Give access on day one, through company-owned accounts. Read access to code, cloud, analytics and vendor contracts. A CTO who has to ask for every login spends the first month waiting.
5. Put the deliverables in writing. A decision log, a short roadmap, a risk and access register, and, if hiring is in scope, job specifications and an interview plan.
6. Plan the exit at the start. Everything they produce lives in your systems, nothing is registered to them, and there is a handover if the engagement ends.
7. Review at 90 days against the decisions you named in step one.

What the First 90 Days Should Produce

A reasonable target for the first 90 days, whoever you hire:

• By the end of week 2: an inventory of systems, vendors, accounts and recurring technology costs; who has access to what; the top risks, in plain language.
• By the end of week 6: the most urgent decisions made and recorded; access and backup gaps closed or scheduled; a baseline of how changes reach production.
• By the end of week 12: a roadmap for the next few quarters; a hiring or vendor plan; a written view on whether the arrangement should continue, change size or become a full-time hire.

Warning Signs It Isn't Working

• Everything waits for their weekly call. A fractional CTO should make the team faster between meetings, not slower.
• Decisions are not written down. If you cannot find why something was decided, it was not really decided.
• Their recommendations always point to the same vendor or stack. Ask directly whether they receive referral fees, resell anything, or would bid for the build work themselves.
• They write the critical code and nobody else understands it. That is a new single point of failure with a better title.
• Ninety days in, nothing you named at the start has changed. Either the scope was wrong or the fit is.

The conflict-of-interest point applies to me too. I also sell implementation and integration work, so if you ask me to judge a build that my own team could bid for, hold me to the same rule: ask me to declare it up front, and get a competing quote. Keep the advice separate from the sale and you can trust it.

Questions to Ask Before You Hire One

• Which decisions will you own, and which will you hand back to us?
• How will we both know, in 90 days, that this is working?
• Do you earn anything from the products, vendors or agencies you might recommend?
• What happens to documentation, access and work in progress if we stop?
• At what point would you tell us to hire a full-time CTO instead?
• What would you push back on in the way we run technology today?

Frequently Asked Questions

What is a fractional CTO?

A fractional CTO is a part-time chief technology officer: a senior technologist who takes on the responsibilities of a CTO for a share of their working time, usually on a monthly retainer, and divides the rest among a small number of other companies. Unlike a project consultant, they are accountable for technical direction across the whole company for as long as the engagement runs.

How is a fractional CTO different from a technology consultant?

A consultant delivers a defined outcome and leaves; an advisor offers opinions without owning the result. A fractional CTO owns ongoing technical decisions and stays long enough to see whether they worked.

How much time does a fractional CTO spend with a company?

It depends on scope, not on any standard. Agree it in terms of the decisions you need made and a fixed cadence, such as a weekly call plus asynchronous access. If the time needed keeps growing, consider a full-time hire.

Should a small company hire a fractional or a full-time CTO?

Fractional, while technical decisions are few but expensive and technology supports the business rather than being the product. Full-time, once the team needs daily leadership or the technology itself is the competitive edge.

Can a fractional CTO also write code?

Yes, and some hands-on work, such as a prototype, a review or a hard integration, keeps their judgment grounded. But if coding takes most of their time, the leadership is not being done. Pay a developer to build and the CTO to decide.

---

Weighing a fractional CTO against a full-time hire, or not sure you need either? See how my fractional CTO engagement works or send me the details and ask whether a one-off review, or nothing at all, would be the better fit.