The agent assembled a substantially complete understanding of Zephior's business model, target market, and positioning, but had to work around a JavaScript-heavy website that obscured pricing details and a broken comparison page. The site's core pages (homepage, /about, /ziva, /zelius) loaded but rendered primarily as HTML skeletons; the agent relied heavily on prior knowledge (45%) and web search results (9%) to fill gaps that the website itself did not expose in machine-readable form. Pricing information was partially available through search results mentioning CHF 749/month, but the official pricing page's full tier details remained inaccessible.

• ›Steps [1], [2], [3], [7], [8] fetched valid 200 responses but returned truncated HTML with minimal visible content—the pages appear to be SPA (Single-Page Application) shells that require JavaScript execution to render. The agent could not extract detailed product info, pricing tables, or feature comparisons from the raw HTML alone.
• ›Steps [11], [12], [15], [16] (web search results) provided the most actionable intelligence: search snippets and external comparison sites mentioned pricing (CHF 749/month), product names (Ziva, Zelius), and competitor context (Loopio, Responsive) that the website itself did not surface in a fetch-friendly way.
• ›The agent correctly identified critical gaps: the /vs comparison page returned 404 [step 13], the /pricing page existed but was not parseable, and key details about knowledge-base setup, Zelius success-fee mechanics, and customer case studies were not publicly documented or machine-readable. The site is visually functional but not agent-navigable without JavaScript rendering.
• ›Pricing information came entirely from external sources (search results and prior knowledge), not from the site's own /pricing endpoint. This indicates the pricing table is dynamically rendered client-side and invisible to server-side fetch.