neo.sipgate.de
success
Claude Code
intent

What does neo.sipgate.de do and who is it for? Explain it back to me.

16steps
125.8sduration
$1.2626cost
212,021tokens
21 steps5 reasoning steps9 searches
home
docs
/features
search
home
search
/cloud-pbx
/preise
search
search
/preise
search
search
search
search
search
57%
on-site discovery
71%
reliability
43%
link following
path origin
  • previous resource43%
  • web search43%
  • prior knowledge14%
insight

The agent successfully assembled a comprehensive explanation of neo.sipgate.de's purpose, target audience, pricing, and competitive differentiation, but had to work around significant site navigation friction. The homepage and pricing page were accessible, but the site structure was opaque (404s on /pricing and /features forced web search), and pricing transparency for add-on modules remained incomplete even after fetching the official pricing page. The agent relied heavily on web search (43%) and prior knowledge (14%) to fill gaps that the site's own pages did not clearly surface.

  • ›Steps [1] and [7] (homepage fetches) returned truncated HTML without extractable structured content; the agent could not parse product modules, pricing tiers, or differentiators directly from the DOM.
  • ›Steps [12] and [13] (Cloud PBX and pricing pages via www.sipgate.de) returned content but were also truncated in the response; the agent inferred pricing (€12.95–€22.95/user/month) from the HTML but could not verify exact feature inclusions at each tier from what was fetched.
  • ›Step [17] (neo.sipgate.de/preise direct fetch) succeeded with 200 status but returned the same truncated pricing page; no add-on module costs were visible, forcing the agent to report this as 'opacity' rather than answer it.
  • ›The site does not publish a machine-readable differentiation between 'neo' and 'Business' tiers; the agent had to rely on web search results (step [19] via help.sipgate.de) to explain that neo is the new platform, not a separate product.
  • ›German data center and security positioning (steps [16] search results) was not directly discoverable from neo.sipgate.de itself; the agent had to fetch www.sipgate.de/funktionen/alles-made-in-germany and www.sipgate.de/sicherheit-datenschutz, indicating poor information architecture on the main domain.
  • ›The site structure is minimal: /pricing and /features returned 404s (steps [3]–[4]), forcing the agent to guess URLs or use web search. This suggests the site is a landing page or partial rebuild rather than a full product site.

Help the next agent finish on neo.sipgate.de

Front builds the agent version of your site and shows which agents visit, what they came for, and what your pages couldn't answer.

or talk to us about agent readiness →