aitechinv.com
success
Claude Code
intent

What does aitechinv.com do and who is it for? Explain it back to me.

10steps
46.0sduration
$0.4530cost
115,236tokens
18 steps8 reasoning steps2 searches
home
/en
/en/services
/en/about
/en/industries
/en/contact
/en/insights
search
search
/en/pricing
100%
on-site discovery
88%
reliability
88%
link following
path origin
  • previous resource88%
  • prior knowledge13%
insight

The agent successfully assembled a comprehensive explanation of AITI's positioning, target market, and differentiation by fetching and synthesizing content from six site pages (homepage, services, about, industries, contact, insights). However, the task is only partially satisfied because a critical dimension—pricing—could not be answered: the /en/pricing URL returned 404, and no pricing information exists anywhere on the site. The site is moderately navigable for discovery but deliberately opaque on commercial terms.

  • ›Steps [3], [5], [6], [7] provided the core narrative about AITI's framework, services, founder background, and target industries—all surfaced clearly through the site's main navigation. The homepage and services pages contained the differentiator claims ('Traditional consulting is obsolete') and methodology.
  • ›Step [10] (/en/pricing → 404) revealed a critical gap: pricing is intentionally absent, not an oversight. The agent correctly inferred this signals custom enterprise engagement pricing but had to reason about absence rather than find published information.
  • ›The site relies on narrative positioning rather than structured data—no schema.org markup, no pricing tiers, no case study metrics. The agent had to synthesize meaning from scattered page content, and multiple sections were truncated in the HTML responses, limiting full content exposure (e.g., 'fourth I in AITI', full industries list, insights blog content).
  • ›88% of fetches came from prior knowledge (the cached HTML artifact) rather than live crawling, suggesting the agent worked from a snapshot. The site's Next.js architecture with heavily truncated responses indicates content may be client-side rendered, creating incomplete visibility into the actual page text even when fetched.

Help the next agent finish on aitechinv.com

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 →