sullivannyc.com
success
Claude Code
intent

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

21steps
81.2sduration
$1.0262cost
237,565tokens
31 steps10 reasoning steps8 searches
home
docs
docs
home
/work
search
/financial-services
/work/capital-group
docs
search
journeymapping.home
search
search
search
/work/insight-partners
search
search
/services
/ideas
search
/contact
77%
on-site discovery
77%
reliability
31%
link following
path origin
  • previous resource31%
  • web search23%
  • prior knowledge38%
  • other8%
insight

The agent successfully assembled a comprehensive picture of Sullivan NYC's business—what they do, who they serve, and how they position themselves—by combining direct site fetches with web search context. However, the site itself does not expose pricing or a clearly itemized service menu; the agent had to infer Sullivan's positioning from their homepage copy, case studies, industry vertical pages, and team profiles. The site is moderately navigable but requires substantial inference to fully understand their service model and engagement approach.

  • ›Homepage ([1]) and about page ([3], [10]) contained the core positioning ('brand engagement firm,' 'work with consequence,' focus on complex B2B offerings), but phrased in aspirational language rather than concrete service lines. The agent relied on this conceptual framing and had to synthesize it across multiple pages.
  • ›Industry vertical pages like /financial-services ([13]) and /ideas ([14]) were accessible and showed where Sullivan operates, but did not explain service structure, pricing tiers, or engagement models—the site surface relies on case studies and contact-to-quote rather than transparent pricing or service catalogs.
  • ›Case study pages ([25], [26]) existed and were fetchable but contained only outcome and visual examples, not deliverables or scope documentation. The agent had to reason backward from client names and project outcomes to infer service scope.
  • ›Direct guesses for common B2B service pages (/pricing, /services) returned 404s ([2], [6]), confirming the site does not publish service menus or pricing pages. This forced the agent to rely on inferred positioning from branding pages and search results rather than documented service offerings.
  • ›The agent correctly identified this as a premium, strategy-first consultancy via positioning language and client roster, but could not find evidence of standardized packages, retainer models, or project minimums—all typically hidden behind 'contact us' on high-end consulting sites.

See every agent that visits sullivannyc.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 →