The agent assembled a comprehensive explanation of LeadPops by combining direct site fetches with web search results, successfully answering what the platform does, who it's for, how it's priced, and how it differs from alternatives. However, the site's navigation and content delivery were opaque—pricing pages failed to load or returned 404s, forcing heavy reliance on web search snippets and prior knowledge (84% of fetches came from prior knowledge or search rather than successful page traversals), and the agent had to explicitly call out multiple pieces of information that were confusing or impossible to locate on the live site.

• ›The homepage [1], pricing page [2], about page [4], mortgage services page [11], CRM comparison guide [15], and lead types blog post [20] were the only fetches that returned 200 status and were cited as sources—but HTML responses were truncated and unreadable in the trajectory, suggesting the agent relied on prior knowledge or search results to extract actual content rather than parsed page text.
• ›Multiple pricing URLs returned 404s ([10] /plans/mortgage, [12] /hybrid-loan-officer-marketing, [16] mortgage.leadpops.com/pricing), indicating the site's pricing structure is either hidden behind authentication, dynamically generated, or deliberately obscured. The agent resorted to web search to gather pricing claims ($200–$5,000+/month range).
• ›The site uses confusing product branding—both 'LeadPops' and 'rebel Ai' / 'rebel iQ' are mentioned, but the relationship between them is not clearly explained on the public site. Search results and web references had to clarify this was the same company/platform.
• ›Key differentiators (exclusive vs. shared leads, cost-per-funded-loan economics, Zillow/Bankrate heritage) appear in blog posts and guides rather than front-and-center on the homepage, requiring deep navigation or search to discover.
• ›The agent explicitly flagged unresolved gaps: exact pricing opacity, unclear CRM integration details, vague implementation timelines, and missing compliance/regulatory documentation—all items a human would struggle to find on the live site as well.
• ›The site is a Next.js SPA (React app), which means critical content may be client-rendered and not visible in raw HTML fetches, further degrading agent discoverability. The agent had to bridge this by using search and prior knowledge.