The agent successfully assembled a comprehensive explanation of Heron's business model, target market, and differentiation by combining homepage content, product/platform pages, and a funding announcement blog post. However, the site itself offers no public pricing information—the agent had to acknowledge this gap directly rather than fill it from the site's own content. The site is moderately navigable for discovery but deliberately opaque on commercial terms.

• ›Steps [0], [18], [19] returned rich, well-structured product descriptions: the homepage tagline 'Automate Your Document Heavy Work' and meta descriptions established the core value (document intake → extraction → enrichment → CRM sync), and the /platform and /product pages elaborated on parsers, validation, and real-world use cases (60% time savings, 80% automation rates). These were the primary sources for 'what Heron does' and 'who it's for'.
• ›Step [22] (the $16.6M funding blog post) was the only source that surfaced customer ROI claims and industry positioning (lending + insurance focus). This page was not directly discoverable from the homepage—the agent found it via web search, not site navigation.
• ›Pricing was the largest friction point: steps [1], [2], [3], [5], [6], [7], [8], [9] returned only 404s for /pricing, /features, /use-cases, /contact, /how-it-works, /underwriting, /insurance, /lending. The agent correctly concluded Heron does not publish pricing publicly and requires sales contact. The /glossary/cost-per-submission page (step [14]) merely defines the metric, not the actual rates.
• ›Competitor information came entirely from web search results and third-party sites (G2, CBInsights, TipRanks), not from Heron's own site. The /competitor/competitor-d URL (step [13]) exists but returns a template with no content, suggesting incomplete implementation.
• ›The site's navigation structure is sparse: most standard SaaS pages (pricing, features, contact, use-cases) do not exist or return 404s. The agent had to rely on prior knowledge and web search (37% + 37% per metadata) to fill critical gaps that a typical SaaS site would surface in navigation or a resources hub.