craigjamieson.com
success
Claude Code
intent

What does craigjamieson.com do and who is it for? Explain it back to me.

21steps
134.5sduration
$1.6331cost
191,458tokens
35 steps14 reasoning steps14 searches
home
search
docs
/now
search
search
/freelance-creative-di…
/in-good-company
search
/in/craig-jamieson
search
search
/contact
search
search
search
search
search
search
search
search
14%
on-site discovery
57%
reliability
0%
link following
path origin
  • web search86%
  • prior knowledge14%
insight

The agent assembled a working understanding of Craig Jamieson's positioning and services by combining web search snippets and a handful of successfully fetched article pages, but had to work around a largely inaccessible website (homepage timeout, database errors on key pages) and missing critical commercial information. The site surfaces positioning and philosophy unevenly through blog content, but does not publish pricing, engagement models, or clear value propositions in any machine-readable or readily fetchable form.

  • ›Step [11] (Freelance Creative Director Success article) and [12] (In Good Company article) were the only substantive page fetches that succeeded; both returned blog content framing his philosophy ('creative direction shapes the work, creative director shapes the people') rather than service offerings or pricing.
  • ›Steps [24], [25], [30] — web search snippets — supplied most of the semantic understanding (team building, creative excellence, leadership coaching focus) but the snippets were inferred from page titles and meta descriptions, not from fetched page content that explicitly stated these.
  • ›The site's homepage, About page, and Now page all failed to fetch (timeouts in steps [1], [5]; 500 error in step [6]), forcing the agent to rely entirely on search results and two blog articles rather than authoritative landing pages.
  • ›Pricing, engagement models, case studies, and CR—G brand meaning are entirely absent from any publicly fetchable content; the agent could not find these even through targeted searches (step [20]), confirming the site does not publish commercial fundamentals.
  • ›The Contact page (step [22]) fetched successfully but returned only boilerplate HTML headers — no actual contact form, CTA, or engagement instructions were visible in the response snippet.
  • ›The agent cited sources in its final response (About, Homepage, three articles, LinkedIn, Contact), but only 2 of those were successfully fetched during the run; the remainder were cited from search result titles or inferred positioning, not from verifiable page content.

Help the next agent finish on craigjamieson.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 →