Sample report

A practical readiness report a business can act on.

See the kind of evidence, priorities and publishable guidance a paid workspace gives your team.

Built for existing websites whose next buyer may ask an AI agent before they ask sales.

Want this for your own site?

Run the free scan first. The preview gives a score and package recommendation; paid workspaces unlock the detailed report and implementation files.

Run free scan

saas

SaaS agent readiness sample

Score

Grade

A SaaS site with pricing and docs, but no dedicated agent discovery files or manifest.

Example buyer

B2B SaaS team with a usable homepage, pricing page and docs, but no clear agent-readable route through the offer.

Public pages explain the category, but not the buying path.

Docs and support exist, yet agents have to infer how they fit together.

No dedicated discovery files or agent catalog are visible.

Why it matters

An assistant can describe the company loosely, but may miss plan boundaries, support routes, current status and the safest next step for a buyer.

Paid workspace includes

Prioritized public-site findings

Review notes for claims and unknown facts

Draft discovery files for customer approval

Post-publish verification prompts

View Agent Delivery Pack

Executive decision previewShow

EXECUTIVE DECISION SUMMARY

Readiness: 54/100 (Grade D)
Decision: Core implementation recommended

PRIORITY 1 - Public discovery
Status: Open
Owner: Website team
Why it matters: Assistants do not have a stable route into current product context.
Acceptance: Public discovery routes resolve and match approved website facts.

PRIORITY 2 - Buyer handoff
Status: Open
Owner: Marketing and commercial
Why it matters: Plan, support and next-step context is spread across separate pages.
Acceptance: A fresh review can identify the product, audience, plans and human buying route without assumptions.

PACKAGE OUTCOME
SYA Standard Discovery Layer, customer review workflow and assisted installation.

api

Developer/API sample

Score

Grade

A developer tool with docs, but unclear OpenAPI, auth scopes and write-action boundaries.

Example buyer

Developer-tool team whose docs are useful to humans, but hard for agents to map into a safe technical recommendation.

Docs are present, but the canonical API path is not obvious.

Auth, scope and write-action boundaries need clearer public wording.

Examples exist, but agents need stronger cues about what is live.

Why it matters

Technical buyers may get a generic summary instead of a reliable route to docs, auth requirements, examples and support.

Paid workspace includes

Developer-readiness findings

API/docs routing recommendations

Safe action boundary notes

Agent test prompts for technical buyers

View Agent Delivery Pack

Executive decision previewShow

EXECUTIVE DECISION SUMMARY

Readiness: 62/100 (Grade C)
Decision: Developer/API upgrade recommended

PRIORITY 1 - Technical source of truth
Status: Open
Owner: Product and engineering
Why it matters: Agents can find docs but cannot confidently distinguish current examples, limits and actions.
Acceptance: The approved technical entry point states authentication, scope and safe action boundaries consistently.

PRIORITY 2 - Human escalation
Status: Open
Owner: Developer experience
Acceptance: Unsupported or account-specific questions route to the published support path.

ecommerce

Commerce readiness sample

Score

Grade

A commerce site with product pages, but unclear support, shipping, return and checkout boundaries.

Example buyer

Commerce business with product pages, but scattered policy, support and checkout context.

Products are visible, but delivery and support expectations need stronger routing.

Refund and policy pages are not easy for agents to connect to the purchase path.

Human checkout boundaries need to be explicit.

Why it matters

Assistants may describe products but avoid sending buyers onward, or they may overstate policy details that are not clearly published.

Paid workspace includes

Buying-path readiness findings

Policy and support routing notes

Human approval boundary guidance

Commerce-specific verification prompts

View Agent Delivery Pack

Executive decision previewShow

EXECUTIVE DECISION SUMMARY

Readiness: 48/100 (Grade D)
Decision: Commerce upgrade recommended

PRIORITY 1 - Purchase context
Status: Open
Owner: Ecommerce and content
Why it matters: Product facts are visible, but policy and support context is not joined to the buyer path.
Acceptance: A buyer can verify current product, delivery, support and human checkout steps from published routes.

BOUNDARY
No autonomous purchase claim. Pricing and policy facts require customer confirmation.

web3

Web3 product sample

Score

Grade

A Web3 product with strong docs, but missing a concise agent-readable commercial and support summary.

Example buyer

Web3 product with docs and technical context, but missing a concise commercial and support summary for agents.

Docs are strong, but buyer-facing status and support routes are harder to summarize.

Network, asset and wallet boundaries need conservative public wording.

Commercial claims need to stay separate from technical documentation.

Why it matters

Agents may mix product claims, docs and ecosystem assumptions unless the public context is more tightly framed.

Paid workspace includes

Safe-claims review notes

Agent-readable support and status summary

Discovery file drafts

Post-publish prompt checks

View Agent Delivery Pack

Executive decision previewShow

EXECUTIVE DECISION SUMMARY

Readiness: 71/100 (Grade B)
Decision: Targeted context upgrade recommended

PRIORITY 1 - Public scope
Status: Open
Owner: Product and communications
Why it matters: Strong technical docs do not fully explain the buyer-facing offer and official support route.
Acceptance: Published context separates live product facts, customer-provided onchain context and claims that must not be inferred.

BOUNDARY
No token-safety, investment-quality, ownership or security conclusion is inferred from an address alone.