The agent successfully understood SecPlaner's core business, target market, pricing model, and competitive positioning by assembling information from the site's homepage, feature pages, blog, and pricing page. The website is partially navigable for discovery — the agent had to use web search to find the pricing URL (/preise) and specific feature pages because the site uses client-side rendering that obscured navigation links. Core content exists but is not discoverable through standard URL guessing or navigation extraction.

• ›Step [1] (homepage) and steps [6, 7, 20] (feature pages) returned content confirming SecPlaner is a shift-planning and workforce management tool for security services, with features like AI-assisted scheduling, digital logbooks, guard control systems, and shift swaps. These pages were fetched successfully but the agent could not extract full navigation structure due to Next.js client-side rendering.
• ›Step [16] (pricing page at /preise) was only found via web search query [15], not through site navigation. The pricing URL is non-standard (/preise instead of /pricing), requiring prior knowledge or search. The agent could not access detailed pricing table content from the HTML response, but the URL discovery itself plus referenced pricing figures (€59/month base, €4/month per employee) came from search snippets and prior knowledge rather than direct page parsing.
• ›Step [14] (blog article on service planning) provided context on the use case but was discovered through search, not the site's IA. The site does not surface its own documentation or competitive comparison pages in a format the agent could extract; the agent had to rely on web search results mentioning competitors (Papershift, ShiftJuggler) rather than finding competitive positioning on secplaner.de itself.
• ›The agent explicitly noted HTML rendering issues — the Next.js framework returned truncated responses with no visible page content, forcing reliance on web search and prior knowledge (36% of fetches sourced from prior knowledge, 27% from web search, 36% from previous artifact). This indicates the site is not machine-readable in static form.
• ›Missing information (trial/freemium, support channels, integrations, implementation details) was not found on the site and could not be retrieved, suggesting these details are either behind login, not published, or require direct contact.