The agent successfully gathered enough information to explain armslength.ai's core business, target audience, and positioning, but encountered significant gaps in pricing transparency and competitive differentiation. The homepage, pricing page, and subpages (about-us, ai-benchmarks, tp-os, transfer-pricing-software, blog) were discoverable and loaded cleanly, but the pricing page itself did not contain granular tier details, forcing the agent to rely on prior knowledge and web search to fill gaps.

• ›Step [1] (homepage) and steps [12–14] (subpages: tp-os, ai-benchmarks, transfer-pricing-software) returned structured content that clearly positioned the product as a transfer pricing platform with two modules (benchmarking and documentation), reducing time by up to 80%, and targeting Big 4 / mid-market firms. The site was navigable via the sitemap [8].
• ›Step [2] (pricing page) returned a valid 200 response but did not expose granular pricing tiers, feature matrices, or module-specific costs in a machine-readable form. The agent noted the €469/month floor but could not extract tier details from the fetched HTML, indicating the pricing page likely relies on client-side JavaScript rendering or is intentionally vague.
• ›Steps [16, 18, 19, 21] were web searches that surfaced competitor context (TPGenie, ONESOURCE, Aibidia, t0) and team/founder credibility (Borys Ulanenko's 11 years in TP), but these came from external sources, not the site itself—suggesting armslength.ai does not explicitly document competitive positioning or founder narrative on its owned pages.
• ›Step [6] (about-us page) was discoverable but returned metadata-heavy HTML; the agent could infer the company uses practitioners and has team photos, but detailed mission/vision/values were not extracted from the response snippet, suggesting minimal structured copy or client-side rendering.
• ›The agent worked around missing pricing details by flagging the gap as 'confusing' and noting a `/calculate-savings` page exists but was not accessible in the crawl, indicating some features are either protected, require interaction, or are dynamically rendered.
• ›Site is moderately agent-ready: top-level product story is surfaced on the homepage and subpages via standard URLs, but critical commercial details (pricing tiers, integrations, data sources, ROI metrics) are either absent, buried, or require client-side interaction.