samcarlton.com
success
Claude Code
intent

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

19steps
44.7sduration
$0.3944cost
234,362tokens
32 steps13 reasoning steps
home
home
/_markdown/index.md
/ai-app-rescue
/_markdown/ai-app-resc…
/engineering-partner
/_markdown/engineering…
/workflow-pilot
/_markdown/workflow-pi…
/_markdown/projects.md
/_markdown/portfolio/r…
/_markdown/contact.md
docs
/_markdown/pricing.md
/_markdown/about.md
sitemap
sitemap
/_markdown/testimonies…
/_markdown/agent-reada…
100%
on-site discovery
95%
reliability
68%
link following
path origin
  • previous resource68%
  • prior knowledge32%
insight

The agent successfully understood Sam Carlton's core positioning, three main service offerings, and target audience by reading the site's markdown pages. However, pricing information was incomplete and misaligned—the site publishes two different pricing structures (legacy Web Experience Audit at $18k vs. unlisted custom quotes for the main services), forcing the agent to flag confusion rather than provide a definitive answer. The site was navigable but pricing transparency was a significant gap.

  • ›Steps [5, 11, 12, 13] provided the core narrative: the homepage markdown listed three services (AI App Rescue, Engineering Partner, Workflow Pilot), and dedicated markdown pages for each described the use cases, target personas, and workflow. This content was machine-readable and well-structured.
  • ›Step [21] (pricing page) returned two tiers ($18,000 for Web Experience Audit, $1,500 for Site Diagnostic, $500 for Consulting Call) that do not map to the three main services—no pricing listed for AI App Rescue, Engineering Partner, or Workflow Pilot. The agent had to conclude these are custom-quoted, unpriced engagements.
  • ›Step [28] (testimonies) provided social proof but was dated (2013+ web design work), not recent validation of the new AI/workflow services—the agent noted this gap in the final response.
  • ›The site exposes content via markdown artifacts (/_markdown/*.md endpoints), which the agent discovered by prior knowledge (32% of fetches) and inference. This is agent-friendly but required the agent to know or guess the artifact pattern—not self-evident from HTML alone.
  • ›The agent correctly identified that portfolio projects ([19]) demonstrated past building work but did not illustrate deliverables from the consulting services, leaving a case-study gap that would help buyers understand engagement scope and outcome.

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