railwaymen.org
success
Claude Code
intent

What does railwaymen.org do and who is it for? Explain it back to me.

7steps
34.9sduration
$0.0480cost
23,975tokens
8 steps1 reasoning step
home
/services
docs
/why-railwaymen
/case-studies
/hire-developers
/portfolio
80%
answer from your site
43%
answer efficiency
83%
followed site links
answer sources
  • from this site80%
  • from agent knowledge20%
url discovery
  • given in the task14%
  • followed a link71%
  • guessed the URL14%
insight

Agent successfully assembled a coherent overview of Railwaymen's positioning, pricing model, and market focus from three working pages (homepage, services, case-studies). The site is moderately navigable but sparse on details—it relies on custom consultations rather than publishing case study examples, competitor comparisons, or pricing ranges; the agent filled gaps with inferences about typical engagement models rather than retrieved facts.

  • ›Step [0] (homepage) and [1] (services) provided the core facts: services offered, target industries, custom pricing model, and contact channels—all clearly stated. Step [5] (case-studies page) added differentiation points (awards, client count, industry experience) but did not link to specific named case studies despite the URL suggesting it would.
  • ›Three attempted URLs returned 404 (/about, /why-railwaymen, /hire-developers), indicating either broken navigation links or guessed URLs that don't exist. The agent recovered by typing /portfolio and /case-studies from memory, not by following site-furnished links.
  • ›Pricing information is complete but deliberately vague: the site explicitly states 'no definite answer' and directs prospects to submit estimate requests. This is publishable fact (not a gap), though the agent noted it under 'couldn't find' because specific ranges or tier examples are absent.
  • ›The agent correctly distinguished between what the site states (service categories, company stats, client regions) and what it does not publish (named case studies, competitor positioning, engagement model options). The 'couldn't find' section uses model reasoning rather than failed fetches.
  • ›Navigation friction was light: the site's working pages were findable and complete enough to answer the core task, but the shallow site structure (many 404s, no detailed case studies visible) meant the agent had to infer industry-specific engagement models from general development industry knowledge.

See every agent that visits railwaymen.org

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 →