treba.io
success
Claude Code
intent

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

5steps
45.4sduration
$0.0515cost
22,524tokens
6 steps1 reasoning step
home
docs
docs
/how-we-compare
/faq
80%
answer from your site
60%
answer efficiency
25%
followed site links
answer sources
  • from this site80%
  • from agent knowledge20%
url discovery
  • given in the task20%
  • followed a link20%
  • guessed the URL60%
insight

Agent satisfied the task by assembling a comprehensive overview of Treba's business model, pricing, target market, and differentiation from fetched pages (homepage, pricing, about). The site was navigable but incomplete: pricing lacked concrete numbers, competitor comparison page returned 404, and key operational details (onboarding, FX protection specifics, proof of concept) were absent or unclear from available content.

  • ›Site exposed core value proposition on homepage (step [0]): EOR model, 60–80% cost savings, 4 service domains, 50+ role types, 7-day hiring, 30-day guarantee. This was content-bearing and formed the backbone of the answer.
  • ›Pricing page (step [1]) revealed the bundled fee model and three engagement tiers but deliberately withheld actual per-seat prices, requiring manual disclosure during scoping calls—the agent correctly flagged this as a friction point for someone evaluating the service.
  • ›About page (step [2]) provided explicit target customer profiles, use case examples, and three core differentiators (EOR vs. freelancers, timezone overlap, 98% rejection vetting). This was the richest content-bearing step for positioning.
  • ›Agent attempted direct navigation to /how-we-compare and /faq (steps [3–4], both 404) without discovering them from the site itself, indicating those comparative resources were either not published or not linked from main pages—a significant gap for someone doing competitive evaluation.
  • ›Agent's final response correctly attributed missing elements (published pricing, Managed Pod cost breakdowns, competitor comparisons, training/onboarding detail, FX protection edge cases, case studies) to site absence rather than retrieval failure, demonstrating accurate scoping of what the site actually exposes.

See every agent that visits treba.io

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 →