releaf.co.uk
success
Claude Code
intent
What does releaf.co.uk do and who is it for? Explain it back to me.
9steps
50.7sduration
$0.6525cost
139,065tokens
16 steps7 reasoning steps3 searches
home
/pages/pricing
docs
search
docs
search
/how-it-works
docs
search
50%
on-site discovery
67%
reliability
33%
link following
path origin
- previous resource33%
- web search50%
- prior knowledge17%
insight
The agent successfully assembled a comprehensive explanation of Releaf's business model, pricing, and market positioning by combining web search results with targeted page fetches. However, the site's heavy JavaScript rendering meant most direct fetches returned unreadable HTML, forcing the agent to rely on search result snippets and prior knowledge (50% web search, 33% artifact/context) rather than direct site content. The core information was findable but not directly parseable from the website itself.
- ›Direct navigation to key pages (/pricing, /about, /how-it-works) failed initially or returned JavaScript-heavy HTML that couldn't be parsed; web search results for the same pages succeeded, indicating the site publishes the right URLs but renders content client-side.
- ›The agent successfully extracted pricing tiers (£9.99 initial, £19.99 follow-up, £39.99/month Releaf+, £7.99/gram products), condition coverage (60+ conditions), eligibility (9/10 approval rate, prior treatment requirement), and competitive positioning from search snippets and blog post references rather than from structured page content.
- ›Critical information gaps remain unfilled: the 'Cannabis Card' feature mentioned on the homepage, full product catalog/strains, exact prescription-to-delivery turnaround, and detailed eligibility documentation requirements could not be retrieved because the site does not serve this in a machine-readable static form.
- ›The agent cited 7 URLs in its final sources, but only 3 were direct Releaf pages successfully fetched ([9] pricing, [12] blog, [14] how-it-works); the remainder were either external comparison/review sites or search result titles that provided context rather than primary content.
- ›Site navigation friction was high: predictable routes (/about, /pages/pricing) returned 404s, forcing the agent to discover correct URL patterns through web search before fetches would succeed.
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 →