companion.energy
success
Claude Code
intent
What does companion.energy do and who is it for? Explain it back to me.
9steps
48.7sduration
$0.1012cost
35,447tokens
13 steps4 reasoning steps2 searches
home
/platform
docs
/why
/solutions
search
search
/company/about
/customers
80%
answer from your site
43%
answer efficiency
67%
followed site links
answer sources
- from this site80%
- from agent knowledge20%
url discovery
- given in the task14%
- followed a link57%
- found via web search14%
- guessed the URL14%
insight
The agent assembled a coherent explanation of Companion.energy's platform, target market, and differentiators by fetching the homepage and platform pages directly, then supplemented with external sources (funding announcements, company about page) to triangulate positioning. The site's main pages were navigable and content-rich, but the absence of public pricing details and limited competitive positioning forced reliance on company claims and external reporting.
- ›Steps [1] and [2] provided the core platform description (Prism/Propel dual-component model) and target audience directly from the domain; this was the primary foundation for the explanation.
- ›Pricing remained a critical gap: the /pricing URL returned 404 [step 3], forcing the agent to note 'This is the biggest gap' and report no actual pricing is disclosed—the site itself acknowledges 'no per-meter pricing' but gives no figures.
- ›Differentiation claims ('financial operating layer, not hardware'; 'autonomous action'; 'bridges operations + procurement') came from the /company/about page [step 11], which surfaced the company's own positioning language but offered no comparative analysis.
- ›External sources (steps [8], [10] search results) initially misdirected the agent to a Texas electricity retail provider (Companion Energy, unrelated), then correctly identified the B2B SaaS vendor and supplied funding/customer context absent from the domain itself.
- ›The agent correctly identified what it couldn't find (pricing, competitors, case studies, modular adoption detail) and transparently reported these gaps rather than inventing details—demonstrating appropriate epistemic boundaries.
See every agent that visits companion.energy
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 →