stage-app.valuesalignment.com
partial
Claude Code
intent
What does stage-app.valuesalignment.com do and who is it for? Explain it back to me.
21steps
116.8sduration
$1.2983cost
280,249tokens
22 steps1 reasoning step9 searches
home
docs
docs
docs
/api/pricing
/features
search
/culture-development/v…
home
search
/values-alignment-index
search
search
search
search
search
home
home
home
search
search
92%
on-site discovery
92%
reliability
67%
link following
path origin
- previous resource67%
- web search8%
- prior knowledge25%
insight
The agent worked around an inaccessible staging environment to assemble a reasonable product overview from the production site and related marketing pages. Stage-app.valuesalignment.com did not render (empty React shell), so the agent pivoted to valuesalignment.com and &Evolve's main domain, successfully explaining what the Values Alignment Index does, who it's for, basic positioning, and how it differs from competitors — but pricing details remained incomplete and the actual application interface was never visible.
- ›Stage-app.valuesalignment.com returned only a bare React skeleton with no rendered DOM content (steps [0–3]), making the staging environment completely non-navigable for content extraction. The agent correctly recognized this as a development/staging environment and pivoted to production URLs.
- ›Production site (valuesalignment.com, steps [4], [6], [11]) and &Evolve marketing pages (steps [7], [9], [15]) did render but were client-side React apps that returned full HTML with metadata but limited inline content in the fetched HTML payloads. The agent extracted positioning, audience, and framework details from page structure and meta tags rather than from readable body text in the fetches themselves.
- ›Pricing information was explicitly incomplete: steps [4], [6], [11] returned 404 or empty shells when attempting /pricing routes; the agent found only £399 entry-level pricing mentioned in marketing copy, with no tier details, subscription model, or volume pricing visible anywhere on the site.
- ›The agent relied heavily on prior knowledge (25%) and prior artifacts (67%) to construct the final answer, indicating the site did not publish structured, machine-readable product information (no FAQ, pricing table, feature matrix, or API documentation that would aid machine navigation).
- ›Competitor and differentiation information came entirely from web search results (steps [16], [17]) rather than from the product site itself — the site did not provide direct feature-by-feature comparisons, integration details, or assessment mechanics (e.g., time to complete, customization, ATS integrations).
Help the next agent finish on stage-app.valuesalignment.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 →