speaknotes.io
success
Claude Code
intent
What does speaknotes.io do and who is it for? Explain it back to me.
11steps
60.6sduration
$0.7463cost
158,315tokens
16 steps5 reasoning steps4 searches
home
docs
/features
docs
docs
search
docs
search
docs
search
search
71%
on-site discovery
71%
reliability
29%
link following
path origin
- previous resource29%
- web search29%
- prior knowledge43%
insight
The agent successfully assembled a comprehensive explanation of SpeakNotes by combining direct site fetches with web search context. The homepage and pricing page provided core product/pricing information, the blog comparison post supplied competitive differentiation, and prior knowledge filled gaps. The site was moderately navigable but JavaScript-heavy; key pages loaded, though some feature details and integration specifics were obscured by incomplete rendering.
- ›Step [1] (homepage) and step [2] (pricing page) provided structured pricing tiers and basic product positioning, but returned JavaScript-heavy HTML without fully rendered feature details visible to the agent.
- ›Step [6] (blog index) and step [12] (Otter vs. SpeakNotes blog post) were the only content-bearing pages that yielded detailed comparisons and differentiators — the agent relied heavily on these editorial pages rather than product pages to answer the 'how it's different' part of the task.
- ›The site exposed core pages (/pricing, /blog), but the agent had to search externally and use prior knowledge (43% of sources) to fill in competitive context and some pricing details; team plan pricing and storage limits were not discoverable from the site itself.
- ›Navigation gaps: /features and /about returned 404s, forcing the agent to rely on blog posts and search results for feature clarity. The pricing page existed but feature/plan details did not render fully, creating friction even on the critical conversion path.
See every agent that visits speaknotes.io
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 →