ashling.ai
success
Claude Code
intent
What does ashling.ai do and who is it for? Explain it back to me.
6steps
33.9sduration
$0.3664cost
19,625tokens
10 steps4 reasoning steps1 search
home
/solutions
docs
docs
search
/partners
86%
answer from your site
40%
answer efficiency
50%
followed site links
answer sources
- from this site86%
- from agent knowledge14%
url discovery
- given in the task20%
- followed a link40%
- found via web search20%
- guessed the URL20%
insight
Agent successfully retrieved and synthesized Ashling's core positioning, service model, target market, and competitive advantages directly from their homepage and partners page. Site navigation was sparse (most standard URL paths returned 404s), forcing reliance on the homepage's comprehensive overview and one partners page; pricing remained intentionally opaque with no published rates.
- ›Homepage [1] was content-rich and self-contained: it delivered the five-phase service model, target industries, client scale, revenue growth, certifications, and accelerators without requiring navigation to subpages. The site did not surface dedicated pricing, solutions, or about pages (all 404s [3–5]), indicating a minimal information architecture.
- ›Partners page [8] was essential for understanding differentiation—it provided the tier-specific partnership details (UiPath Diamond, Celonis Gold/2024 Partner of the Year, Blue Prism Global Partner of the Year 2024) that the homepage mentioned only in passing. This page had to be discovered via web search, not site navigation.
- ›Pricing absence is a site design choice, not a retrieval failure: the homepage explicitly states 'contact their team directly,' and no pricing page exists. This is a deliberate enterprise sales gate, making it impossible for the agent to retrieve what the domain does not publish.
- ›Web search [7] supplied competitor context (Accenture, Deloitte, Cognizant, PwC) and company financials ($43.4M revenue, 272 employees) that were not on the site. The agent correctly attributed these to external sources rather than claiming site content.
- ›Agent had to fill gaps around deployment timeline and case study depth from model memory [final response under 'What I Couldn't Find']. These are reasonable gaps, not claims about Ashling's actual capabilities, so they do not misrepresent the site.
See every agent that visits ashling.ai
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 →