--- title: "How to brief an agency | Am I Ready for Agents?" description: "How to brief an agency on agent readiness: a one-page brief that gets a fixed-scope, checkable proposal. Six items, with the red flags to watch." canonical: https://amireadyforagents.com/guides/how-to-brief-an-agency site: "Am I Ready for Agents?" last_updated: 2026-11-04 section: "Guides" --- # How to brief an agency | Am I Ready for Agents? > How to brief an agency on agent readiness: a one-page brief that gets a fixed-scope, checkable proposal. Six items, with the red flags to watch. Source: https://amireadyforagents.com/guides/how-to-brief-an-agency Site: Am I Ready for Agents? Last reviewed: 2026-11-04 # How to brief an agency on agent readiness ## In short Brief an agency on agent readiness with one page that asks for a fixed-scope, checkable proposal instead of an open retainer. Name the task, require a before scan from a public scanner, ask for each fix to be named by identifier, price it per fix or sprint, and require the same scanners and one agent journey after delivery. ## What goes on the one page 1. The main task an agent should be able to complete, and how you will know it did. Buy, book, request a quote or read an article. 2. The starting evidence: a scan from at least one free public scanner and screenshots of what a plain fetch of your key pages returns. 3. The standard to work to. Ask for each fix to be named by its AgentReady identifier, such as AR-FIND-01, or by the scanner's check name. 4. The price: a fixed fee per fix or per sprint, not a monthly retainer for AI visibility. 5. The proof: the same scanners re-run after delivery, plus one agent journey on the main task. 6. Your platform: named experience with Shopify, WordPress, Next.js or whatever you run. ## Why this shape works The evidence in the list below says that only two changes stopped an agent from getting an answer in Ora's experiment: an answer hidden in JavaScript and a 403 returned to agent user agents. Both are web team fixes that a scanner can show before and after. A proposal that does not start there should explain which check each month of work will fix. The same evidence is why a leader can ask for identifiers. The list of what a site should implement has stable names, so an agency can say which items it will deliver and you can check them without a developer. ## Red flags in a proposal - A promise of a position in AI answers. No agency controls what an AI product recommends. - No before and after evidence from a scanner you can run yourself. - A retainer that starts with content volume rather than the two blockers. - A file such as llms.txt as the headline deliverable. In Ora's experiment it did not change whether an agent got the answer, although it can be a reasonable small addition. ## What the evidence says Give a leader a one-page brief that gets a fixed-scope, checkable proposal instead of an open retainer. - 4 Nov 2026 Ora's scan is free, with no key, card or signup, and rate-limited by IP (read 4 Nov 2026). Vendor claim. [Ora pricing (JSON)](https://ora.ai/pricing?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=guide), read 4 Nov 2026 - 19 Oct 2026 Ora's 19-configuration experiment (190 probes) found only two changes stopped retrieval: an answer hidden in JavaScript (0 of 5 for plain fetch) and a 403 to agent user agents (0 of 5 for both clients). Vendor claim. [AgentReady.org guide](https://agentready.org/?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=guide), read 4 Nov 2026 - 19 Oct 2026 AgentReady requirements carry stable identifiers such as AR-FIND-01 and strengths MUST, SHOULD and MAY; the spec itself scores no one. [Introducing AgentReady.org (19 Oct 2026)](https://ora.ai/blog/agentready-launch?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=guide), read 4 Nov 2026 - 19 Oct 2026 The AgentReady essentials for every site are: allow agents in robots.txt and bot protection, put the answer in the initial HTML, return real HTTP status codes, and list pages in a sitemap. [AgentReady.org guide](https://agentready.org/?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=guide), read 4 Nov 2026 - Read 4 Nov 2026 Cloudflare's free scanner at isitagentready.com checks discoverability, content accessibility, bot access control, protocol discovery and commerce. [Is Your Site Agent-Ready? (Cloudflare, isitagentready.com)](https://isitagentready.com/), read 4 Nov 2026 - Read 4 Nov 2026 is-agentic.com, built by Vercel with Ora, weights essential checks for content sites and excludes checks that do not apply. [Is Agentic: AI Agent Readiness Score for your Site and App](https://is-agentic.com/), read 4 Nov 2026 ## Related - [What to ask a vendor](https://amireadyforagents.com/vendors/what-to-ask)Ora first, then three others, scored on the same five questions. - [Ask your web team](https://amireadyforagents.com/ask-your-web-team)The sentences to send, grouped by area. - [Tools that check](https://amireadyforagents.com/tools-that-check)Three free scanners, and the one we recommend. ## Sources 1. [Ora pricing (JSON)](https://ora.ai/pricing?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=guide) (ora.ai/pricing), read 4 Nov 2026. Vendor claim. 2. [AgentReady.org guide](https://agentready.org/?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=guide) (agentready.org), read 4 Nov 2026. Vendor claim. 3. [Introducing AgentReady.org (19 Oct 2026)](https://ora.ai/blog/agentready-launch?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=guide) (ora.ai/blog/agentready-launch), read 4 Nov 2026. 4. [Is Your Site Agent-Ready? (Cloudflare, isitagentready.com)](https://isitagentready.com/) (isitagentready.com), read 4 Nov 2026. 5. [Is Agentic: AI Agent Readiness Score for your Site and App](https://is-agentic.com/) (is-agentic.com), read 4 Nov 2026. Last reviewed 4 November 2026 Reviewed 4 November 2026. [5 sources](#sources), each with the day it was read.