tunity.be
success
Claude Code
intent
What does tunity.be do and who is it for? Explain it back to me.
9steps
69.0sduration
$0.3840cost
28,359tokens
11 steps2 reasoning steps1 search
home
docs
docs
/services
/portfolio
search
/en/about-us
/company/tunity
/contact
60%
answer from your site
25%
answer efficiency
57%
followed site links
answer sources
- from this site60%
- from search results20%
- from agent knowledge20%
url discovery
- given in the task13%
- followed a link50%
- found via web search25%
- guessed the URL13%
insight
The agent successfully synthesized Tunity's positioning, services, and differentiation by combining the homepage and about-us page with search-derived pricing data. The site required guesswork and external lookups because pricing was absent, portfolio pages returned 404s, and information was distributed across non-standard URLs.
- ›Step [1] (homepage) was the primary source for services and positioning; Step [8] (about-us, discovered via search) provided the core differentiation narrative ('5 specialized experts per account', transparency values). Neither page was directly linked from the home page.
- ›Pricing was entirely absent from the site: three direct URL guesses (/pricing, /about, /services) all returned 404s. The agent had to rely on external search results (step [7]) to cite any price figure (€110–150/h), which was attributed to Sortlist, not Tunity's own disclosure.
- ›The site's navigation structure was fractured: standard pages like /pricing, /portfolio, /services returned 404s, forcing the agent to discover /en/about-us only via web search, not internal linking. The homepage URL had to be typed from memory, not discovered through navigation.
- ›Step [8] (about-us) directly supplied differentiation claims (team size, transparency positioning, regional focus) that became the backbone of the 'How It's Different' section; the homepage did not articulate these distinctions as clearly.
- ›Several claims in the final response (team size ~10 employees, founding year 2018, capacity details) came from search result snippets in step [7], not from fetched site content, indicating the agent relied on third-party business directories to fill gaps left by the site itself.
Help the next agent finish on tunity.be
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 →