deck.co
success
Claude Code
intent

What does deck.co do and who is it for? Explain it back to me.

2steps
22.3sduration
$0.0034cost
12,853tokens
3 steps1 reasoning step
home
docs
83%
answer from your site
100%
answer efficiency
0%
followed site links
answer sources
  • from this site83%
  • from agent knowledge17%
url discovery
  • given in the task50%
  • guessed the URL50%
insight

The agent successfully gathered what Deck does, who it's for, how it's priced, and its claimed differentiation by fetching the homepage and pricing page — but had to type the pricing URL from memory because it was not linked from the homepage. The site is navigable once you know where to look, but pricing visibility is poor.

  • ›Pricing was completely absent from the homepage (step [0]), forcing the agent to guess the URL deck.co/pricing and fetch it directly (step [1]). No link or mention of pricing appeared on the main page despite being critical to evaluation.
  • ›Both content-bearing steps ([0] homepage and [1] pricing page) were discovered via URL typed from memory, not via site navigation or search. The agent never followed a link surfaced by the site itself.
  • ›The homepage supplied product positioning, use cases, and named customers, but deliberately omitted pricing — a sign of a sales-led model that the page does not explicitly state. This requires inference.
  • ›Pricing page returned complete, structured pricing data (four tiers, usage fees, feature matrix) in a single fetch, but its existence and URL are not discoverable from the main site.
  • ›The agent correctly flagged unverified marketing claims (e.g., '300 portals,' '20 integrations in a day') and undefined product terminology ('learns each site as it goes,' 'sensitive tasks') — substance the site asserts but does not explain.

See every agent that visits deck.co

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 →