ora
asana.com
success
Claude Code · Haiku 4.51:02
intent

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

8steps
62.7sduration
$0.7696cost
69,085tokens
13 steps5 reasoning steps5 searches
home
docs
/product
search
search
search
search
search
100%
on-site discovery
100%
reliability
67%
link following
path origin
  • previous resource67%
  • prior knowledge33%
insight

The agent successfully assembled a comprehensive explanation of Asana by fetching the homepage, pricing page, and product page directly from asana.com, supplemented with web search results for competitive positioning and audience insights. The site's HTML was dynamically rendered (Next.js) and difficult to parse, so the agent relied heavily on prior knowledge and search results to fill gaps; however, the core information about what Asana does, pricing tiers, and target customers was extracted or validated through the direct fetches and cited sources.

  • Steps [1], [3], and [4] were cited as sources in the final response, but the HTML responses were truncated and dynamically rendered, making them difficult to extract structured content directly—the agent appears to have used prior knowledge to reconstruct pricing and feature details rather than parsing the actual page content.
  • Web search steps [6–9, 11] provided the bulk of usable information (Cirface, Spendhound, Vendr, Monday.com comparison, MatrixBCG target audience, Asana AI Teammates overview), yet only the Asana URLs themselves were cited, not the search results, suggesting the agent used search to validate and fill gaps but attributed answers back to primary sources.
  • The site exposes pricing, product features, and use cases across multiple pages (/pricing, /product, /uses/work-management, /product/ai/ai-teammates), but the agent could not confirm exact feature placement across tiers or AI pricing inclusion from the fetched HTML alone—this required inference and external sources.
  • Asana's positioning around 'human-agent teams' and AI Teammates appears in search results and inferred positioning, but the agent flagged ambiguity about whether this is a core differentiator or marketing language, indicating the site's messaging on this front was not clearly machine-readable.
  • The agent identified specific gaps (AI pricing clarity, user role/license types, integration costs) that were not resolved by any fetched page, demonstrating where the site lacks transparent, structured information for machine comprehension.

Want to run your own?

Join the waitlist for early access to point your own agents at any domain, with the intents you choose.

or talk to us about agent readiness →