inspinia.eu
success
Claude Code
intent

What does inspinia.eu do and who is it for? Explain it back to me.

16steps
61.0sduration
$1.0348cost
132,257tokens
24 steps8 reasoning steps8 searches
home
search
docs
/solutions
/solutions/building-ma…
/applications/skyplatf…
/solutions/knx-solutions
search
search
search
search
search
search
search
home
docs
50%
on-site discovery
75%
reliability
13%
link following
path origin
  • previous resource13%
  • web search50%
  • prior knowledge38%
insight

The agent successfully assembled a comprehensive overview of Inspinia's business model, products, and market positioning by combining direct website fetches with web search results. However, the site itself was poorly agent-readable—full HTML responses were truncated and the agent relied heavily on web search (50%) and prior knowledge (38%) to fill gaps that the site should have made explicit. The most critical gap remains: pricing information is entirely absent from the public website, forcing any serious evaluation to require a sales contact.

  • ›Steps [1] and [3] fetched the homepage but returned truncated HTML (4400+ chars truncated); steps [6], [10], [11], [12] similarly returned partial content. The agent had to infer product details and positioning from fragments rather than complete, structured data.
  • ›Web search steps [4], [14], [15], [16], [18], [19], [21], [22] surfaced URLs the agent then fetched directly—showing the site is discoverable but the search results themselves often contained more contextual framing than the fetches. For example, step [4] listed product pages that the agent later visited, and steps [15], [21], [22] provided URL hints for VRF, touch panels, and use cases.
  • ›The agent could not find pricing on the site and explicitly noted this as 'a significant blind spot.' No /pricing, /plans, or cost-related pages exist; the agent correctly concluded pricing is quote-based but had to infer this from absence rather than explicit communication.
  • ›Product and use-case information came from successful fetches ([10] BMS page, [11] SkyPlatform, [12] KNX solutions, [21] touch panels, [22] use cases), but the agent noted these pages did not render fully, limiting confidence in specification completeness.
  • ›The agent correctly identified that Inspinia is Czech-based and part of Elko EP ecosystem, but this required web search inferences rather than clear statements on the fetched About page ([6]).
  • ›Competitive differentiation had to be reverse-engineered from product descriptions and inferred from the agent's prior knowledge of the BMS market; the site does not explicitly compare itself to Honeywell, Johnson Controls, or Siemens.
  • ›The site is a JavaScript-heavy Webflow build that does not serve complete content through standard HTTP fetches, creating systematic friction for agent navigation.

Help the next agent finish on inspinia.eu

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 →