The agent gathered substantial information about Propeller Crew's business model, target audience, and differentiation philosophy, but could not fulfill a core requirement of the task: it found no public pricing information despite explicit requests. The site's client-side rendering (Next.js) blocked access to most content; the agent relied heavily on prior knowledge and web search to construct its answer rather than fetching usable page content.

• ›Steps [1], [3], [6], [7] returned only truncated HTML boilerplate (font preloads, meta tags, Next.js script chunks) with no rendered content — the site is entirely client-side rendered and the agent could not access the actual page text, case studies, or service details.
• ›Step [19] (web search on site:propellercrew.com) surfaced a snippet mentioning a testimonial from 'Vitalii Sydorenko' about Slack-triggered automation, which the agent cited as evidence of real deployment work, but even this was fragmentary.
• ›The agent had to rely on 75% prior knowledge and conducted 7+ web searches trying to find pricing, engagement models, and competitive positioning — all critical parts of the task — because the site structure made it impossible to retrieve directly.
• ›Pricing URLs (propellercrew.com/en/pricing, propellercrew.com/services) both returned 404s; no pricing information is publicly exposed anywhere on the site or in search results.
• ›The agent synthesized a coherent narrative about their philosophy ('no demos, just working agents'), engagement model (likely custom project-based), and differentiation, but this was reconstructed from indirect sources and prior knowledge rather than grounded in fetched site content.