The agent assembled a reasonably complete overview of Consulting Revenue's core offering, pricing, and positioning by stitching together the homepage, workshop page, FAQ, and blog/insights content. However, the site's sparse structural organization and JavaScript-heavy rendering limited discoverability—the agent had to guess at several URL patterns (/pricing, /about, /how-it-works returned 404s) and relied heavily on prior knowledge and web search to fill gaps, particularly around competitive differentiation, case studies, and AI integration specifics.

• ›Steps [0, 3, 5] (homepage, contact, workshop) were the only directly content-bearing pages on the domain itself; they contained the service description, the £5,000 fixed price, the 1-day + 30-day-support model, and the target audience (boutique B2B consultancies). The workshop page title explicitly mentioned 'Scope, Terms and Price,' confirming pricing was on-site.
• ›Steps [9, 11, 13, 14] (blog, insights, FAQ, frameworks) returned 200s but were routed via prior knowledge or sitemap; the agent did not cite their actual content in the final answer, suggesting the pages existed but contained supplementary material rather than core positioning or pricing details that weren't already captured by the homepage and workshop pages.
• ›Steps [15–18] (web search results) and [19] (Nynch.com fetch) were essential to assembling the 'how it's different' narrative; the agent could not find a comparative positioning statement or alternatives page on consultingrevenue.com itself, so it inferred differentiation (AI integration into existing tools, founder-led delivery, 1-day compressed model) from search snippets and the related Nynch platform. This indicates the site does not explicitly document competitive positioning.
• ›The agent failed to fetch /pricing, /about, /how-it-works, /case-studies, /why, /alternatives, and /resources (all 404s), suggesting either a very minimal site structure or that critical information pages are missing or named differently—this forced reliance on homepage metadata, the workshop detail page, and external search to answer the task.
• ›JavaScript rendering dependency: The agent noted that 'the website is built with client-side React rendering, so much of the detailed content wasn't accessible through my standard fetch.' This is a significant agent-readiness gap—critical details about 'the plays,' AI integration mechanics, case studies, and testimonials likely live in the rendered DOM and were not exposed to the fetch.
• ›Pricing and core offer were clearly stated (£5,000, fixed, prepaid, GBP, 1-day workshop + 30 days support) on the homepage and /workshop page, making those facts well-indexed and easy to extract. However, post-workshop support specifics and AI tooling details remained ambiguous despite dedicated pages existing.