dials.co
partial
Claude Code
intent

What does dials.co do and who is it for? Explain it back to me.

26steps
107.0sduration
$1.6525cost
424,040tokens
43 steps17 reasoning steps12 searches
home
docs
docs
home
search
search
search
home
reference.home
search
/journal
search
search
search
/rolex
/brands
/help
sitemap
robots.txt
search
search
/api
/api/brands
search
search
search
86%
on-site discovery
36%
reliability
21%
link following
path origin
  • previous resource21%
  • web search14%
  • prior knowledge64%
insight

The agent could not fully satisfy the task of explaining dials.co to someone else. It retrieved the homepage meta description and a journal page, discovered competing watch reference databases (WatchBase, WatchCompared, Grail Watch Reference) through web search, and inferred positioning based on the standardized spec model mentioned in the site's own tagline. However, it could not find pricing, company/founder information, monetization model, or detailed features—all critical gaps that prevent a complete explanation. The site is poorly navigable for discovery-evaluation: it lacks informational pages (about, pricing, features), appears minimally indexed in search results, and relies on a React SPA that hides navigation structure.

  • ›Steps [1] and [5] returned only meta descriptions and HTML shells; the homepage and journal page responses were truncated and contained no readable content body, making direct site content inaccessible to the agent.
  • ›Steps [38–39] and [41] were discovery-layer attempts: the agent found that WatchBase (403 blocked), Grail Watch Reference, and WatchCompared exist as competitors, but had to infer Dials' positioning from the brief meta description ('described to one specification — case, calibre, dial and bracelet') rather than from product marketing on the Dials site itself.
  • ›The site does not publish critical information (pricing, company identity, monetization, feature details) in a discoverable or fetchable form; the agent's final answer explicitly flags these gaps and resorted to assembled inferences from the tagline and competitive context rather than from Dials' own content.
  • ›Multiple guessed URLs (/about, /pricing, /brands, /help, /sitemap.xml, /api/*) all returned 404s or redirects to the homepage, indicating poor information architecture and no human-readable info pages to bridge the agent's understanding.
  • ›The agent's final response cites Grail Watch Reference, WatchCompared, and The Watch Pages as sources—these are NOT from the Dials site itself, but from web search results [41], confirming that the agent could not answer the task from Dials' own content.

Help the next agent finish on dials.co

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 →