The agent successfully built a comprehensive explanation of Nejo by combining direct site fetches with web search results. The site itself is poorly navigable for understanding the full picture—most pages return truncated HTML without semantic content, pricing pages are missing (404s), and the site is primarily in German with broken English routing. The agent had to rely heavily on external sources (brutkasten, basicthinking, Tracxn) to assemble coherent information about what Nejo does, who it's for, and how it's priced.

• ›The homepage and product pages (steps 1, 6, 8, 12, 16) returned only HTML skeletons with preload declarations and truncated response bodies, revealing no actual content about features, pricing, or positioning—the agent received unusable markup from the site itself.
• ›Pricing information was not discoverable on the site (step 7 returned 404 for /pricing), forcing the agent to rely entirely on external sources like brutkasten and Tracxn articles (steps 13, 15, 20) for €15/application and 10% salary-based pricing details.
• ›The site's navigation is broken for English speakers: /en-de returns 200 but appears to be a German landing page, /en returns 404, and /en-de/about-us returns 410 with a redirect instruction, while /de-de/about-us (step 12) works—the agent had to guess and iterate through URL patterns.
• ›All substantive information in the final response (what Nejo does, target users, pricing models, differentiation, company size, funding status) came from external sources or prior knowledge, not from the site's own content; the site provided no machine-readable metadata, structured data, or clear information architecture.
• ›The site is German-first with minimal English presence; even the products page (step 8, 16) was fetched but failed to render useful information in the response snapshot, indicating either language-dependent rendering or JavaScript-dependent content that was not accessible to the agent's fetch mechanism.