DenyaDev / Handbook

Working with a fractional CTO: a handbook for founders

What the role covers, what it costs, how to choose one, and how engagements are set up and end.

By Paul Denya · Updated October 2026

A fractional CTO is a senior engineer or technology leader who owns a company's technical decisions part-time, on an ongoing basis. Most work one to three days a week and are paid monthly.

A fractional CTO owns technical decisions part-time

The role comes from the broader idea of the fractional executive: a senior leader who works for a company part-time or on contract and takes real ownership of an area. For a CTO, that area is technology. Typical responsibilities are setting technical direction, making architecture and build-vs-buy decisions, overseeing security and infrastructure, and speaking for engineering in leadership conversations.

In practice the job at a small company is usually a mix of deciding and doing. Someone has to choose the stack, review what ships, deal with vendors and hosting, and often write a meaningful share of the code.

Interim CTOs, advisors and agencies cover different needs

The titles overlap, and the useful distinctions are time, length and what the person owns.

RoleTimeLengthOwns
Fractional CTO1–3 days a weekOngoingTechnical decisions, and often part of the build
Interim CTOFull-time3–12 monthsThe whole function while a permanent CTO is hired
Technical advisorA few hours a monthOpen-endedAdvice; decisions stay with the team
Agency or freelancerVariesPer projectDelivering a defined scope
Full-time CTOFull-timePermanentTechnology, the team and its growth

Most engagements start with a specific problem

Engagements usually start from a specific situation:

  • No technical co-founder. The company needs someone to own infrastructure, auth and data decisions.
  • First engineering hires. The company wants help defining roles, running technical interviews and evaluating candidates.
  • An agency or developer is leaving. Someone has to take over the code, the servers and the accounts.
  • An MVP has been outgrown. A product built with no-code tools, freelancers or AI coding tools has traction and is ready for a sturdier foundation.
  • An inherited codebase. The product works, and the team wants an independent read on its condition.
  • Investor diligence. A fundraise brings technical questions that benefit from a senior answer.

When the people who built the product leave, secure access and ownership first

An agency contract ends, a freelancer moves on, an offshore team stops answering, or a co-founder CTO leaves with the team. The first steps are the same each time. Not knowing who holds each login is normal after a departure; finding out is week-one work.

  1. Recover every admin account. Code hosting, cloud hosting, the domain registrar and DNS (the settings that point the domain at the site and email), company email, app stores, and payment and API services. Remove everyone who left and change the passwords and keys they knew. Anyone with admin access can still change or delete things, and investors will ask whether the company controls its own systems.
  2. Copy code and data. Repositories, the production database and uploaded files go into storage in the company's name, so a billing dispute or lapsed account can't take the product with it.
  3. Confirm the company owns the work. Counsel checks for a signed invention assignment, a contract transferring what someone builds to the company, from every employee and contractor who wrote code. Under US copyright law, code a contractor writes generally stays the contractor's unless a signed agreement transfers it (U.S. Copyright Office). Investors ask who owns the code, and gaps are easier to close while the authors are reachable.
  4. List what's been promised. Customer deadlines, pilots, open security questionnaires, investor follow-ups. Each needs a new owner, and some need a revised date.
  5. Pause unchecked claims. Performance numbers and security or compliance statements wait until someone has checked them against the product, since customers and investors may ask for a demonstration.
  6. Pay for handover time. A few weeks of hourly help from the people who left is usually the cheapest knowledge transfer available. Ask early, while the details are fresh.
  7. Test a fresh build. Someone new should be able to build, run and deploy the product from a clean copy, without its authors. The result sets what can ship and what needs rework.

Engagements usually come in three shapes

A fixed-price assessment or plan

One to four weeks. The fractional CTO reads the code, checks infrastructure and access, and writes up what they found and what to do next. Many practitioners credit the fee toward later work. Technical due diligence for investors is a more formal version of the same review.

An advisory retainer

A fixed number of hours a month for decisions, code review, hiring and vendor oversight. The team does most of the building.

An embedded or hands-on retainer

More time, often two or three days a week, and part of the build. This is the most common shape at very small companies where there is no team yet to direct.

Specialists handle the deep work, under contracts the company holds

A fractional CTO is a senior generalist. Some work needs credentials, tools or depth in one field, and companies usually contract it separately:

  • Security testing. In a penetration test, outside assessors try to get past a system's security under agreed limits (NIST). Security firms run these tests and formal security audits.
  • The SOC 2 audit. SOC 2 is the AICPA's standard for reporting on a company's security and privacy controls, and CPA firms issue the reports (AICPA). The fractional CTO can own readiness: closing gaps, writing policies and gathering evidence before the auditor starts.
  • Deep technical specialties. Machine learning research, specialized mobile work and hardware.
  • Legal questions. Who owns the code and other IP, and how customer data may be used, are questions for company counsel.

The fractional CTO runs the process: scopes the work, finds candidates, writes the brief, reviews what comes back and holds the specialist to the brief. That ties the findings to the company's real decisions, such as which security issues to fix before a launch.

Contracts in the company's name. Specialist firms should be hired and paid by the company directly. If the fractional engagement ends, the company keeps the relationship, the reports and the work product. A fractional CTO who earns nothing from a specialist's hours also has no reason to add more of them.

Experts on hiring panels. When the company hires for a specialty the fractional CTO can't evaluate in depth, a domain expert can join the interview panel, paid for each round of interviews. The fractional CTO still runs the process and judges general engineering ability.

An advisor for depth. For recurring questions in one field, a part-time advisor who works in that specialty gives the company and the fractional CTO someone to check decisions against.

Most US fees run $4,000–$25,000 a month, and some costs sit outside the fee

Published asking prices from US practitioners mostly run from about $4,000 a month for light advisory work to about $25,000 a month for two to three days a week. Hourly rates in the middle of the market sit around $170–$250. These are asking prices; few sources report what companies actually paid.

Lighter arrangements, such as hosting plus occasional advice, can run a few hundred dollars a month.

A full-time CTO salary is the usual point of comparison. It also helps to compare the fee against the specific problem it addresses: what a launch that slips a quarter, an engineering hire who doesn't work out, or a rewrite would cost the company.

Budget separately for work outside the fee

  • Specialists. Security testers, auditors and other specialist firms, usually hired and paid by the company directly. The fractional CTO scopes and reviews their work.
  • Recruiting fees. If an agency fills an engineering role, contingency recruiters typically charge 15–25% of the hire's first-year salary (First Round Review).
  • Legal counsel. A startup lawyer to confirm the company owns its code, review contractor IP agreements and handle any equity grants.
  • Handover help. A departed developer or agency may agree to a few paid hours to walk through the code, servers and accounts. Expect to pay their usual rate.
  • Hosting and tools. Cloud hosting, domains, app store accounts and paid services, billed to the company directly or included in a hosting arrangement.

Payment is usually cash, invoiced in advance

  • Assessments. A fixed fee, paid up front and often credited toward later work if the engagement continues.
  • Ongoing work. A monthly or four-week fee invoiced in advance, usually month to month with a notice period, commonly 30 days. Some practitioners ask for a three-month minimum.
  • Fixed-scope builds. Paid by milestone, with each payment tied to an agreed piece of delivered work.

Cash is the norm. Some fractional CTOs accept a small equity grant on top of cash, and equity-only arrangements are rare.

Choose on fit, references and written work, then start with a small paid scope

Fractional CTOs vary more than the title suggests. Some mostly advise and some mostly build, and backgrounds range from startup engineering to enterprise IT. These checks help before signing:

  • The right mix. A company with no engineers needs someone who writes and ships code. A company with a team needs someone who reviews, directs and hires. Ask how their time usually splits between the two.
  • A similar situation. Taking over from a departed agency, hiring a first team and preparing for diligence are different jobs. Ask for an example of the one that matches, and what its first month produced.
  • References with an ending. Talk to two founders they've worked with, ideally one whose engagement has finished. Ask how reachable they were, what changed, and how the handover went.
  • A sample of written work. An anonymized assessment, plan or decision memo. A part-time leader works largely through writing, and a sample shows how clearly they explain tradeoffs to someone outside engineering.
  • A small first step. A fixed-scope assessment of one to four weeks lets both sides judge the work before a retainer. A long retainer proposed before anyone has looked at the code skips that check.
  • Disclosed incentives. If they also supply developers, resell services or receive referral fees from vendors, ask for the arrangement and the rates in writing, so spending decisions can be judged on their merits.
  • Availability in writing. Days per week, response time between calls, and who covers when they're away.

Questions for the first call

  • What will the first month produce, in writing?
  • How much of the work will you build yourself, and how much will you review?
  • Who will own the code, accounts and contracts, and when do they move to the company?
  • Do you bring in other developers or vendors, and how are they paid?
  • How do we reach you between scheduled calls?
  • How will we know it's working after 90 days?
  • What does the handover look like when the engagement ends?

Set up ownership and decision rights before work starts

  • Who holds each account. Write down which accounts the company holds and which the fractional CTO or a hosting provider runs for it, across code repositories, cloud hosting, domains, app store accounts and third-party services. For each account the company doesn't hold, agree how it would move over if the engagement ends: the notice period, who pays for the transfer, and the form the code and data come back in.
  • Decision rights in writing. Agree on what the fractional CTO can approve alone and what needs sign-off, such as spending, hiring and vendor contracts.
  • IP terms. Work product belongs to the client; tools and methods the fractional brought with them usually stay theirs.
  • Security accountability. A fractional CTO does the security work, but company leadership remains accountable for the risk.
  • A regular cadence. A standing weekly call and a written update each month keep a part-time role from drifting.

You don't need answers before the first call

The first call doesn't require knowing who holds each login, how the system is built, or what it costs to run. After a developer or agency leaves, those answers are usually spread across old emails, invoices and a former developer's laptop. Gathering them is the first week's work.

If any of these are easy to find, they help:

  • Paid tools and services. A list of what the company pays for. A card statement works.
  • Recent developers. Who last worked on the code, and how to reach them.
  • Dated promises. Anything promised to customers or investors, with the date it's due.
  • Existing documents. Contracts with developers or agencies, and any docs, diagrams or notes.

Finding the rest is part of the first two weeks of work.

Expect a written assessment by the end of the first month

WhenGoalWhat should be done
Days 1–10Take controlAdmin access to the code, hosting, domains, email and every paid service, in the company's name. Anyone who left can no longer get in. Backups exist, and one has been restored to prove it works.
Days 11–30Understand what existsBuild the product from a fresh copy of the code on a new machine. Follow how a change reaches customers. List monthly costs, risks, and commitments already made.
Day 30Written assessmentThe memo below, walked through on a call.

Control comes first because investors and customer security questionnaires ask about it: who owns the code, and who can get into the systems. The company's own access is confirmed before anyone else's is removed.

A useful assessment answers nine questions

  1. What exists. Each app, site and service, and where it runs.
  2. Who controls what. The owner and admins of each account, and whether anyone who left still has access.
  3. Build and deploy. Whether a fresh copy of the code builds, and how a fix gets to customers.
  4. Monthly cost. What each service costs, and what can be cut.
  5. Fine, fragile, urgent. Every finding, sorted by how soon it needs attention.
  6. What can be said. Which claims about the product hold up today, and whether existing commitments can be met on their dates.
  7. The next 90 days. The work in priority order, with a rough size for each item.
  8. Hiring. Whether the company needs to hire, for which role, and when.
  9. Decisions needed. Questions only the founder can answer, each with options, costs and a recommendation.

The clearest memos state each finding in its heading, such as "Backups run nightly but have never been restored."

If the engagement includes building, ask for something small to ship in the first month through the real deploy path. That tests the deploy path and the working relationship at the same time.

Ask for a written recap after every call

A few lines covering what was discussed, what was decided, and the next step with a date. A co-founder, board member or new hire can then catch up without another meeting, and a part-time engagement that starts to drift shows it in the recaps.

The first engineering hire sets the standard for the rest

Small companies usually hire in the same order. First comes a founding engineer or engineering lead who owns delivery day to day: shipping, reviewing code and keeping the product running. More engineers follow once that person has a process to bring them into, and specialists come when a need outlasts the generalists.

The first hire matters most because they choose the tools and habits every later engineer inherits, and they usually interview the next few people. When an agency or contractor is leaving, the takeover tends to come first, so the new hire joins a codebase someone already understands.

A fractional CTO typically runs the technical side of the search:

  • The role. A written description of what the person will own.
  • Pay. A salary and equity range set from market data.
  • Sourcing. Referrals, job boards and direct outreach.
  • Technical evaluation. Interviews, a short practical exercise close to the real work, and reference calls that test the candidate's technical claims.
  • A recommendation. A written view on each finalist, with reasons and risks.

The founder makes the call and owns the relationship with the new hire.

What founders judge. How clearly a candidate explains past work to someone outside engineering, whether they describe outcomes they owned, how they reason through a tradeoff such as speed against polish, and whether the founder wants to work with them every day. The technical interviewer judges the code and whether the stated experience holds up.

Plan for months. In data from 93,000 jobs at companies using its hiring software (January 2021 to March 2026), Ashby found a median of 75 days from opening a technical role to the first hire, against 60 for business roles (Ashby). Companies under 25 people varied the most.

Checking pay directly. The median annual wage for US software developers was $135,980 in May 2025 (BLS). For startup ranges, Carta reports salary and equity by company stage, Pave offers free salary and equity benchmarks, and Levels.fyi collects self-reported pay that leans toward large tech companies.

A permanent technical leader usually comes later

A full-time CTO or VP of Engineering usually makes sense once a company has around 15 or more developers, is at Series B or later, or sells a product where the technology is the main advantage (Stephan Schmidt). A technical co-founder is a separate decision about ownership: significant equity for a long-term partner in running the company.

The fractional CTO runs that search the same way. The handover covers documented systems and past decisions, a few weeks of overlap with the new leader, and moving over any accounts the fractional CTO runs that the new leader should hold. The engagement then ends or narrows to hosting and occasional advice.

Investors look for a plan to hire permanent technical leadership

Many early-stage investors prefer a technical founder. Y Combinator's Dalton Caldwell writes that "companies lacking a technical co-founder underperform," and rejects the idea that part-time consultants or dev shops can stand in for one (Y Combinator). Some founders raising without one report being told investors want a CTO in place.

A fractional CTO fits that picture as a bridge to a permanent hire, so investors evaluate the current arrangement together with the plan to replace it.

  • Accurate titles. In investor materials and on the website, list a part-time technical leader as "Fractional CTO" or "Technical advisor," with their firm's name. Investors talk to the team during diligence, so an overstated role is likely to surface.
  • The hiring plan. Name the permanent role, when it will be filled, and how the money being raised pays for it.

In diligence, the fractional CTO answers the technical questions

Diligence checklists ask about architecture and infrastructure, evidence that the company owns its domains, past security incidents, which developers the product depends on, and the technology budget (TechCrunch). A fractional CTO can write a short overview in advance covering how the product is built, who owns the code and each account, security basics, monthly costs and the team plan. On investor calls, they join as the person who knows the system. If an investor commissions an outside fixed-scope technical review, the same overview gives the reviewer a head start.

Ownership gaps are easier to fix before a round

  • Company-owned code and accounts. Repositories, hosting, domains and app store accounts are registered to the company, and people who have left can no longer get in.
  • Signed IP assignments. Goodwin's William Wilson advises written invention assignment agreements, which transfer ownership of the work to the company, from every employee, adviser and contractor (TechCrunch). Collecting a missing signature from a former contractor is simpler before investors' lawyers ask for it.
  • Claims that match the product. Features described as live on the website or to investors should be live in the code.

A good engagement ends with a handover

Fractional work usually ends one of three ways: the company hires a full-time CTO or VP of Engineering, the product reaches a stable state that needs less senior attention, or the company outgrows part-time leadership. In each case the handover is easier when both sides knew from the start which accounts the company held and how the rest would move, decisions were written down as they were made, and the fractional CTO helped hire their replacement.

Working with DenyaDev

DenyaDev is a fractional CTO practice for founders and small teams, run by Paul Denya. Services covers how engagements start, terms and common questions. The usual first step is a free 30-minute intro call.

Sources

What are you building?

A free 30-minute call to talk through where things stand and what a first step could look like. Send a deck or PRD ahead of time if you have one.