---
title: "12 AEO Retainer Deliverables: What to Bill For and What Software Should Do"
description: "Twelve monthly AEO deliverables, ranked by client impact, with a blunt test for which ones software should execute instead of leaving to your team."
url: "https://groas.com/post/12-things-you-can-bill-for-in-an-aeo-ret"
image: "https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/3e7bcce6-d34f-4bec-8cf2-fadc337094f2.png"
published: "2026-10-27T05:26:27.594Z"
modified: "2026-10-27T05:26:27.661Z"
---

October 27, 2026 · 10 min read

# 12 AEO Retainer Deliverables: What to Bill For and What Software Should Do

[Alexander PerelmanHead Of Product @ groas](https://groas.com/author/alexander-perelman)[LinkedIn](https://www.linkedin.com/in/alexander-433793253/)

![Tiny model workers build buildings out of stacked paper pages while a giant security camera looms over the site, watching but doing none of the work.](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/3e7bcce6-d34f-4bec-8cf2-fadc337094f2.png)

In this article

1. [1. Track the prompts, but do not sell the chart as the work](#1-track-the-prompts-but-do-not-sell-the-chart-as-the-work)
2. [2. Report share-of-answer without hiding the losses](#2-report-share-of-answer-without-hiding-the-losses)
3. [3. Maintain schema without claiming it won the citation](#3-maintain-schema-without-claiming-it-won-the-citation)
4. [4. Read the server logs before trusting the dashboard](#4-read-the-server-logs-before-trusting-the-dashboard)
5. [5. Audit the answers that beat your client](#5-audit-the-answers-that-beat-your-client)
6. [6. Keep the client’s basic facts consistent](#6-keep-the-clients-basic-facts-consistent)
7. [7. Own the monthly roadmap, not just the monthly call](#7-own-the-monthly-roadmap-not-just-the-monthly-call)
8. [8. Turn citation gaps into pages, not a folder of briefs](#8-turn-citation-gaps-into-pages-not-a-folder-of-briefs)
9. [9. Fix crawl access before asking why a page is invisible](#9-fix-crawl-access-before-asking-why-a-page-is-invisible)
10. [10. Refresh pages that already earn citations](#10-refresh-pages-that-already-earn-citations)
11. [11. Earn mentions beyond the client’s own site](#11-earn-mentions-beyond-the-clients-own-site)
12. [12. Publish an answer-first page the client can actually open](#12-publish-an-answer-first-page-the-client-can-actually-open)

Most AEO software demos open on the same screen: a chart showing whether your client appeared in ChatGPT yesterday. I have sat through that demo three times this year. Each time, I asked what my team would still have to do by hand after paying for it. This list is for agency owners building monthly AEO retainers across 10 or more client domains. It counts from the work that mostly measures progress to the work I would start with: something a client can open, read and use.

## 1. Track the prompts, but do not sell the chart as the work

Check a fixed set of buyer prompts across ChatGPT, Gemini, Perplexity and AI Overviews. Save each answer and its citations so you can see what changed. Agency audits commonly cover [20 to 50 queries across 4 to 6 engines](https://www.amicited.com/blog/agencies-add-ai-search-visibility-service/); that set can become the monthly baseline. Polling and parsing are mechanical. **Software should run this without your team.**

Clients pay to know you are watching, but a tracking chart has never won a citation by itself. That matters when you price the retainer. Published AEO pricing spans [$1,500 to $5,000 a month for small businesses, $5,000 to $10,000 for mid-market clients and $10,000 to $20,000-plus for enterprise](https://www.stackmatix.com/blog/aeo-services-pricing). The [$3,000 to $5,000 middle can become a margin trap](https://www.amicited.com/blog/agencies-add-ai-search-visibility-service/): too expensive for monitoring alone, too cheap if your team must make every fix manually. I used to tell clients software covered the work inside the fee. I was wrong. Much of it covers the watching.

**First step:** Lock 30 buying prompts per client for 90 days. Stop adding vanity prompts just to make the chart move.

![Ink cartoon of an agency owner facing AI answer charts while client work piles up](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/5e286988-4710-46af-8b0c-a41a871c98ef.png)

## 2. Report share-of-answer without hiding the losses

For your tracked prompts, report the percentage of answers that mention the client, mention a rival or mention neither. It is the AI-search version of share of voice, and it gives clients a readable view of where they are absent. Software can calculate it. You still choose which rivals count and which prompts deserve attention, so this is **partly automated reporting, not optimization**.

Separate branded, best-X and how-to prompts. A blended average can look healthy while a rival owns every answer to the buying question that matters. Clients should be able to read the report and see what needs work; they should not have to mistake the report for work shipped.

**First step:** Group the existing prompt set by intent and show share-of-answer for each group. Put the biggest commercially relevant absence beside the number.

## 3. Maintain schema without claiming it won the citation

Keep JSON-LD, business-entity details, sameAs links, FAQ markup and product markup valid as pages change. This is billable maintenance. It is also easy to oversell because it looks technical in a report.

A controlled test of [1,885 pages that added JSON-LD against 4,000 controls found small, mixed changes across ChatGPT, AI Mode and AI Overviews, described as statistical noise](https://www.stackmatix.com/blog/aeo-services-pricing). Cited pages were [3x more likely to have schema, but that correlation was attributed to site quality rather than causation](https://www.stackmatix.com/blog/aeo-services-pricing). The mechanism is hygiene: markup keeps facts machine-readable. It does not make an engine trust the page.

Software can validate and patch markup. You still decide which entities and facts matter. **Bill schema as maintenance, never as the reason citations rose.**

**First step:** Validate the markup on the pages you intend to earn citations for, then fix what has broken before adding more.

## 4. Read the server logs before trusting the dashboard

A dashboard tells you what appeared in an answer. Server logs tell you who fetched the site and what happened when they arrived. Separate [training bots such as GPTBot and ClaudeBot from retrieval bots such as OAI-SearchBot, Claude-SearchBot and PerplexityBot, as well as user-triggered fetchers such as ChatGPT-User](https://www.jasper.ai/blog/how-to-audit-and-analyze-ai-crawler-traffic). Then check status codes, most-crawled URLs, 403s and 429s.

Clients pay for this as insurance against an invisible block. Software can parse logs and flag failures; it cannot decide every access policy or settle an argument with the security plugin. For example, a client may choose to [allow OAI-SearchBot while blocking GPTBot](https://www.jasper.ai/blog/how-to-audit-and-analyze-ai-crawler-traffic). That choice needs an owner.

**First step:** Pull one month of logs per client. Identify the fetchers reaching priority pages and investigate a blocked retrieval request before polishing another visibility slide.

## 5. Audit the answers that beat your client

For ten money prompts, save the full answer, the cited URL and the format that won: table, list, definition or review snippet. This turns [competitor share-of-voice benchmarking](https://www.amicited.com/blog/agencies-add-ai-search-visibility-service/) into a work order. If a rival wins with a pricing table, you can see the gap instead of merely reporting that the rival appeared.

Software should collect answers and citations. A strategist must decide which losses are worth pursuing; not every prompt deserves a page. **Do not hand a client 200 losing prompts. Hand them three worth winning.**

The same discipline applies when buying the tracker. At ten clients with 40 prompts each checked on four engines, published comparisons put plans at [$399 a month on Geoptie Enterprise, $489 on Otterly Premium, $795 on Peec Scale, $990 on Semrush with a 25-prompt-per-client cap, and $4,089 on Profound Agency Growth](https://geoptie.com/blog/best-geo-tools-for-agencies). The workload may look identical on a spreadsheet while the limits and bill look nothing alike.

The pool matters as much as the sticker price. In one five-brand comparison, [Koalr Business allows 50 prompts per site, while the cited Peec and Otterly plans use shared prompt pools; Profound is priced by workspace](https://www.koalr.ai/blog/agency-tools). White-label access also differs across [Geoptie, Peec, Otterly and Profound](https://geoptie.com/blog/best-geo-tools-for-agencies). That is why I would run the [22 checks before signing up 10 client domains](https://groas.com/post/the-aeo-platform-pre-signing-checklist-f), not after. **If every useful prompt consumes more of a shared allowance, model the tenth client before buying for the first.**

**First step:** Pick ten prompts tied to pipeline. Record the winning URL and format for each, then choose the three losses you would actually fund a response to.

![Stack of client invoices shrinking as per-prompt tracking fees pile up](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/6f0a5927-d834-4c4e-ac2b-4f7a86560f63.png)

## 6. Keep the client’s basic facts consistent

Check the same name, address, phone number, hours, founders, pricing and service list wherever the client maintains a profile: Google Business, LinkedIn, Crunchbase, Wikidata and relevant directories. Contradictory records make a fact harder to repeat confidently. The deliverable is not a list of discrepancies. It is corrected records.

Software can watch for drift. Someone still has to edit profiles, submit corrections and deal with directory support forms. That is a reason agencies can charge for entity work: an in-house setup using a [$100 to $500 tool plus $2,000 to $6,000 in staff time may still lack Digital PR and entity work](https://www.stackmatix.com/blog/aeo-services-pricing).

**First step:** Agree on five canonical facts with each client. Check those facts monthly and assign an owner to every correction. **A drift alert that nobody resolves is another chart.**

## 7. Own the monthly roadmap, not just the monthly call

Spend thirty minutes showing what shipped, what changed and which three priorities come next. Clients pay for this because a human takes responsibility when the numbers are flat or a rival moves. I have kept $3k retainers alive through flat months by showing the log of fixes, pages and mentions shipped since the previous call. The mechanism is accountability, not a prettier deck.

Software can assemble the action log. It cannot defend a priority when the client asks why the team chose one prompt cluster over another. Nor should a strategist spend the call reading out screenshots the client already has.

**First step:** End every call with three named shipments for the next month, each tied to a prompt cluster. **If you cannot name three, inspect the work before rewriting the deck.**

## 8. Turn citation gaps into pages, not a folder of briefs

Find the prompts where the client is absent and a rival is cited. Then specify what page or update would close each gap. Agencies already sell [citation gap analysis and monthly content optimization briefs](https://www.amicited.com/blog/agencies-add-ai-search-visibility-service/). The client pays because it looks like a plan. The trap is stopping there.

Software that only surfaces opportunities leaves the expensive half to your staff. The [Peec comparison describes opportunities without content writing attached](https://indexly.ai/blog/aeo-and-geo-tool-pricing-comparison-2026-profound-vs-airops-vs-peec-ai-vs-indexly/). I want a tighter handoff: prompt cluster in, answer-first draft out, then a page ready for review in the CMS. A strategist should choose the gaps; software should not make a junior copy each brief into a document and start from zero.

**First step:** Cap each client at three gaps a month and get the three corresponding pages or updates into production. **Ten briefs and zero pages is not a retainer deliverable.**

## 9. Fix crawl access before asking why a page is invisible

Make sure the systems you want to reach a page can fetch it. Check robots.txt, server responses and pages that depend on slow or fragile JavaScript rendering. A blocked fetch can waste every content decision that follows it. I learned the underlying lesson on paid landing pages: good account work cannot rescue a page the crawler cannot read.

Software can flag a block and, where it has access, help patch it. It cannot assume the block was a mistake. Someone must confirm the client’s policy, work with the developer or security owner, and verify the fix. **Automate detection and execution; keep the access decision accountable.**

**First step:** Check retrieval access to priority pages in the week you sign the client. Resolve an unintended block before commissioning another page.

## 10. Refresh pages that already earn citations

Identify the five to ten client pages already earning mentions. Each month, check whether their prices, dates, specifications, availability and opening answers still match what the client offers. A cited page can lose its usefulness when a rival updates a clearer answer and you leave a stale one in place. The work is not another audit of decay. It is the edited page.

Software should compare a cited page with the prompt and the current facts, prepare the stale block for revision and push an approved update to the CMS. If it merely flags decay and waits for your copywriter, you kept the labor and lost the speed. Human review still matters when a price or offer needs confirmation.

**First step:** List each client’s cited URLs and schedule a monthly check. Touch the pages that need it, even when the useful change is only three sentences. **Defend the citation before you have to win it back.**

## 11. Earn mentions beyond the client’s own site

Look for the third-party pages that answers already cite: trade press, review pages, comparison posts, relevant discussions and clean directory listings. Then work to get the client accurately included where it belongs. Publishing another paragraph on the client’s blog cannot substitute for an independent mention.

Software can locate rival mentions and organize outreach. It cannot make an editor publish, create a credible review or turn a directory correction into Digital PR. This is human work, and it deserves a line item. The earlier [in-house cost comparison](https://www.stackmatix.com/blog/aeo-services-pricing) matters here: tools and staff time do not automatically produce external corroboration.

**First step:** For each client, list the five third-party pages cited most often for their money prompts. Work that list before proposing another broad content campaign. **Find the source the answer trusts, then decide whether the client has a legitimate place on it.**

## 12. Publish an answer-first page the client can actually open

Build a page around one buying prompt. Answer it in the first 120 words, then give the reader a useful comparison table, an FAQ where appropriate and a clear next step. This is the [direct-answer, comparison-table and FAQ content](https://www.amicited.com/blog/agencies-add-ai-search-visibility-service/) a client can inspect without learning your reporting vocabulary. A clear, extractable answer gives an AI system something usable to cite. A brief sitting in a folder does not.

This is where I test software claims hardest. In the cited tool comparison, [Profound Growth caps content at three articles a month, Peec surfaces opportunities without writing, and bundles with content agents and publishing can actually ship pages](https://indexly.ai/blog/aeo-and-geo-tool-pricing-comparison-2026-profound-vs-airops-vs-peec-ai-vs-indexly/). If a tool writes a brief but your juniors still paste into WordPress at midnight, **you bought half a product**.

I would ask for CMS publishing in the demo, not another Google Doc. Make the vendor show how a missing answer becomes a reviewed page. That is the economic test behind [the shift from white-label SEO to white-label AEO](https://groas.com/post/from-white-label-seo-to-white-label-aeo): a retainer needs execution, not another login. A prompt tracker that only watches and reports leaves the work on your payroll, no matter how polished the dashboard looks. [The dashboard alone will not protect margin as prompt volume grows](https://groas.com/post/stop-shopping-for-the-best-aeo-software).

[groas offers white-label delivery at $299 per client account per service](https://groas.com/for-agencies), with publishing, technical fixes and citation work rather than a queue of recommendations for your juniors. I would still make it pass the same test as any vendor.

**First step:** On your next demo, bring one missing buying prompt and ask the vendor to show the path to a published answer page. If I were starting one AEO retainer tomorrow, I would start here. It is the line item the client can open, read and forward to a boss.

## Frequently Asked Questions

### Should AEO prompt tracking be billed as a deliverable in a monthly retainer?

Prompt tracking is worth doing because clients pay to know you are watching, but a tracking chart has never won a citation by itself. Polling and parsing prompts across engines is mechanical, so software should run it without your team. Price the retainer with that distinction in mind.

### How should share-of-answer be reported so a blended average doesn't hide losses?

Report the percentage of answers that mention the client, a rival or neither, then separate branded, best-X and how-to prompts. A blended average can look healthy while a rival owns every answer to the buying question that matters. Show the biggest commercially relevant absence beside the number.

### Does adding JSON-LD schema actually win AI citations?

Evidence suggests it is hygiene rather than a citation driver. A controlled test of 1,885 pages that added JSON-LD against 4,000 controls found small, mixed changes across ChatGPT, AI Mode and AI Overviews described as statistical noise. Cited pages were 3x more likely to have schema, but that correlation was attributed to site quality rather than causation. Bill schema as maintenance, never as the reason citations rose.

### Why check server logs instead of relying only on an AI visibility dashboard?

Server logs show who fetched the site and what happened when they arrived, including blocked retrieval requests, 403s and 429s that a dashboard never reveals. Software can parse the logs and flag failures, but a client may deliberately allow OAI-SearchBot while blocking GPTBot, so every access decision needs an owner.

### How many losing prompts should you act on when auditing competitor answers?

Do not hand a client 200 losing prompts; hand them three worth winning. For ten money prompts, save the full answer, the cited URL and the format that won, then choose the three losses you would actually fund a response to. Not every prompt deserves a page.

### What should I check about prompt limits before buying an AEO tracker for multiple client domains?

Model the cost at your full client count, not just the first client. Plans differ widely: some, like Koalr Business, allow 50 prompts per site, while cited Peec and Otterly plans use shared prompt pools and Profound is priced by workspace. If every useful prompt consumes more of a shared allowance, the bill can balloon, and white-label access also differs across vendors.

### What entity facts should be kept consistent across client profiles?

Check the same name, address, phone number, hours, founders, pricing and service list wherever the client maintains a profile, including Google Business, LinkedIn, Crunchbase, Wikidata and relevant directories. Agree on five canonical facts with each client, check them monthly and assign an owner to every correction, because a drift alert nobody resolves is just another chart.

### What should an agency show in a monthly AEO client call?

Spend thirty minutes showing what shipped, what changed and which three priorities come next, each tied to a prompt cluster. A human takes responsibility when the numbers are flat or a rival moves, which is what keeps retainers alive through flat months. Do not spend the call reading out screenshots the client already has.

## Paid Ads & SEO, Run For You

Businesses pay one flat monthly fee per service, agencies resell it under their own brand, and groas does the work either way.

[See Pricing](https://groas.com/pricing)

## Structured data

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://graph.groas.com/entity/groas","name":"groas","url":"https://groas.com/","description":"groas is a done-for-you marketing service, not software: elite people working with proprietary technology systems run search ads, Meta ads, SEO and AI search for businesses, and white label for agencies, with a dedicated senior strategist owning every account.","logo":{"@type":"ImageObject","url":"https://groas.com/icon-512.png","width":512,"height":512},"sameAs":["https://www.linkedin.com/company/groas/"]},{"@type":"WebSite","@id":"https://groas.com/#website","name":"groas","url":"https://groas.com/","inLanguage":"en-US","publisher":{"@id":"https://graph.groas.com/entity/groas"}},{"@type":"WebPage","@id":"https://groas.com/post/12-things-you-can-bill-for-in-an-aeo-ret#webpage","url":"https://groas.com/post/12-things-you-can-bill-for-in-an-aeo-ret","name":"12 AEO Retainer Deliverables: What to Bill For and What Software Should Do","description":"Twelve monthly AEO deliverables, ranked by client impact, with a blunt test for which ones software should execute instead of leaving to your team.","inLanguage":"en-US","isPartOf":{"@id":"https://groas.com/#website"},"about":{"@id":"https://graph.groas.com/entity/groas"},"primaryImageOfPage":{"@type":"ImageObject","url":"https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/3e7bcce6-d34f-4bec-8cf2-fadc337094f2.png"},"breadcrumb":{"@id":"https://groas.com/post/12-things-you-can-bill-for-in-an-aeo-ret#breadcrumb"},"dateModified":"2026-10-27T05:26:27.661Z","mainEntity":{"@id":"https://groas.com/post/12-things-you-can-bill-for-in-an-aeo-ret#article"}},{"@type":"BreadcrumbList","@id":"https://groas.com/post/12-things-you-can-bill-for-in-an-aeo-ret#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://groas.com/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://groas.com/blog"},{"@type":"ListItem","position":3,"name":"12 AEO Retainer Deliverables: What to Bill For and What Software Should Do","item":"https://groas.com/post/12-things-you-can-bill-for-in-an-aeo-ret"}]},{"@type":"BlogPosting","@id":"https://groas.com/post/12-things-you-can-bill-for-in-an-aeo-ret#article","url":"https://groas.com/post/12-things-you-can-bill-for-in-an-aeo-ret","mainEntityOfPage":{"@id":"https://groas.com/post/12-things-you-can-bill-for-in-an-aeo-ret#webpage"},"isPartOf":{"@id":"https://groas.com/blog#blog"},"headline":"12 AEO Retainer Deliverables: What to Bill For and What Software Should Do","description":"Twelve monthly AEO deliverables, ranked by client impact, with a blunt test for which ones software should execute instead of leaving to your team.","datePublished":"2026-10-27T05:26:27.594Z","dateModified":"2026-10-27T05:26:27.661Z","image":{"@type":"ImageObject","url":"https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/3e7bcce6-d34f-4bec-8cf2-fadc337094f2.png"},"author":{"@id":"https://groas.com/author/alexander-perelman#person"},"publisher":{"@id":"https://graph.groas.com/entity/groas"},"keywords":"client, software, pages, first step, aeo, work, prompts, each","wordCount":2185,"inLanguage":"en-US"},{"@type":"Person","@id":"https://groas.com/author/alexander-perelman#person","name":"Alexander Perelman","jobTitle":"Head Of Product @ groas","description":"My background includes Goldman Sachs and Stanford Computer Science.","image":"https://groas.com/media/blog/4f17cac3a81acc224cc1b2cfab8f94bbc295a3089d13e8421125771ef8d4064f.jpg","worksFor":{"@id":"https://graph.groas.com/entity/groas"},"sameAs":["https://www.linkedin.com/in/alexander-433793253/"]},{"@type":"FAQPage","@id":"https://groas.com/post/12-things-you-can-bill-for-in-an-aeo-ret#faq","mainEntity":[{"@type":"Question","name":"Should AEO prompt tracking be billed as a deliverable in a monthly retainer?","acceptedAnswer":{"@type":"Answer","text":"Prompt tracking is worth doing because clients pay to know you are watching, but a tracking chart has never won a citation by itself. Polling and parsing prompts across engines is mechanical, so software should run it without your team. Price the retainer with that distinction in mind."}},{"@type":"Question","name":"How should share-of-answer be reported so a blended average doesn't hide losses?","acceptedAnswer":{"@type":"Answer","text":"Report the percentage of answers that mention the client, a rival or neither, then separate branded, best-X and how-to prompts. A blended average can look healthy while a rival owns every answer to the buying question that matters. Show the biggest commercially relevant absence beside the number."}},{"@type":"Question","name":"Does adding JSON-LD schema actually win AI citations?","acceptedAnswer":{"@type":"Answer","text":"Evidence suggests it is hygiene rather than a citation driver. A controlled test of 1,885 pages that added JSON-LD against 4,000 controls found small, mixed changes across ChatGPT, AI Mode and AI Overviews described as statistical noise. Cited pages were 3x more likely to have schema, but that correlation was attributed to site quality rather than causation. Bill schema as maintenance, never as the reason citations rose."}},{"@type":"Question","name":"Why check server logs instead of relying only on an AI visibility dashboard?","acceptedAnswer":{"@type":"Answer","text":"Server logs show who fetched the site and what happened when they arrived, including blocked retrieval requests, 403s and 429s that a dashboard never reveals. Software can parse the logs and flag failures, but a client may deliberately allow OAI-SearchBot while blocking GPTBot, so every access decision needs an owner."}},{"@type":"Question","name":"How many losing prompts should you act on when auditing competitor answers?","acceptedAnswer":{"@type":"Answer","text":"Do not hand a client 200 losing prompts; hand them three worth winning. For ten money prompts, save the full answer, the cited URL and the format that won, then choose the three losses you would actually fund a response to. Not every prompt deserves a page."}},{"@type":"Question","name":"What should I check about prompt limits before buying an AEO tracker for multiple client domains?","acceptedAnswer":{"@type":"Answer","text":"Model the cost at your full client count, not just the first client. Plans differ widely: some, like Koalr Business, allow 50 prompts per site, while cited Peec and Otterly plans use shared prompt pools and Profound is priced by workspace. If every useful prompt consumes more of a shared allowance, the bill can balloon, and white-label access also differs across vendors."}},{"@type":"Question","name":"What entity facts should be kept consistent across client profiles?","acceptedAnswer":{"@type":"Answer","text":"Check the same name, address, phone number, hours, founders, pricing and service list wherever the client maintains a profile, including Google Business, LinkedIn, Crunchbase, Wikidata and relevant directories. Agree on five canonical facts with each client, check them monthly and assign an owner to every correction, because a drift alert nobody resolves is just another chart."}},{"@type":"Question","name":"What should an agency show in a monthly AEO client call?","acceptedAnswer":{"@type":"Answer","text":"Spend thirty minutes showing what shipped, what changed and which three priorities come next, each tied to a prompt cluster. A human takes responsibility when the numbers are flat or a rival moves, which is what keeps retainers alive through flat months. Do not spend the call reading out screenshots the client already has."}}]}]}
```