pillar.it
success
Claude Code
intent

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

15steps
68.9sduration
$1.0533cost
169,411tokens
24 steps9 reasoning steps7 searches
home
/prezzi
/features
/en-gb
search
/p/266593/pillar
/2026/05/12/pillar-sec…
search
/en/pillar-the-start-u…
search
search
search
search
search
/chi-siamo
62%
on-site discovery
50%
reliability
38%
link following
path origin
  • previous resource38%
  • web search38%
  • prior knowledge25%
insight

The agent partially satisfied the task by assembling a coherent explanation of Pillar's positioning, target market, and differentiation from competitors. However, critical information gaps remained: the site itself did not expose pricing, detailed feature lists, customer names, or implementation details. The agent relied heavily on external news articles and prior knowledge to construct the answer, rather than pulling this information directly from pillar.it. The site's marketing-heavy, JavaScript-rendered homepage and missing translation/navigation to key pages (Italian-language subpages returned 404s) made it difficult to extract specifics from the primary source.

  • ›The two content-bearing fetches ([13] and [16]) were both external news/startup coverage articles (Tech.eu and StartupBusiness.it), not pillar.it itself. These provided founding timeline, funding amounts (€12M, €3.2M), and high-level product positioning.
  • ›Pillar.it's own website returned only JavaScript-heavy homepage renders with no readable content extracted. Attempts to navigate to Italian subpages (/prezzi, /features, /chi-siamo) returned 404 errors, and the English translation (step [7]) also rendered heavily script-dependent markup without accessible content.
  • ›Pricing information was explicitly unavailable: the agent correctly identified that Pillar uses a custom quote-on-demo model, but this was inferred from startup coverage and common SaaS patterns, not from the company's own pricing page (which either doesn't exist or wasn't navigable).
  • ›The agent had to execute 5 web searches to find external coverage because the site itself lacked SEO-friendly, machine-readable product details. This indicates poor agent-readiness: no structured data (schema.org), no public pricing, no feature matrix, no customer testimonials visible in the fetched HTML.
  • ›The final answer correctly flags the limitations: 'no public pricing information,' 'limited feature details on their actual website,' 'who exactly are their current customers unclear.' These gaps were not overcome by the site itself.

Help the next agent finish on pillar.it

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 →