--- title: "Hire a fractional CTO: what it covers, how it works, what it costs" description: "What a fractional CTO actually does, how an engagement is scoped, and what it costs. Part-time technical leadership for early-stage founders, a few days a month, with no lock-in." url: https://www.88mph.tech/fractional-cto/ last_modified: 2026-08-14 --- Fractional CTO ## Someone who owns the technical decisions, a few days a month. You do not need a full-time CTO yet. You do need someone experienced who is answerable for the technology choices your company is making right now. [Book a free 30-min call](https://www.88mph.tech/call/) [See what it covers](#what-it-covers) - Pre-seed to Series A - Flexible retainer - Remote, from London Decisions I would own with you - What gets built, and what does not - Whether the work is any good - Which suppliers to trust - Who to hire, and when - Whether it holds up at real volume ### Working with a fractional CTO For most early-stage companies the problem is not a shortage of people who can write code. Developers and agencies are straightforward to find and to pay for. The problem is that a non-technical founder has no reliable way to judge whether the right things are being built, whether the work coming back is good, and whether the money going out is buying anything durable. Those questions need someone with enough experience to answer them, and enough distance from the building to answer them honestly. The arrangement suits companies between pre-seed and Series A: far enough along that real technical decisions are being made, not yet large enough that a full-time technology leader is justified. [New to the term? Read what a fractional CTO is, what they do, and what it costs](https://www.88mph.tech/guides/what-is-a-fractional-cto/) What it covers ### The decisions you should not be making alone Not extra hands to write code. Judgment on the calls that are expensive to get wrong, and someone answerable for them afterwards. #### Direction What to build first and what to leave out, how the product should be put together, and whether today's choices still work when the business changes. The scope is set by what you are trying to learn, not by a feature list. #### Oversight of the work An independent read on whether your developers or agency are doing good work, whether a milestone is genuinely done, and whether an estimate is reasonable. You get an honest answer from someone who is not the one building it. #### Suppliers and tools Choosing between building, buying, and assembling what already exists, reviewing contracts and quotes before you sign, and making sure you own what you paid for. #### Team When to make your first engineering hire, how to run a process that reveals judgment rather than trivia, and how to keep the work accountable once someone is in the seat. How it works ### Light to start, easy to change An ongoing partnership rather than a one-off report, sized to what you actually need right now. 1 #### A free 30-minute call We talk through where you are and the decisions in front of you. If a fractional CTO is not what you need, I will tell you that on the call. 2 #### A scope that fits A flexible monthly retainer, typically a few days a month, matched to the decisions actually coming up. It moves up or down as things change. 3 #### We work I stay close enough to steer the calls that matter, review the work honestly, and be there when something needs deciding. You are never deciding alone. ### What a fractional CTO costs Engagements run on a monthly retainer, sized to the number of days you need. For most early-stage companies that is somewhere between two and six days a month. The figure is agreed before anything starts, so you know what you are committing to, and it moves up or down as the work in front of you changes. The comparison worth making is not against a developer's day rate. It is against the cost of a full-time technology leader, which in the UK means a salary well into six figures once you add employer national insurance, pension, equity and recruitment fees. A fractional arrangement gives you the same standard of decision-making for a small fraction of that, because you are paying for a small fraction of the week. The other comparison, harder to put a number on but usually larger, is the cost of the decisions themselves. Rebuilding a product that was put together without a plan, paying for a system nobody can maintain, or spending nine months on a first version that could have been three, all cost considerably more than the retainer that would have prevented them. For the market rates, how the pricing models differ, and the questions to ask before agreeing a price, read the guide: [How much does a fractional CTO cost?](https://www.88mph.tech/guides/fractional-cto-cost/) How the pricing works ### Priced on the work, not on hours logged You are paying for judgment on a set of decisions, not for time recorded against a timesheet. The scope is what we agree the work is, and the fee follows from that. - **Agreed up front.** You know the number and the scope before we start. - **No lock-in.** Month to month. If it stops being worth it, you stop. - **Judged on decisions, not activity.** The point is the calls that get made well and the mistakes that do not happen. ### How this compares to the alternatives Several arrangements sound similar and are often used interchangeably, which makes it hard to work out what you are actually being offered. The differences matter, because they change who is accountable and for how long. ArrangementTimeBest when **Fractional CTO** Part-time, ongoing You have never had a CTO, real technical decisions are being made, and a full-time hire is not yet justified. **Interim CTO** Full-time, fixed period A technology leader has left and the role cannot sit empty while you recruit a permanent replacement. **Technical advisor** A few hours a month You want someone to talk things through with, and you are comfortable owning the decisions and the follow-through yourself. **Development agency** Project based You know what needs building and you need the capacity to build it. Note that the agency is not independent of its own work. **Technical co-founder** Full-time, permanent You have found someone who believes in the idea enough to take equity instead of salary, and you want them there for the long term. The distinction that matters most is between advice and accountability. An advisor gives you an opinion and leaves the decision with you. A fractional CTO makes the call with you and is answerable for how it turns out, which is the part most non-technical founders are actually missing. On fit ### What your situation actually calls for Most pages like this one say the answer is always yes. What genuinely helps depends on where you are right now, and sometimes the useful thing I can do is point you at something else. **You are still working out whether anyone wants it.** Getting to a clear view of the problem before anyone writes code is part of the work, and usually the cheapest part of it. **What you need is more hands to build.** That is a developer or an agency. I can help you choose one, read the quotes before you sign, and judge the work once it starts. **You need deep expertise in one narrow area.** A specialist will serve you better there. I can help you work out what to ask for, and whether the answer you get is any good. **You already have a technical leader the team trusts.** Bringing in a second senior voice can undermine the first. It works well when that person wants it: someone to mentor them, or to help them navigate a project or a growing team for a while. Worth deciding together with them. Questions ### Questions founders ask before starting What is the difference between a fractional CTO and an interim CTO? An interim CTO fills a role that already exists, usually full-time and for a fixed period, while you look for a permanent hire. A fractional CTO works with you part-time on an ongoing basis, and the arrangement is designed to continue rather than to end when a replacement is found. If you have never had a CTO and are not ready to hire one, fractional is usually the better fit. If someone has just left a full-time role and the work cannot pause, that is an interim job. How many days a month does a fractional CTO work? Most early-stage engagements land somewhere between two and six days a month. What matters more than the number is when those days fall. Being available in the week a supplier contract needs reviewing is worth more than a fixed day every Monday. Scope is agreed up front and can move as the decisions in front of you change. Do I need to give a fractional CTO equity? No. The arrangement is a monthly fee, so you keep your equity for the people who will be with you full-time. Some founders prefer to add a small equity component for alignment on a longer engagement, and that is a conversation worth having, but it is never a condition of starting. Can a fractional CTO work with the developers or agency I already have? Yes, and this is one of the most common reasons founders get in touch. Your developers keep building. What changes is that someone experienced is reviewing the work, questioning estimates, and making sure the direction still serves the business. Good agencies tend to welcome it, because clear decisions and quick answers make their job easier too. Can a fractional CTO help me hire my first developer? Yes. Writing the role, sifting applications, running the technical part of the interview, and judging whether someone is actually as strong as they present are all part of the work. Hiring your first engineer is one of the most expensive decisions to get wrong when you cannot assess the skill yourself, so it is worth having someone who can. What happens when the company outgrows a fractional CTO? That is the intended outcome. As the team grows, the right answer becomes a full-time technology leader, and part of the work is recognising when that point arrives and helping you hire the person. A good fractional engagement should leave you with clear documentation, a team that knows how it works, and a handover that does not lose momentum. How quickly can we start? Usually within a week or two of the first call. There is no long onboarding, because the first thing that happens is a conversation about the decisions already in front of you rather than a discovery project. Start here ### Let's find out what your product actually needs Book a free 30-minute call. We'll talk through where you are, what to build next, and whether working together makes sense. No pressure, no jargon. [Book a free 30-min call](https://www.88mph.tech/call/) [Email me instead](mailto:federico@88mph.tech)