spadework.ai
success
Claude Code
intent

What does spadework.ai do and who is it for? Explain it back to me.

16steps
63.4sduration
$1.0199cost
193,177tokens
26 steps10 reasoning steps6 searches
home
home
docs
/features
docs
search
search
/en/industries
/en
search
search
search
/en/gettingstarted
/en/contact
search
/en/pricing
60%
on-site discovery
80%
reliability
20%
link following
path origin
  • previous resource20%
  • web search40%
  • prior knowledge40%
insight

The agent successfully assembled a comprehensive explanation of Spadework AI by combining homepage metadata, direct site navigation, and web search discovery. The site was moderately navigable—core positioning and feature names were accessible via homepage and targeted page fetches, but specific pricing details remained opaque and required the agent to acknowledge a gap. The agent worked around incomplete HTML responses and 404 errors by using prior knowledge and search results to fill in product positioning and differentiation.

  • ›Steps [1], [14] (homepages in Dutch and English) provided meta descriptions that clearly stated the core value proposition ('Automate your Recruitment Workflow', 'Transform CVs', 'keep your ATS automatically up to date'), which anchored the agent's explanation of what Spadework does.
  • ›Step [5] returned a pricing page title but the response body was truncated (4400+ chars cut off), preventing direct extraction of pricing tiers or costs. The agent had to acknowledge in the final response that 'specific dollar amounts aren't prominently displayed' and suggested contacting sales—this is accurate to what was actually fetchable.
  • ›Steps [7], [13], [22], [24] (About, Industries, Contact, product-specific pages) were either direct guesses or discovered via search results, not linked from the homepage. The site's navigation structure is not self-evident; the agent had to conduct searches to find pages like /industries and /products/up-to-databaser.
  • ›Step [24] search results exposed product names ('CV-Parser', 'Up-to-databaser', 'CV Transformer') and specialized use cases ('executive search') that the agent then cited as sources, indicating the search snippets themselves contained positioning language the agent used to explain differentiation.
  • ›Multiple 404s on /features and /gettingstarted (steps [6], [21]) suggest the site structure is either incomplete or language-dependent. The agent correctly noted this in the final response as 'confusing or missing elements'.
  • ›The agent relied heavily on prior knowledge (40%) and web search (40%) to construct the final answer, indicating the website alone provided incomplete semantic context for differentiation and pricing—a sign of lower agent-readiness despite successful task completion.

Help the next agent finish on spadework.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 →