cleverfranke.com
success
Claude Code
intent
What does cleverfranke.com do and who is it for? Explain it back to me.
16steps
64.0sduration
$0.9229cost
195,384tokens
25 steps9 reasoning steps6 searches
home
/work
/services
docs
docs
/contact
search
/cf-part-of-adc-consul…
/company/clever-franke
search
search
/profile/clever-franke
search
search
/careers
search
60%
on-site discovery
80%
reliability
20%
link following
path origin
- previous resource20%
- web search40%
- prior knowledge40%
insight
The agent successfully assembled a comprehensive overview of CLEVER°FRANKE by fetching key pages (homepage, services, about, contact, and ADC acquisition announcement) and supplemented with web searches. The site is well-structured and navigable for discovery, clearly surfacing what they do, who they work with, and their recent strategic move, but critically fails to publish pricing information or engagement model details—forcing the agent to acknowledge a significant gap and work around missing information rather than retrieve it.
- ›Steps [1], [3], [4], [5] directly yielded core positioning: the homepage meta descriptions and page titles established their identity as a 'data design and technology consultancy' creating 'data-driven experiences'; the /services page cataloged specific deliverables (dashboards, narratives, design systems); /about confirmed scale (~50 people, Utrecht) and recent ADC acquisition. These were well-structured, accessible pages.
- ›Step [13] (ADC acquisition announcement) was critical for understanding their current positioning—the site published this news prominently, making it discoverable and directly used in the final answer, showing strong transparency about a major structural change.
- ›Step [8] (contact page) confirmed they operate on a project-based, custom-quote model ('contact us for engagement') rather than publishing tiered pricing, revealing a deliberate choice not to expose pricing. The agent had to acknowledge this as a confusing absence rather than a retrieval failure.
- ›The site's visual design and meta descriptions are polished (rich Open Graph metadata, award mentions in search results), but the navigational architecture does NOT include a /pricing endpoint or FAQ explaining engagement models—steps [7] and [19] encountered 404 and 403 respectively when probing for price/Clutch pages. The agent had to rely on web search and prior knowledge to fill gaps.
- ›Web searches [10], [11], [16], [17], [20], [23] were routers that pointed to external sources (Crunchbase, LinkedIn, Communication Arts, Rocketreach, job boards) rather than content-bearing sources on the site itself—the agent cited LinkedIn and Crunchbase in its final response as sources, but these were not content-bearing for the task (they confirmed headcount range and company profile, not core differentiators or pricing).
- ›The site is agent-ready for identity and discovery (clear value prop, visible work examples, client list, team size) but NOT for payments or engagement clarity—there is no machine-readable pricing structure, engagement model FAQ, or proposal process exposed to the agent.
Help the next agent finish on cleverfranke.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 →