The agent successfully built a comprehensive overview of Authsignal by fetching the main site (authsignal.com) and pricing page, then supplemented with web search for competitive context. The site was navigable but fragmented: business information lived on authsignal.com while docs.authsignal.com contained only technical docs; pricing required a separate URL fetch; and competitor positioning had to be inferred from the layering concept rather than explicitly stated.

• ›Site separation friction: docs.authsignal.com is purely technical reference—the agent had to type authsignal.com from memory to reach business content (pricing, use cases, positioning). The docs site did not link outward to the marketing site, forcing agent memory-based navigation.
• ›Pricing page not discoverable by browsing: the agent found /pricing by URL memory; the homepage fetch did not surface a pricing link or navigation path. Half of URLs came from memory, not site links.
• ›Composable positioning is the core differentiator but not formally documented: the agent inferred Authsignal's 'sits on top, doesn't replace' advantage from marketing copy, but the docs never explicitly contrast it against Auth0, Okta, or Duo. Competitive positioning is implicit, not structured.
• ›Search-only source for alternatives: the agent used web search to populate the competitor landscape section—no on-site competitive analysis or alternatives page exists. The final response's 'sources' section cites external competitor aggregators, not Authsignal's own content.
• ›Implementation and ROI details missing: the agent correctly flagged that while Authsignal claims 3-week deployment and cost savings, neither the docs nor the marketing site provides case studies, ROI calculators, or professional services pricing—the site requires sales contact for these details.