demo.looper.mn
success
Claude Code
intent

What does demo.looper.mn do and who is it for? Explain it back to me.

4steps
43.3sduration
$0.2040cost
17,313tokens
9 steps5 reasoning steps
home
home
home
home
100%
answer from your site
100%
answer efficiency
100%
followed site links
answer sources
  • from this site100%
url discovery
  • given in the task25%
  • followed a link75%
insight

Agent successfully gathered enough information to explain Doowy's core purpose, target market, feature set, and sales approach, but the site offers minimal transparency on pricing and no direct competitor positioning, forcing the agent to infer differentiation from feature descriptions and positioning language rather than explicit comparisons.

  • ›All four fetches returned the same URL (demo.looper.mn/) with different response summaries, suggesting the agent re-fetched the homepage multiple times hoping for different sections. The site appears to be a single-page or heavily JavaScript-driven application where link navigation may not have been exposed or discoverable — 75% of discovered URLs came from following links within fetches, but the agent relied on URL memory (25%) to access content.
  • ›Pricing is intentionally hidden behind a consultation wall (contact-us funnel). The site provides no public pricing tiers, making it impossible for an agent to complete a cost-benefit analysis without human intervention. This is a deliberate design choice that creates a hard barrier to autonomous evaluation.
  • ›The site is in Mongolian and English, but Mongolian text dominates feature descriptions. The agent's final response notes language as a limiting factor, suggesting the fetched content may have been partially machine-translated or the Mongolian sections were unavailable in full clarity.
  • ›No competitor comparison exists on the site. The agent had to infer differentiation from feature lists (GPS/WiFi/QR attendance, customizable workflows, mobile apps) and value-proposition phrasing ('professional partner'), not from explicit competitive positioning. This required the agent to reason about what 'consolidation' means in ERP context using external knowledge.
  • ›The site surfaced no case studies, customer references, or deployment examples. The agent could describe what Doowy claims to do, but not validate product-market fit or provide proof points that would strengthen the 'explain to someone else' goal.

Help the next agent finish on demo.looper.mn

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 →