# Agent Ready Website Monthly QA Playbook

Run this 30 day workflow to make your SaaS docs easier for AI agents to discover and consume, then report measurable progress to leadership.

## Setup
Use your current docs site, one agent readiness scanner, your llms.txt file, and a fixed set of five recurring buyer questions from sales or enablement.

## Steps

### 1. Baseline your current docs surface
Run an agent readiness scanner and do a manual review of your top docs paths. Record missing crawl guidance, broken paths, and pages that are hard for AI systems to parse.

### 2. Publish core machine consumption assets
Ship llms.txt plus markdown friendly delivery for your most used product docs. Keep this focused on high traffic and high intent docs first.

### 3. Define a fixed test set of buyer prompts
Use the same five recurring buyer questions each week so your trend data is comparable. Include at least one pricing nuance question such as "Does this SaaS support SSO on the mid tier plan?"

### 4. Run weekly validation and retrieval checks
Validate llms.txt every Friday, then run your five buyer prompts against top product pages. If retrieval misses spike week over week, roll back the docs change and re run validation.

### 5. Report monthly deltas to leadership
At day 30, report answer correctness rate, time to correct answer, and token usage trends. Focus on trend lines, not one off wins.

## Done when
You can show month over month improvement on correctness, speed, and token efficiency for the same buyer question set, and your docs changes are tied to those gains.