gurus.works
success
Claude Code
intent

What does gurus.works do and who is it for? Explain it back to me.

9steps
59.1sduration
$0.5420cost
94,665tokens
16 steps7 reasoning steps3 searches
home
home
docs
/servicios
/services
search
search
search
/desarrollo-web-guatem…
83%
on-site discovery
50%
reliability
17%
link following
path origin
  • previous resource17%
  • web search17%
  • prior knowledge67%
insight

The agent gathered enough information to partially explain gurus.works, but the site's lack of transparent pricing and public portfolio forced heavy reliance on prior knowledge and inference. Step [1] provided the homepage meta description (the core service claim), and step [14] confirmed their content strategy, but neither returned structured pricing data or detailed service tiers. The agent successfully characterized what they do and who they target, but had to acknowledge major gaps in pricing transparency and differentiation.

  • ›Step [1] homepage returned only meta description and truncated HTML—no visible body content describing services, pricing, or differentiators in a machine-readable way. The agent relied on the meta tag 'Agencia guatemalteca de desarrollo web, apps móviles y SEO. Creamos sitios WordPress y tiendas en línea para PYMEs. Entrega en 4 a 8 semanas' as the primary source for what they do.
  • ›Steps [5], [6], [7] all returned 404s for /pricing, /servicios, /services—indicating the site does not publish pricing in dedicated, discoverable pages. The agent had to infer from prior knowledge that they offer 'custom project basis' pricing starting at $100, which was never confirmed by any fetched content.
  • ›Step [14] (blog post on web development in Guatemala) was routed via search results but returned only truncated HTML, not the full article body. The agent cited it as a source in the final response's source list without confirming it contained substantive pricing or service differentiation content.
  • ›The agent's statement 'The structured data mentions a price range starting at "$100"' appears to come from prior knowledge or search snippet extraction, not from any fetched HTML that was shown in the trajectory.
  • ›Web search steps [9], [10], [12] returned link lists but no search snippets containing pricing or service details were included in the trajectory. The agent may have used search results to route to step [14] but did not extract answer content from the search responses themselves.
  • ›The site is poorly agent-navigable for pricing discovery: no /pricing page, no structured markup visible in truncated HTML, no clear CTA linking to pricing from homepage, and no public case studies or portfolio links mentioned in any response. The agent had to work around this entirely.

Help the next agent finish on gurus.works

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 →