dotruby.com
success
Claude Code
intent

What does dotruby.com do and who is it for? Explain it back to me.

20steps
96.1sduration
$1.4583cost
152,838tokens
30 steps10 reasoning steps13 searches
home
/services
docs
docs
search
search
search
/work
search
search
docs
search
search
search
search
search
/company/dotruby
search
search
search
86%
on-site discovery
71%
reliability
43%
link following
path origin
  • previous resource43%
  • web search14%
  • prior knowledge43%
insight

The agent successfully assembled a comprehensive overview of DotRuby by fetching their homepage, about page, work portfolio, and LinkedIn profile—but had to work around significant gaps in published information. The site lacks pricing pages, detailed engagement models, and concrete service descriptions, forcing the agent to infer positioning from sparse, philosophy-focused copy and portfolio work. While the agent delivered a usable answer about what DotRuby does and who it's for, it explicitly flagged critical missing information (pricing, team size, engagement model, product offerings) that would normally be discoverable on a client-facing business site.

  • ›Step [1] (homepage) and step [5] (about page) returned only truncated HTML snippets—the agent could not retrieve full text content, indicating either client-side rendering, JavaScript-heavy layout, or content delivery that broke the fetch. The agent had to piece together understanding from metadata titles and prior knowledge rather than actual page body text.
  • ›Steps [11] (work/portfolio) and [24] (LinkedIn) were the only truly content-bearing fetches, providing client names and confirmation of agency positioning. The portfolio page returned the same truncated HTML as other pages, suggesting a systematic site navigation or rendering barrier.
  • ›No pricing, services, engagement model, or team composition information exists at discoverable URLs (/pricing, /services returned 404s in step [3] and [4]). The agent resorted to 12 follow-up web searches, none of which returned DotRuby-owned pages with pricing or detailed service definitions—only external directories and comparison sites.
  • ›The agent's final answer relies heavily on inference and philosophical positioning language ('pragmatic professionalism,' 'shipping-focused') extracted from minimal copy, rather than explicit capability or pricing statements. This forced reliance on interpretation rather than fact is a strong signal that the site does not publish machine-readable business information.
  • ›The site's minimalist marketing approach (described by the agent as 'lean and understated') actively obscures information a prospect or evaluation agent would typically expect: no case study details, no testimonials, no service menu, no pricing tiers. This is intentional brand positioning but creates friction for both human and AI evaluation.
  • ›The agent correctly identified that third-party review sites (Clutch, GoodFirms) do not list DotRuby, removing an alternative information channel that often surfaces for agencies. This further narrows discoverable data to the site itself and LinkedIn, both of which returned incomplete or inaccessible responses.

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