The agent successfully understood Maven AGI's core offering, target market, and positioning, but had to work around the company's deliberate opacity on pricing and technical details. The site itself provided clear positioning and compliance credentials but offered no public pricing page or detailed competitive feature matrices—forcing the agent to supplement with third-party sources (eesel.ai) and infer from sales-driven design patterns.

• ›Steps [5], [6], [7], [11] returned clear, well-structured marketing content on the homepage, about page, product page, and resources hub—all stating the core value prop (93% autonomous resolution), customer count (90+), compliance certifications (SOC 2, HIPAA, PCI-DSS), and funding ($50M+). This content was directly usable and required no disambiguation.
• ›Step [8] (pricing page) was a bait-and-switch: the URL exists and returns 200, but the page is titled 'Book a Demo' with no actual pricing or plan information visible in the HTML. The agent had to infer from this non-response that Maven deliberately hides pricing behind sales conversations.
• ›Step [12] (eesel.ai third-party blog) was the only external source that provided concrete pricing estimates (~$100k+), demonstrating the site itself publishes no cost structure. The agent cited this as necessary context.
• ›The site provides no side-by-side competitor comparison tables or detailed feature differentiators—only blog posts about 'alternatives to Cognigy' etc. Step [14] returned one of these blogs, but it positions Maven as *the* answer rather than explaining tradeoffs. The agent had to note this as a gap.
• ›The domain mismatch (maven-agi.com vs. mavenagi.com) was handled by the agent via web search [3], which immediately surfaced the correct domain. The parked domain added friction but not blocker-level confusion.
• ›The site is agent-ready for discovery and positioning (clear navigation, structured meta descriptions, published case studies) but deliberately agent-resistant for pricing evaluation and technical depth—no public cost structure, no API docs linked, no model card or hallucination/safety disclosures.