heykompa.com
success
Claude Code
intent

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

18steps
84.7sduration
$1.0705cost
218,658tokens
30 steps12 reasoning steps7 searches
home
docs
/features
/features
search
/es
docs
docs
search
search
search
search
docs
/help
search
home
/faq
search
100%
on-site discovery
91%
reliability
55%
link following
path origin
  • previous resource55%
  • prior knowledge45%
insight

The agent successfully assembled a comprehensive overview of Hey Kompa by fetching the homepage, pricing, features, about, and help center pages. The site surfaced most key information (what it does, pricing tiers, target audience, WhatsApp-first positioning) in meta descriptions and navigable pages, but the agent had to work around incomplete documentation—notably, supported social platforms were never explicitly listed anywhere on the site, forcing the agent to note this as a significant gap. The site is moderately agent-ready for discovery but lacks structured detail on critical features.

  • ›Steps [1], [3], [4], [6], [23] returned complete meta descriptions and page titles that directly answered 'what,' 'pricing,' 'features,' and 'who it's for'—these were the primary sources of the final answer. Step [3] (pricing page) clearly stated the three tiers ($49, $99, $199) and trial details. Step [1] (homepage) established the core value proposition (WhatsApp-managed social media, approval-based).
  • ›The site's navigation structure is logical and discoverable—pricing, features, about, and help pages all exist at predictable URLs and are reachable from the homepage. However, the site does NOT explicitly list supported social platforms (Instagram, Facebook, TikTok, LinkedIn, etc.), despite this being a critical feature question. The agent searched for this information [steps 14, 18, 21] but found no site-level answer, only generic web results, indicating the site actively hides or omits this detail.
  • ›The site is poorly structured for machine-readable feature extraction. Metadata and page titles are descriptive but vague ('publishes everywhere,' 'replies to DMs'). Step [20] (help center) was fetched but its response was truncated in the trajectory—the full FAQ structure was not available to the agent. Specific feature details (team multi-user support, autonomous vs. alert-only DM handling, analytics depth) are conspicuously absent from all fetched pages. The agent had to explicitly call these out as confusions, indicating the site prioritizes marketing narrative over operational clarity.

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