puzzlesandprofits.com
partial
Claude Code
intent
What does puzzlesandprofits.com do and who is it for? Explain it back to me.
20steps
96.5sduration
$1.2390cost
206,060tokens
31 steps11 reasoning steps10 searches
home
/how-we-help
docs
/contact
search
/services-4
/pricing-plans/list
search
search
search
search
/post/a-people-first-a…
search
search
/product-page/the-comp…
search
search
search
/pricing-plans/list
docs
60%
on-site discovery
100%
reliability
40%
link following
path origin
- previous resource40%
- web search40%
- prior knowledge20%
insight
The agent assembled a partial but usable picture of Puzzles & Profits by combining meta tags from the homepage, web search snippets, and one discovered product page, but could not access detailed pricing, service tiers, or team information because the site is built as a React SPA with dynamically loaded content. The agent correctly identified what the company does (AI strategy and governance for mission-driven nonprofits) and its positioning, but had to acknowledge gaps in pricing certainty and specific service package details.
- ›Step [1] (homepage) returned only static HTML with meta tags and boilerplate; the actual content rendering happens client-side in React, making the response non-content-bearing for details beyond the tagline and description.
- ›Steps [8], [17], and [23] (web searches) returned URLs and snippets that pointed the agent to pages like /services-4, /pricing-plans/list, and the product guide page, but when those URLs were fetched (steps [10], [11], [25], [28]), they also returned only the same generic React shell without rendered content—a classic SPA anti-pattern for agent discoverability.
- ›The agent successfully inferred core business positioning ('mission-driven organizations,' 'human-first AI,' 'nonprofits and startups') from the homepage meta description and blog post titles visible in search results, but had to explicitly state it could not confirm pricing ranges or service tiers because the pricing page returned no structured data.
- ›The site surface area is hostile to agent navigation: no structured data (schema.org), no pricing table in HTML, no team bios in fetch responses, and critical content gated behind client-side rendering. The agent had to rely on prior knowledge and web search context to construct a coherent narrative rather than reading it directly from the site.
- ›The agent cited four sources in its final response, but only [1] was a direct site fetch; [8], [17], and [23] were search results that merely pointed to pages rather than containing content. This indicates the agent backfilled gaps using search artifact snippets and inferred positioning rather than site-native content.
Help the next agent finish on puzzlesandprofits.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 →