Agent successfully answered what Dembrane does, who it's for, and how it's priced using direct site fetches, but filled gaps in competitive differentiation using model memory rather than site content—three critical pages (how-it-works, solutions, blog post comparisons) returned 404s, forcing reliance on external comparison frameworks rather than Dembrane's own positioning.

• ›The site is poorly navigable: /how-it-works, /solutions, /features, and specific blog post URLs all returned 404s, eliminating core paths a user would follow to understand mechanics and differentiation. The agent had to guess URLs rather than follow internal links.
• ›Pricing and basic value proposition (what they do, who it's for) are retrievable directly from the homepage and /pricing page—these pages are well-structured and comprehensive, making that core sales information accessible.
• ›The agent's differentiation claims (live synthesis, democratic tech positioning, vs. traditional SRM platforms like Borealis/Jambo) are derived from model memory and external search results, NOT from site-provided comparisons—the blog post 'Why we said goodbye to AssemblyAI' was referenced on the blog index but failed to fetch.
• ›The /about page provided founder names and mission framing but did not articulate technical differentiation—the agent inferred positioning from high-level mission language rather than explicit competitor comparison.
• ›The agent had to conduct a web search to contextualize Dembrane within the broader stakeholder engagement market, indicating the site itself does not position the product against known alternatives or explain why it differs from SRM platforms.