How an Agency Sets AEO Deliverables and SLAs in the Client Contract

The hardest sentence in an AEO contract is the one about results. Clients want a promise: we will show up in ChatGPT by quarter two. You cannot make it, because AI answers are probabilistic, they change every time the same question is asked, and no agency controls the model. But "we promise nothing" does not close deals or survive a renewal either. The way out is to write two different kinds of commitment into the agreement and keep them clearly separated: process SLAs the agency fully controls and honors every month, and outcome KPIs the agency measures, reports, and works toward but never guarantees. Here is how to draft each, what belongs in the deliverables schedule, and the guarantee language a careful agency keeps out.

Why AEO contracts cannot borrow the SEO template wholesale

SEO retainers already avoid ranking guarantees, and for good reason: Google states plainly that no one can guarantee a specific position, so reputable SEO retainer contracts commit to process and KPI targets instead. AEO makes that problem sharper. A Google ranking, once earned, is relatively stable and observable by anyone. An AI citation is neither. Ask ChatGPT the same buyer question twice and you can get two different brand lists, because sampling, retrieval, and the live index all shift between runs. So an AEO agency that copies an SEO scope and swaps "rankings" for "citations" has quietly promised something even less controllable than the thing SEO contracts already refuse to promise.

That does not mean AEO work is unmeasurable. It means measurement has to be defined as a method, not a snapshot. You do not report "we are cited in ChatGPT." You report "across a fixed 40-prompt panel, sampled five times per engine per month, the brand's citation share rose from 4 percent to 11 percent." The contract has to name that method, because the method is the deliverable that makes every outcome number meaningful.

The two-layer commitment structure

Write the agreement in two clearly labeled layers. The client should be able to see, at a glance, what you are bound to do and what you are working toward.

Everything you can do regardless of how the engines behave goes in the top row and is binding. Everything that depends on the model's behavior goes in the bottom row as a target you report against honestly, up months and down months alike. The line between the two rows is the single most important thing in the document, and it is the line that protects both sides: the client knows exactly what they are buying, and the agency is never in breach because an engine reshuffled its answer. Handling that conversation well is a skill in itself, covered in what to say when a client demands AEO guarantees you cannot make.

What belongs in the deliverables schedule

Name every deliverable explicitly, with a count and a cadence, the way a disciplined scope of work names pages-per-month rather than "content." A real AEO retainer, priced in 2026 at roughly 3,000 to 15,000 dollars a month depending on scope per current agency cost guides, typically commits to a version of the following.

• A baseline AI visibility audit, delivered once at kickoff: the fixed prompt panel, the engines tested, the sampling frequency, and the starting citation share per engine. This is the measurement instrument the rest of the engagement reports against, and it is the same source-tracing logic behind how OnlyAEO works.
• Answer-first content production, at a named velocity. Two to four pieces per month is a common baseline; state the exact number, because "ongoing content" is where scope creep lives.
• Technical AEO implementation: structured data, a maintained machine-readable feed, and crawler-access fixes. Specify whether you build the llms.txt file with a generator and maintain it, or hand the client a spec to implement, because that boundary decides who is accountable when a crawler is blocked.
• Off-domain authority work: a stated number of roundup pitches, review-site actions, or earned placements per period. Name the count, not the outcome, since you cannot force a publisher to say yes.
• Monthly reporting on a fixed date and in a fixed format, tracking citation share against the panel and tying it to pipeline signals. The structure that survives a skeptical finance review is laid out in what to put in a monthly AEO report for agency clients.

For each line, write the number, the cadence, and the boundary of what is in scope. Feed maintenance and content velocity are exactly the kind of continuous work the AI Feed Engine is built to keep running, and pinning them to explicit counts is what lets you defend your delivery hours later.

The SLAs worth committing to

Process SLAs are promises about responsiveness and reliability, and they are where an AEO agency can differentiate without overreaching. Commit to the ones you can hit every single month.

• Reporting SLA: the report lands by a named business day, every month, in the agreed format. Missing it is a real breach, which is the point; it is a promise you can keep.
• Turnaround SLA: a defined response window for two urgent cases: an engine stating a wrong fact about the client, and a competitor displacing them on a priority prompt. Two to three business days to a diagnosis and a plan is defensible.
• Content SLA: the committed pieces ship within the month, with a defined revision cycle so approvals do not become an excuse for missed velocity.
• Measurement-integrity SLA: the prompt panel and sampling method stay fixed for the engagement, and any change is documented and agreed, so the trend line cannot be gamed by quietly swapping prompts.

Notice that none of these promise a citation. Every one is inside your control, and together they tell the client they are buying a reliable operator, which is a stronger sell than a hollow outcome guarantee.

The clauses to keep out, and the ones to add

Some language does not belong in an AEO contract at all, and a few clauses should always be present.

Keep out any guaranteed citation, guaranteed placement in a named engine, guaranteed traffic figure, or guaranteed position by a date. These are the AEO equivalents of guaranteed number-one rankings, and they are red flags in any credible engagement. Also keep out ownership terms that let you retain the client's content or feed if they leave; the client should own the assets you produce.

Add a performance disclaimer that names the real sources of variance in plain terms: AI models change without notice, answers vary between runs, retrieval indexes update on their own schedules, and third-party sources the engines cite are outside anyone's control. Add a measurement-method clause that defines the panel and sampling as the agreed source of truth. Add an exit clause with a reasonable notice period and clean asset handover. And add a leading-indicator framing so that when a month is flat or down, the report has somewhere honest to point: crawl and ingestion evidence, new citable passages shipped, and off-domain placements earned, all of which move before citation share does.

An engagement built this way is defensible at renewal because the value is visible in the process record even in a noisy quarter, which is exactly what carries a contract through the retainer renewal conversation. The FastTrackr AI case study shows the end state: a program where the deliverables were consistent, the measurement was fixed, and the citation gains followed. Write the contract so the work is the promise and the results are the honestly reported consequence, and you will spend far less time defending a number an engine chose for you.