What does steno.com do and who is it for? Explain it back to me.
- previous resource20%
- web search50%
- prior knowledge30%
The agent successfully assembled a comprehensive explanation of Steno's business model, target market, and differentiation by fetching the homepage, about page, and several service/technology pages, supplemented by web search results. However, the task was only partially satisfied on pricing: Steno's website does not publicly display transparent pricing information, forcing the agent to rely on inference (rate cards mentioned in help docs, DelayPay details from a dedicated page) and external sources rather than direct disclosure. The site is navigable but fragmented—key information is scattered across separate pages with no single overview, and the most critical pricing data is deliberately withheld from public view.
- ›The homepage [1] and about page [4] provided positioning and business context ('built by lawyers'), but did not expose pricing, service offerings, or competitive differentiation—these had to be found by guessing URLs like /services/court-reporting [10], /technology/firm-dashboard [11], /technology/transcript-genius [14], and /services/delaypay [16].
- ›Pricing was intentionally opaque: the site does not publish per-page rates, tiers, or a public rate card. The agent found references to 'rate cards' and DelayPay financing, but exact pricing requires contacting the company. This is typical in court reporting but makes Steno harder to evaluate without human contact.
- ›The site's information architecture is scattered—no centralized 'how it works' or 'pricing & plans' page exists. The agent had to construct the answer from fragments: court reporting page [10], dashboard page [11], Transcript Genius page [14], and DelayPay page [16], none of which links to the others in an obvious hierarchy.
- ›Web search [8, 9, 13, 15] was essential to discover service pages and external validation (G2, funding news, Above the Law), suggesting the site's internal navigation and discoverability are weak. The agent used prior knowledge to guess /pricing, /solutions, and /platform URLs, all of which returned 404s.
- ›The final response correctly identifies this gap and flags 'no transparent pricing' as a key limitation—the agent did not hallucinate rates but honestly reported what it could not find.
Help the next agent finish on steno.com
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 →