giantparticle.com
success
Claude Code
intent

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

23steps
92.0sduration
$1.1166cost
162,892tokens
27 steps4 reasoning steps10 searches
home
docs
/services
/work
/contact
/projects
search
search
search
docs
sitemap
robots.txt
search
/projects
search
/about-us
/about-us
/giantparticle
search
search
search
search
search
85%
on-site discovery
23%
reliability
46%
link following
path origin
  • previous resource46%
  • web search15%
  • prior knowledge31%
  • other8%
insight

The agent gathered a partial understanding of Giant Particle by retrieving the homepage and a Dribbble profile, but encountered a nearly inaccessible website—most navigational URLs returned 404s, and critical information like pricing, team details, and portfolio case studies could not be fetched directly. The agent compensated heavily by inferring positioning from the homepage meta description and tagline, then assembling a plausible business model from web search results it could not directly verify. The site is poorly agent-navigable: no pricing page, no structured data, no accessible portfolio or about page, and no clear service package definitions.

  • ›Step [1] (homepage) yielded only the meta description ('independent design studio working with startups across brand, growth and product') and tagline ('Startups with better design win')—minimal content for a full assessment. No pricing, team info, or detailed service descriptions appeared in the HTML.
  • ›Step [19] (Dribbble) was fetched as an external proof of work but returned only boilerplate Dribbble page scaffolding, not actual portfolio content that could be parsed.
  • ›Steps [2–7, 12–15] all returned 404s: /pricing, /about, /services, /work, /contact, /about-us, /projects, /sitemap.xml. The site either uses a single-page app with hash routing, or has a deliberately minimal public surface. Search results repeatedly cited /about-us and /projects URLs, but these do not resolve, suggesting stale indexing or a site restructuring.
  • ›The agent relied on web search snippets (steps [10, 11, 18, 21, 23–25]) to infer services, positioning, and competitive landscape, but those snippets themselves were not directly accessed—they were search result titles and metadata, not full page content. The agent then cited these URLs as sources in the final response even though it never successfully fetched them.
  • ›No pricing information exists anywhere on the site or in searchable form. The agent correctly flagged this as a major gap and noted the contact-for-quote model, but had to infer engagement model and price range from comparison with other agencies rather than from Giant Particle's own disclosures.
  • ›The site provides no structured data (schema.org, JSON-LD), no API documentation, no public case studies, and no team bios—critical signals for agent trust and verification. The final answer is largely an educated guess built from the tagline, meta description, and LinkedIn/Dribbble breadcrumbs.

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