Six days a month, a payment clause tied to “successful deployment of the agent programme”, and not one engineer whose objectives the signatory can change. That combination turns up often enough in fractional Chief AI Agents Officer engagement letters to be worth naming as a drafting fault rather than a negotiation detail. The role is sold as ownership. The paper grants advice. When the two diverge the programme stalls, and both sides blame the other for a gap that was written in before anyone started work.
Part-time ownership can work. It works when the engagement letter treats authority as a schedule to be enumerated, not as something implied by the job title. What follows is the set of clauses that decide whether a fractional CAAO can act, and the failure mode that appears when each one is left vague.
Days per month, and the split that makes them useful
A day count on its own tells you almost nothing. Two engagements at eight days a month behave completely differently depending on whether those days are pre-allocated or drawn down on request. The second version reliably collapses into meeting attendance, because meetings are what other people put in a calendar.
Split the days by function in the contract itself. A workable structure names three buckets and fixes the ratio, with a variance band rather than a hard figure so that a heavy month does not become a breach.
| Bucket | Share of contracted days | What it covers | What happens if it is not ring-fenced |
|---|---|---|---|
| Governance and decision rights | 40-50% | Approval gates, risk register, model and tool selection, vendor review, board or ExCo reporting | Approvals queue behind delivery work and the holder becomes the bottleneck |
| Delivery direction | 30-40% | Backlog shaping, design review, agent evaluation criteria, sign-off on production releases | Engineers proceed on their own judgement and the holder audits after the fact |
| Incident and unplanned reserve | 15-20% | Escalations, regulator or customer queries, rollback decisions | Every incident becomes an overage argument held mid-crisis |
Those percentages are drafting defaults to argue over, not benchmarks. There is no reliable public dataset of fractional CAAO engagements as of August 2026, so treat any figure quoted with more precision than this as somebody’s single sample. Calibrate against your own release cadence: an organisation shipping agent changes weekly needs a larger delivery-direction share than one shipping quarterly.
Two mechanical points matter as much as the ratio. Fix the minimum contiguous block – half a day is usually the floor below which nothing substantive happens. And state whether unused days roll forward, because the unstated assumption on the buyer’s side is always that they do.
Approvals that travel with the role
The centre of the contract is a delegated authority schedule: a list of decisions, and for each one whether the fractional holder decides, recommends, or has no standing. Anything absent from the list defaults to the internal executive, and the letter should say that explicitly so the ambiguity resolves in a known direction.
| Decision | Typical fractional right | Drafting note |
|---|---|---|
| Promoting an agent to production against customers | Decides, or holds a veto | A veto without a decision right is usually enough, and is far easier to get signed |
| Suspending a live agent | Decides unilaterally, without prior consultation | The one right that cannot be conditional; consultation wording defeats it |
| Tooling and model vendor selection | Decides below a stated spend threshold | Set the threshold as a figure in the contract currency, not as “material amounts” |
| Engineering priority inside the agent programme | Recommends, with a named internal owner obliged to respond in writing | The obligation to respond within a stated period is what makes a recommendation real |
| Hiring, objectives and performance review of programme engineers | Consulted | Rarely granted in full; ask for input into objectives rather than into review |
| Data access and retention policy for agent logs | Recommends; legal or the data protection officer decides | Keep the split visible so accountability is not implied by silence |
Suspension authority deserves separate attention. It is the only right that must survive out of hours, must not require a quorum, and must be technically enforceable – meaning the holder either carries the credentials to trigger the kill switch or names two internal people contractually obliged to act on instruction. A suspension right that depends on somebody answering a phone at 02:00 is a suspension right that does not exist.
Incident escalation and out-of-hours cover
Agent incidents rarely arrive on contracted days. The letter has to answer four questions, and where it answers none of them the default is a holder who is nominally accountable and practically absent.
- Who holds the pager. A fractional executive should not sit on first line. Name the internal on-call rota and place the CAAO at second or third escalation.
- What triggers escalation to the role. Define it by consequence rather than by severity label: customer-visible incorrect output, unauthorised data egress, autonomous action outside approved scope, contact from a regulator.
- Response commitment. A stated window – acknowledgement within a set number of hours on business days, a longer one at weekends – is more honest than implied availability. Overpromising here is what makes the whole arrangement look unserious after the first incident.
- How incident time is charged. Drawn from the reserve bucket first, then billed at a stated day rate beyond it. Agree that rate at signature, never during an incident.
The accountability gap: outcomes without direction rights
The characteristic failure of fractional ownership is a contract that assigns responsibility for outcomes produced by people the holder cannot direct. Payment is linked to adoption or reliability targets; the engineers delivering against those targets report to a delivery director whose own objectives say nothing about agents. The holder can advise, escalate and document. They cannot reprioritise a sprint.
The symptoms appear early, usually inside two release cycles. Recommendations are minuted but never scheduled. The holder starts writing longer memos, which is what people do when writing is the only lever they hold. Risk items reappear unchanged in consecutive steering packs. Delivery leadership begins routing decisions around the role, because consulting it adds a week.
There are three honest resolutions and no fourth. Grant the holder a formal dotted line over the programme engineers, including input into their objectives. Or install an internal deputy with real line authority who is contractually bound to execute the CAAO’s directions within an agreed scope. Or delete the outcome language and price the engagement as advisory, which is a perfectly respectable thing to sell. What does not work is keeping accountability wording because it reassures the board.
The internal successor and what they inherit
Every fractional CAAO engagement should be written as a temporary arrangement with a named endpoint, even when neither side expects it to end soon. The deputy is not an administrative convenience. They are the mechanism that converts part-time authority into full-time enforcement, and they are the reason the engagement can end without the programme unwinding.
Name the person in the schedule, not the job family. Give them a defined share of the contracted days as direct handover time. And specify what transfers, because the failure here is a departing holder leaving slide decks rather than operating machinery. The successor should inherit, at minimum:
- The agent register: every deployed agent, its business owner, scope of autonomy, data access and date of last evaluation
- Evaluation harnesses and their pass thresholds, held in the company’s repository rather than the holder’s
- The risk register with open items, decision history, and the rationale recorded for each accepted risk
- Vendor contracts, model versions in production, and the exit path from each
- The approval log – who approved which production release, against what evidence
- Incident history with post-incident actions and their current status
Make the register a dated deliverable rather than a closing obligation. Handover artefacts written at the end of an engagement are written under the worst possible incentives.
Exit terms worth negotiating before signature
Notice periods on fractional executive contracts tend to be short, which is part of the appeal and part of the risk. Three points are worth fixing while goodwill is still intact.
First, asymmetric notice. A longer period from the holder than from the client is reasonable given how much knowledge concentrates in one person, and offering it strengthens the case for the authority being asked for elsewhere. Second, a run-off obligation: a fixed number of days after termination reserved for handover and for answering the successor’s questions, priced in advance. Third, access revocation as a checklist attached to the contract – credentials, model provider accounts, repositories, vendor portals – each line with a named internal owner. Revocation is the moment when nobody wants to spend an hour reading paperwork, so the paperwork has to be written already.
On intellectual property, separate the client’s operating material from the holder’s method. Registers, evaluation suites, prompts and configurations built for the client belong to the client. Frameworks and templates the holder brought with them should be licensed rather than assigned, and the clause should name them individually instead of gesturing at “pre-existing materials”.
The decision this leaves you with
Read the draft engagement letter and mark every sentence that makes the fractional holder accountable for an outcome. For each one, trace the shortest path from that sentence to a person who can be told what to build. Where the path runs through somebody who is only obliged to listen, you have two options.
Name an internal deputy with real line authority from day one – written into the schedule with their days, their obligation to execute directions within scope, and their inheritance defined. Or strike the accountability language and buy advice at an advisory price. Decide before signature. After the first production incident the same conversation costs a great deal more, and it is held in front of an audience.