A fractional CTO holds the technology seat for part of the week and is accountable for the result. Founders and investors can use the sections below to decide whether that seat is the one they need.
Kompella is an AI-first fractional CTO and CPO firm. A small senior team works with healthcare, fintech, and SaaS startups from pre-seed through Series B. The prices on this page are the ones we publish for CTO time and the work that sits next to it. How the title gets stretched across the industry is covered in what fractional CTO means.
What a fractional CTO does
A fractional CTO does the CTO's job on the days they are in the company: judgment, hiring, and the calls that are expensive to reverse.
Architecture and priorities. What to build, what to buy, what to stop, and in what order. That covers the stack, the shape of the system, and a roadmap the business can fund.
The engineering team. Who to hire, what good looks like in review, and whether the team can ship when the CTO is not in the room. At 1, 2 or 3+ days a week there are not enough hours to write the product. The company's engineers, or a build partner, do that.
Vendors and partners. Cloud, tools, and agencies. The review is whether the contract, the access, and the estimate are sound, because the CTO works for the company.
The external technical story. Boards, investors, and buyers ask how the product is built, what breaks under growth, and who is accountable. The fractional CTO prepares that story and can sit in the room.
Regulated products and AI, when that is the work. In healthcare and fintech, access control, logging, and how data moves are design constraints from the first week. Where the company is adding AI, someone senior has to say what is safe to ship and what should wait. Kompella builds with AI-native engineering practices and helps clients ship AI features safely. A fixed four-week version of that work is the AI Build Sprint. When the company needs a product leader as well as a CTO, that is a separate seat: fractional CPO services.
The standing offer for the CTO seat is fractional CTO services.
When a startup needs one, and when it does not
You need a fractional CTO when technical decisions are expensive to reverse and nobody senior owns them.
- You are a non-technical founder about to sign a build contract, and nobody on your side can judge the work. Building a first product with a fractional CTO walks through that setup.
- The team ships, and architecture, hiring, and the board story have no owner.
- You are raising, and investors will ask technical questions the founding team cannot answer precisely.
- The product is in healthcare or fintech, and compliance has to be designed in from the first week.
- You are adding AI, and nobody senior owns whether the feature should exist, how it will be evaluated, or what it costs to run.
- A technical co-founder, or a full-time CTO already in the seat, is making those calls and checking the work.
- The scope is settled and you need people to build it. That is a development agency, or your own engineers. The split is in fractional CTO vs agency.
- The CTO seat is empty and someone has to own the team for most of the week until a permanent hire starts. That is interim cover. See interim CTO vs fractional CTO.
- You want a written view on one decision, and then the person is done. That is technical advisory, which is lighter than holding the CTO seat.
Fractional vs full-time vs interim vs agency
These four get confused because a company can use more than one in the same quarter. They are different purchases. The closer pairs are written up in fractional CTO vs full-time CTO and interim CTO vs fractional CTO.
| Fractional CTO | Full-time CTO | Interim CTO | Agency | |
|---|---|---|---|---|
| What you are buying | Decisions and accountability, part time | A CTO on the payroll, every day | An owner for an empty seat | People to build an agreed scope |
| Time | 1, 2 or 3+ days a week | Full time | Most of the week, until a hire starts | A project or a sprint team |
| Writes most of the code | No | No, once a team exists | No, once a team exists | Yes |
| Accountable to | You, on an ongoing basis | You, as an employee | You, for the length of the gap | The contract |
| Ends when | You hire a full-time leader, or the need passes | They leave or you replace them | The permanent CTO starts | The scope ships |
| Kompella price | $8K, $15K or $25K a month | A salary on the company's payroll | From $25K a month, or $30K for PE portfolio companies | Our MVP build: 8 to 12 weeks, scoped and quoted on a call, separate from CTO time |
What it costs
CTO time at Kompella is one of three monthly amounts. It is not a band you negotiate into a fourth number.
| What | Price | Time |
|---|---|---|
| CTO time, Advisory | $8K a month | 1 day a week |
| CTO time, Fractional | $15K a month | 2 days a week |
| CTO time, Embedded | $25K a month | 3+ days a week |
| Interim cover | From $25K a month | An empty CTO seat. $30K a month for PE portfolio companies |
| Technical due diligence | $15K to $75K | 2 to 8 weeks |
| MVP build | Scoped and quoted on a call | 8 to 12 weeks |
| AI Build Sprint | Scoped and quoted on a call | 4 weeks |
The detail lives on fractional CTO services, technical due diligence, MVP builds, and the AI Build Sprint.
Need help thinking this through? Book a 30-min call, no pitch. Book a Free 30-Min Strategy Call →
How engagements work
A fractional CTO engagement at Kompella follows five steps. The same steps are on the fractional CTO service page and, in shorter form, on how we work.
- Discovery call. Thirty minutes on stage, team, and what success looks like. You leave with three specific recommendations whether or not we work together.
- Stack audit. A two-week review of architecture, the codebase, infrastructure cost, hiring, and risk. You get a written report with actions in priority order.
- 90-day plan. A working session before the retainer starts. We agree three measurable outcomes, the sequence of work, and what will count as success.
- Embedded execution. 1, 2 or 3+ days a week in the leadership team: standups, code review, hiring, and board prep. Month to month, with 30 days' notice.
- Hiring and transition. When the team can run, we help you hire a full-time CTO or a VP of Engineering and step back. The engagement is designed to end.
How to choose one
Use this list with us and with anyone else you talk to.
- You meet the people who will do the work. Kompella is a small senior team. You should know who is on the engagement before you sign, rather than being assigned a name afterward.
- The experience matches the company. Healthcare, fintech, or SaaS, and a stage from pre-seed through Series B. A regulated product needs someone who has shipped inside that kind of constraint.
- Accountability is written down. Who signs off on architecture, who owns hiring, and who answers to the board when something technical fails. If none of that is in the agreement, the relationship is advisory.
- The price is the published price. You should see $8K, $15K or $25K a month before anyone asks you for a proposal.
- Leadership and building are separate lines. You can stop one without the other. Fractional CTO vs agency covers how to set that up, including when both are the right buy.
- They are paid by you. If a CTO earns a fee from the agency they recommend, the recommendation is no longer independent.
A fractional CTO is the right seat when the next technical decision is expensive and nobody in the company can own it. It is the wrong retainer when that person is already there, when the seat is empty and needs someone most of the week, or when the only gap is people to write code.
If you want a direct view on which of those you are in, book a 30-min call. We will say so if a fractional CTO is the wrong shape.

