ferchau.com
success
Claude Code
intent
What does ferchau.com do and who is it for? Explain it back to me.
15steps
64.3sduration
$0.8849cost
130,156tokens
24 steps9 reasoning steps6 searches
home
/en/en
search
/de/en/about-us/who-we…
/de/en/customer/full-s…
search
search
/company/ferchau
/c/ferchau-engineering…
search
/company/ferchau
search
search
/de/de/services
/de/de/ueber-uns
56%
on-site discovery
67%
reliability
44%
link following
path origin
- previous resource44%
- web search44%
- prior knowledge11%
insight
The agent assembled a serviceable overview of FERCHAU's business by combining direct site fetches (English-language pages at /de/en URLs) with external sources (LinkedIn, Owler). The site itself proved difficult to navigate — defaulting to German, requiring URL guessing to find English content, and offering limited explicit detail on pricing, service boundaries, and differentiation. The agent had to rely heavily on inference, web search context, and LinkedIn metadata to complete the evaluation task.
- ›Step [9] (About Us page) and Step [10] (Full Service page) returned the core positioning — 'engineering and IT service provider' with 'full service' promise — but both pages were truncated in the response, limiting what factual detail was actually extracted from the site itself.
- ›Step [22] (LinkedIn company page) was truncated and likely the source of company metrics (employees, revenue, founding date) cited in the final response, but those figures were not directly visible in the trajectory. The agent appears to have inferred or synthesized from external metadata rather than parsing the actual site content.
- ›No pricing information was found on ferchau.com itself; the agent explicitly called this out as 'murky' and inferred a 'customized per contract' model based on industry norms rather than site disclosure. The site provides no transparent rate cards, quote tools, or billing examples.
- ›The site's language routing and URL structure (/de/en path) required the agent to guess or derive correct URLs; initial attempts to /en/en returned 404s. Search results were necessary to discover the correct /de/en subdirectory structure, indicating poor English discoverability.
- ›The agent never accessed a true 'competitors' section or explicit differentiation statement on the site; competitive claims ('deep specialization', 'full service promise', '145+ branch offices') were synthesized from about-us and service pages rather than parsed from a dedicated comparison or positioning page.
- ›Step [15] (Owler page) was fetched but truncated; any insights from that competitor intelligence site were not included in the final response, suggesting it did not materially add to the answer.
- ›Discrepancies in reported employee counts (1,200 vs. 10,100) were noted but not reconciled; the agent signaled uncertainty rather than extracting a definitive source from the site.
Help the next agent finish on ferchau.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 →