Technical leadership · Fractional CTO

A fractional CTO who owns your AI architecture decisions, part-time

If you need accountable technical leadership for AI architecture and team direction but not a full-time executive, a fractional CTO retainer fits. I take ownership of a written remit, such as architecture, build-or-buy decisions, hiring and delivery reviews, for a stated number of days each month, keep a decision record, and plan for handing over to a permanent leader.

This is a good fit if…

  • You are a founder or CEO with an engineering team building AI features and nobody senior who owns the architecture and the trade-offs.
  • You are between technical leaders, or before your first senior hire, and decisions on models, providers and data are piling up.
  • Your board or investors want a named person accountable for technical risk, and a full-time CTO is not yet justified.
  • You are deciding whether to build, buy or integrate an AI capability and want that decision owned, not just advised on.

Look elsewhere if…

  • You need a hands-on CTO, Head of AI or VP Engineering as a substantial personal role, full-time or interim. That is a leadership appointment, discussed through dipankar.name.
  • You need senior hands on code under your own manager rather than leadership. Hire a contract AI solutions architect instead.
  • You need someone to own AI adoption across business teams rather than engineering. Use the fractional AI enablement lead.

What you get

Part-time technical ownership retainer

  • A written remit stating which technical decisions I own, which I advise on, and which stay with you.
  • A decision record covering architecture, providers, data handling and build-or-buy choices, with the reasoning and review dates.
  • A technical roadmap tied to business milestones, revisited each quarter.
  • A hiring plan and interview process for the roles you need, and participation in the loops.
  • A succession plan, so a permanent leader can take over the remit and the decision record.

How it runs

  1. 01

    Agree the remit

    We write down the decisions I own, the ones I advise on, the people I work with, the monthly capacity and how we will know the retainer is working.

  2. 02

    First-month review

    I review the architecture, delivery process, team and current AI commitments, and open the decision record with the most urgent choices.

  3. 03

    Run the cadence

    A regular rhythm with the team and leadership: architecture and delivery reviews, decisions recorded, hiring loops, and a short written update each month.

  4. 04

    Review and succession

    Each quarter we review the remit against outcomes. When a permanent leader is hired, I hand over the remit and the decision record and step back.

What needs to be in place

  • A sponsor, usually the CEO or founder, with authority to grant the remit.
  • Access to the codebase, architecture documents, delivery tools and the engineering team.
  • Clarity on budget and hiring plans, even if provisional.
  • Agreement on how decisions are escalated when I am not available.

Not included

  • Full-time or on-call availability. Capacity is stated in days per month and is not exceeded without agreement.
  • Statutory director duties or a seat on the board unless agreed separately and in writing.
  • Line management of the whole engineering organisation as a substitute for a permanent leader.
  • Legal, regulatory or investment advice.

Fractional CTO compared with other leadership options

Technical adviserFractional AI CTO (this page)Interim or full-time leaderContract architect
Accountability Advises; decisions stay with youOwns a written remit of decisionsOwns the whole technical functionOwns the design work you assign
Time commitment Occasional sessionsA stated number of days per monthMost or all of the working weekAgreed days, under your manager
Works with the team Rarely directlyRegularly, through reviews and hiringDaily, as their managerDaily, as a member
Writes code NoOccasionally, to de-risk a decisionDepends on the roleYes
Good fit when Your leadership is in place and wants a second opinionYou need ownership of key decisions without a full-time executiveThe role is large enough to need a person most of the weekYou have leadership but need senior design hands

When you need a fractional CTO, not a full-time one

Many companies building with AI reach the same gap. The engineering team can ship features, but the decisions that shape the next two years have no owner: which model providers to depend on, where customer data may be processed, whether to build a capability or integrate a vendor’s, how to evaluate output quality, and what to hire for next. The founder makes these calls between other jobs, or they are made implicitly by whoever writes the code first.

A full-time CTO may be the right answer eventually, but not yet: the role is not large enough, the budget is not there, or the company is still learning what kind of leader it needs. A fractional CTO fills that gap with accountable, part-time ownership of a defined set of decisions. I have written about what a fractional CTO is and when to hire one; this page describes how I run the role for AI-focused companies.

What the role involves

The core of the engagement is the remit: a short document that lists the decisions I own outright, the ones where I advise and you decide, and the ones that stay entirely with you. Typical owned decisions include architecture direction, model and provider choices, data-handling design for AI features, and the build, buy or integrate call for new capabilities. Typical advised decisions include hiring, budgets and roadmap priorities.

Within that remit, the work runs on a regular cadence:

  • Architecture and delivery reviews with the team, focused on decisions rather than status.
  • The decision record: each significant choice written down with options considered, reasoning and a date to revisit it.
  • Hiring: role definitions, interview design and participation in loops.
  • Board and investor support: technical sections of updates, and answers to technical due diligence questions.
  • De-risking: occasionally writing a spike or prototype myself when a decision depends on something nobody has tested.

My background for this is more than 18 years building and operating production software, including leadership roles such as Head of AI and Platform at Orangewood Labs and Principal AI Architect at a UK fintech.

The signature deliverable

You receive a part-time technical ownership retainer, made inspectable by the remit and the decision record. Illustrative example of a decision record entry:

FieldEntry
DecisionUse a hosted model provider for the document assistant; keep retrieval and evaluation in-house
Options consideredFully hosted assistant product; hosted model with own retrieval; self-hosted open-weight model
ReasoningCustomer contracts allow processing in the provider’s region; retrieval quality is the differentiator; self-hosting cost not justified at current volume
OwnerFractional CTO (owned decision under remit)
RevisitWhen monthly volume or a customer contract changes data-location terms

Illustrative example. Not taken from a client engagement.

How the retainer is judged

At the start we agree what success looks like, for example a decision backlog cleared, a senior hire made, or a platform migration planned and under way. Each quarter the sponsor reviews the remit against those measures and the monthly updates. If the retainer is not working, either side can end it on the notice agreed in writing.

Ownership and succession

Everything produced stays with you: the remit, the decision record, the roadmap, the hiring material. A fractional role should make itself unnecessary over time, so the retainer includes a succession plan: when a permanent technical leader joins, I hand over the remit and the record, and step back or end the engagement.

When to choose something else

If the question is a single build, buy or integrate decision rather than ongoing ownership, start with the build, buy or integrate guide. If you need someone to own AI adoption across business teams, see the fractional AI enablement lead. If you need senior design and code under your own manager, see hire a contract AI solutions architect. For a hands-on CTO, Head of AI or interim leadership role, see the leadership link on this page.

Questions buyers ask

What does a fractional CTO actually do each month?

Within the agreed remit: review architecture and delivery with the team, make or record the decisions I own, work through hiring loops, prepare technical material for the board or investors, and write a short monthly update. The exact mix is set in the remit and reviewed each quarter, so you can see where the days went.

How much time do we get?

A stated number of days per month, written into the retainer, with how quickly I respond between sessions. The engagement model on this page shows how the retainer is priced. If the work consistently needs more than the agreed capacity, that is a signal to discuss a larger role or a permanent hire, not to stretch the retainer quietly.

How is this different from hiring you as interim CTO or Head of AI?

A fractional retainer is part-time ownership of a defined remit. A hands-on CTO, Head of AI or VP Engineering role, full-time or interim, is a substantial personal leadership appointment with a different scope and contract. Those conversations happen through dipankar.name.

Can you help us hire our permanent CTO?

Yes. Writing the role, designing the interview process and taking part in the loop are common parts of the remit. The decision record and roadmap are kept so that a new leader can take them over, and the retainer is designed to end cleanly when they arrive.

Why an AI-focused fractional CTO rather than a generalist?

Because many current decisions are AI-specific: which models and providers, where data may go, how to evaluate output quality, when to build versus integrate, and what agents may do unsupervised. I have more than 18 years of production software experience, and my recent roles have been in AI architecture and platform leadership.

Discuss a fractional leadership brief

A short, non-confidential description is enough to start. I read every brief personally and reply within two business days, including when the answer is that I am not the right fit.

Step 1 of 2 · The basics