The agent successfully assembled a comprehensive explanation of GetWhys by relying almost entirely on web search results and press releases rather than the website itself. The official getwhys.io domain returned only JavaScript-heavy Next.js pages with minimal extractable content, forcing the agent to piece together what GetWhys does, who it serves, pricing model, and competitive positioning from external sources (Crunchbase, PR Newswire, third-party analysis). The site itself was poorly navigable for information discovery—direct navigation attempts yielded 404s (/features) or blank pages—making the "heavy bridge" friction classification appropriate.

• ›The homepage and main pages at getwhys.io returned only JavaScript bundles with no visible HTML content; no information about the product, pricing, or differentiators could be extracted directly from the site.
• ›All substantive answers came from web search results pointing to press releases (PR Newswire), company profile sites (Crunchbase, ZoomInfo, Tracxn), and third-party review/comparison sites. The agent never successfully extracted content from the official domain pages.
• ›The /pricing page returned a 404, and /about, /request-pricing, and /data-sources returned valid HTTP 200 responses but with identical JavaScript-only payloads—the site's navigation structure exists but the content is client-side rendered and invisible to content fetches.
• ›Pricing and product tier details (Compass, Compass Pro, Compass Scale) appeared only in external sources and press releases, not on the official site. The agent correctly noted this lack of transparency and cited the outdated $99/month pricing reference.
• ›Competitive positioning and unique differentiators (vs. Suzy, Cint, traditional research agencies) were inferred from search results and third-party comparisons, not from GetWhys' own marketing or positioning documents.
• ›The agent filled substantial gaps with prior knowledge and synthesis (e.g., interpreting the platform's three data sources, explaining the flat annual fee model) rather than finding these details on the site.
• ›The site is agent-hostile: it uses client-side rendering for all content, lacks structured data or meta descriptions in fetched responses, and does not publish machine-readable pricing or product information at discoverable URLs.