ora
shopwave.com
success
Claude Code
intent

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

15steps
63.2sduration
$0.7990cost
123,851tokens
18 steps3 reasoning steps5 searches
home
/company
docs
/faq
/case-studies
help.home
search
search
/products
/products/point-of-sale
/solutions
search
search
/products/connect
search
60%
on-site discovery
90%
reliability
40%
link following
path origin
  • previous resource40%
  • web search40%
  • prior knowledge20%
insight

The agent successfully assembled a comprehensive explanation of Shopwave by combining fragments from the site's marketing pages with prior knowledge and web search. The site's content was scattered across multiple pages with heavy JavaScript rendering, making it difficult to extract complete information without inference. Key gaps—particularly pricing details and competitive positioning—were not directly available on the site and required external research to answer fully.

  • The homepage [1] established Shopwave's core positioning as a 'Merchant Orchestration Engine' but did not explain what that means or how it differs from POS competitors; the agent had to infer this from searching and cross-referencing multiple pages.
  • Pricing was completely inaccessible on the site: /pricing returned a 404 [3], forcing the agent to search external review sites (Merchant Machine, SoftwareWorld) to retrieve specific pricing tiers (£99/$125/€115 per terminal/month). This is a critical gap for a discovery-evaluation task.
  • Products and solutions pages [10, 11, 12, 15] existed but were JavaScript-heavy SPA pages; the fetched HTML contained meta descriptions and structure but not the detailed feature lists or module breakdowns needed to fully explain 'what they do.' The agent relied on prior knowledge to synthesize these.
  • The company page [2] and FAQ [4] were accessed but did not surface in the final response's citations, suggesting they contained generic messaging rather than substantive product or positioning details.
  • The site does not publish direct competitor comparisons or a feature matrix. The agent had to infer differentiation (orchestration vs. POS-first, offline-first design, Quantum Pricing) by reading between product page fragments and combining with external knowledge.
  • Case studies page [5] was fetched but not cited, indicating it may have contained customer examples rather than the 'what/who/how/why' definitions needed to explain the platform fundamentally.

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 →