Skip to content
ClelandCo

Part-time AI executive mandate — Fractional CAIO

Scoping conversations

A part-time executive mandate for defined AI operating decisions.

AI decisions need an assigned mandate. The workload may not be full-time.

A scoped, part-time Chief AI Officer mandate for named roadmap, evaluation, governance, vendor, reporting, and selected implementation decisions—without guaranteeing the business result. A defined executive mandate without a full-time seat.

Discuss whether a fractional seat is justified (opens in a new tab)

Briefing

A full-time Chief AI Officer is the right structure when the mandate and workload are genuinely full-time. Some organizations may need recurring executive decisions before the workload is large or stable enough to justify a permanent hire. The fractional seat covers that defined gap.

The technical work can be sound while executive responsibility is still unassigned. AI is added to an already full executive remit, vendor decisions accumulate, and pilots reach the production handoff without one person authorized to prioritize, stop, and report on them.

This is a standing, part-time seat with a written mandate and leadership access. The proposed mandate assigns the agreed roadmap, evaluation, governance, vendor, and reporting decisions to the fractional role. Legal, financial, and headcount commitments stay with the authorized company officers and arrive with a recommendation and the reasoning attached.

I can also build within the named scope. Implementation can remain inside the fractional mandate where a separate handoff would stall a specific system — for example evaluations, deployment, monitoring, latency, or cost work.

This is not a review-only advisory arrangement. It is an executive function held part-time, with the mandate, boundaries, and reporting line written down.

Three ways forward

Three options. One recommendation.

01

Hire a full-time Chief AI Officer.

The cleanest answer when the mandate and workload are already full-time. It is premature when the organization is still defining the authority, outcomes, and team the role would own.

02

Add it to the CTO’s remit.

This can work when capacity and authority are explicit. It is a poor fit when AI is simply added to an existing remit without removing work, setting decision rights, or creating a reporting cadence.

03

Define the fractional mandate.

A part-time executive mandate with defined decision rights, a reporting line, named systems in scope, and a transition plan for a permanent role.

How the engagement starts

Two scopes. One decision at a time.

The normal starting point is the assessment. A standing mandate is proposed only after the problem, authority, and systems in scope are written down.

AI Adoption Assessment

Bounded first step

Fixed diagnostic

One time, 1 to 2 weeks

A written read on where AI is worth spending, what has to be true before anything ships, and what to do first. The same assessment starts both leadership alternatives; it ends with a direct recommendation about which, if either, is justified — including when the answer is neither.

Scope is set by

The stakeholder groups, active use cases, systems, vendor decisions, and risk context to review.

Fractional CAIO

Optional standing engagement

Standing engagement

Six-month initial term, then month to month

A part-time Chief AI Officer seat with a written mandate for agreed roadmap, evaluation, governance, vendor, and reporting decisions. Legal, financial, and headcount commitments stay with authorized officers. Named implementation is included only where a handoff would stall the work.

Scope is set by

The decision mandate, leadership cadence, systems in scope, implementation load, vendor portfolio, and risk obligations.

Discuss whether a fractional seat is justified (opens in a new tab)

AI Adoption Assessment

Commitment

One time, 1 to 2 weeks

Scope is set by

The stakeholder groups, active use cases, systems, vendor decisions, and risk context to review.

Scope the problem before anyone signs a standing seat.

Format

  • Separate interviews with the people building and the people funding so their descriptions of the roadmap, evidence, and authority can be compared
  • A use-case inventory scored against client-approved value and feasibility criteria, with explicit continue, defer, stop, and unknown recommendations
  • A data-handling, evaluation, deployment, monitoring, and governance evidence-gap review mapped to stated questions, without a compliance or audit-readiness opinion
  • Build-versus-buy guidance per use case with criteria and assumptions recorded, plus technical and commercial review of vendor materials already in flight; legal terms remain with counsel
  • A roadmap prioritized under the agreed criteria and a recommendation on whether ongoing work is justified, including when the answer is no or not yet
Discuss whether a fractional seat is justified (opens in a new tab)

Usually the AI Adoption Assessment. The mandate and fee are written only after the problem has been scoped.

This is right for you if…

The board has started asking about AI and the answers are assembled the night before. You have vendor spend growing and no measurement of what it returns. You are considering a standing seat and would rather scope the mandate than invent it in month two. This is the same assessment the advisory engagement starts with; here it ends by saying whether a standing seat is justified yet.

Fractional CAIO

Commitment

Six-month initial term, then month to month

Scope is set by

The decision mandate, leadership cadence, systems in scope, implementation load, vendor portfolio, and risk obligations.

A seat in leadership, defined decision rights, and one person responsible for running and reporting the mandate.

Format

  • Stewardship of the AI roadmap against evaluation criteria agreed in writing before implementation begins.
  • A seat in the leadership meetings named in the mandate and a written monthly report to the executive team or board.
  • Governance, evaluation, and risk-control records mapped to stated customer, audit, or acquisition questions, without a readiness or compliance opinion.
  • The AI Contingency Framework run across in-scope systems, with rehearsal criteria established before they carry material work.
  • Vendor selection and build-versus-buy recommendations documented inside agreed authority; technical/commercial requirements are reviewed while legal terms remain with counsel and authorized officers.
  • Hands-on implementation on named systems where splitting strategy from delivery would stall the work.
  • A hiring plan and interview support for the permanent team, including the person who may take the permanent role.
Discuss whether a fractional seat is justified (opens in a new tab)

A recurring weekly decision cadence, attendance at the leadership meetings named in the mandate, and a written monthly report to the executive team or board.

This is right for you if…

Pilots keep stalling after the demo and no single person answers for it. You need someone who can take a board the available evidence, recommend stop or continue, and still be technical enough that the roadmap survives a conversation with your engineers.

Fit

Worth knowing before you call.

Signals this engagement may fit

Mid-market companies, funded startups, and portfolio companies with active AI work, no assigned senior mandate for the function, and a mandate that does not yet require a full-time executive.

  • Pilots repeatedly stall between demonstration and production and the transition has no assigned operating lead.
  • The board is asking about AI and the reporting process is assembled ad hoc.
  • Vendor commitments are growing without a shared way to evaluate them.
  • A customer, auditor, or acquirer has started asking how AI systems are governed.

Where this is the wrong call

  • Organizations that want a reviewer rather than a decider. That is the AI Strategic Advisor engagement.
  • Anyone who wants the title without granting authority. Without leadership access and an agreed mandate, the role cannot exercise the proposed decision rights.
  • Teams that want one bounded project delivered rather than a standing executive seat.
  • Companies that cannot name a business outcome for AI. Start with the assessment; it may recommend waiting.

What happens first

The opening phase, step by step.

The AI function has one named responsible role, an agreed mandate, a roadmap tied to written outcomes, and a decision record covering what is funded, stopped, bought, built, and reported.

  • Days 1–30

    Assessment and roadmap.

    A scoped inventory and evidence review of current AI activity: what evidence exists, where spend lacks evaluation, which opportunities score highest under client-approved criteria, and what has to be true before an in-scope decision proceeds. Ends in a prioritized roadmap with outcomes agreed in writing, not a list of features.

  • Days 31–60

    Governance, vendors, and the first build.

    Evaluation and risk controls mapped to stated customer, audit, acquisition, and legal requirements without claiming readiness or compliance. Technical and commercial vendor requirements are reviewed; contract interpretation and renegotiation remain with counsel and authorized officers. A first implementation proceeds only if it is named in scope and has attainable acceptance evidence.

  • Days 61–90

    Measure, compare, and report.

    Early evidence is compared with the definition of done agreed in writing during the first thirty days. The board or executive team receives the available evidence, limitations, open risks, and continue, change, or stop recommendations.

  • Ongoing

    Operate, and plan your own exit.

    Monthly reporting, continuous vendor and roadmap stewardship, and a hiring plan for the permanent team — including the interview loop for the person who takes the seat. Where included in scope, handover artifacts begin during the initial operating window rather than at the end.

Against the alternatives

Advisory, mandate, or visibility.

DimensionAI Visibility MeasurementAI Strategic AdvisorFractional CAIO
Starts withAI Visibility BaselineAI Adoption AssessmentAI Adoption Assessment
Initial termThree-month initial term, then month to monthThree-month initial term, reviewed each quarterSix-month initial term, then month to month
Working cadenceAfter live validation, sampling is planned weekly across configured ChatGPT, Perplexity, Gemini, Claude, and Google AI Mode surfaces, with a written monthly report and review call.A standing weekly working session with the people doing the build, defined async availability between sessions, and a written monthly decision record.A recurring weekly decision cadence, attendance at the leadership meetings named in the mandate, and a written monthly report to the executive team or board.
Scope is set byThe approved question set, validated provider surfaces, locations, competitors, and remediation backlog.The use cases, systems, vendor decisions, stakeholder groups, and risk requirements under review.The decision mandate, leadership cadence, systems in scope, implementation load, vendor portfolio, and risk obligations.
Who holds the mandateYou approve the target questions. I carry responsibility for the measurement process and agreed remediation work.Your leadership holds the mandate. I pressure-test the plan and record the reasoning.I carry the agreed part-time mandate and report on the function.
Decision rightsExecution inside an agreed remediation scope; business decisions stay with you.Advisory. Your leadership decides.Delegated decision rights inside a written mandate; legal, financial, and headcount commitments stay with authorized officers.
Hands on keyboardYes. Profile, schema, and citation work is included within the written scope.Review and working sessions; no implementation in this engagement.Yes, on named systems where separating strategy from delivery would stall the work.
Best forMeasuring and improving how AI answers describe and cite a business.A capable team that needs senior judgment and reusable criteria.An active AI function with no assigned senior mandate and no demonstrated need for a full-time seat yet.

The operator

Who you're working with.

Jeremy Cleland is the sole operator. About gives the background and its limits; Selected Work links the public technical evidence, contribution, status, and limitations.

About JeremyInspect selected work

What this engagement does not include.

Full-time availability. The scope names the recurring meetings, decision channel, systems, and implementation work included. If those obligations require daily availability, the recommendation is a full-time hire.

A title without the authority. Without leadership access and agreed authority/budget boundaries, the role cannot exercise the proposed decision rights and becomes a reporting layer. If the operating mandate is not there, the AI Strategic Advisor engagement may fit better.

Net-new research. This is applied work on your systems and your data. Original research, unrelated platform rebuilds, and speculative model training require a separate decision and scope rather than being implied by the standing mandate.

Permanence. The intended ending is that you hire a full-time CAIO and I help you interview them. An engagement that has no exit condition is a subscription, and you should be suspicious of anyone selling you one.

Questions

Asked and answered.

How much time does the seat carry, and how is the fee set?
It is a part-time seat scheduled around the decisions and leadership meetings named in the mandate, not a promise of unlimited access. The written scope accounts for the decision authority, systems, implementation work, vendor portfolio, meeting load, and risk obligations. The scope, cadence, term, boundaries, and fee are presented together before you decide.
What decisions do you actually own?
The mandate can include use-case prioritization, evaluation and governance gates, vendor selection, build-versus-buy calls, and the executive reporting rhythm. Legal, financial, and headcount commitments remain with the authorized company officers; those decisions come with a recommendation and written reasoning.
Do you build, or only decide?
Both, within the named scope. Implementation is included where a separate strategy-to-delivery handoff would add material execution risk for a named system. Unrelated platform work and net-new research are separate, so the executive seat does not become an undefined engineering retainer.
How is this different from hiring an AI consultant?
A project consultancy is normally accountable for a defined deliverable. This is a standing executive mandate: responsibility for the roadmap, recurring decisions, reporting, and follow-through remains in one defined role for the term. If you need only a document or one bounded project, that is the cleaner structure.
What happens when we hire a full-time CAIO?
That is the intended ending. The hiring plan, interview loop, and transition plan are part of the work. Handover includes the roadmap, decision record, runbooks, controls, and open questions whether or not the fractional engagement is extended.
What happens when the AI fails?
The published AI Contingency Framework applies to in-scope systems: planning, rehearsal, and sustainment. Rehearsal criteria are agreed before material use, and the monthly report records what was tested, what failed, and what remains open.
What is out of scope?
Full-time availability, net-new research, unrelated platform rebuilds, and work outside the named systems or mandate. Additional work is scoped separately rather than absorbed into vague executive access.

Start with the mandate, not the title.

The assessment maps the work, authority, risks, and expected evidence before a standing seat is proposed. It can recommend the fractional mandate, the advisory engagement, a bounded project, a full-time hire, or no engagement yet.

Discuss whether a fractional seat is justified (opens in a new tab)