fusefleet.com.au
success
Claude Code
intent

What does fusefleet.com.au do and who is it for? Explain it back to me.

23steps
93.2sduration
$1.1426cost
375,534tokens
36 steps13 reasoning steps6 searches
home
docs
docs
/features
sitemap
/page-sitemap.xml
/onboarding
search
/fleet-insurance
/wp-json/wp/v2/pages/5…
/motor-fleet-insurance
/wp-json/wp/v2/pages/5…
/services
/wp-json/wp/v2/pages/3…
search
/faqs
/wp-json/wp/v2/pages/4…
search
search
/who-we-are
/wp-json/wp/v2/pages/4…
search
search
71%
on-site discovery
82%
reliability
65%
link following
path origin
  • previous resource65%
  • web search29%
  • prior knowledge6%
insight

The agent successfully assembled a comprehensive overview of Fuse Fleet's business model, target market, and competitive positioning by combining site content (fetched pages and their JSON API equivalents), web search snippets that cited the site, and prior knowledge about fleet insurance. However, the site itself is poorly structured for answering the core task — critical information like pricing, fleet size minimums, and telematics implementation details are either buried, fragmented across pages, or not published at all, forcing the agent to rely on inference and external context to fill gaps.

  • ›Content-bearing steps returned only raw HTML/JSON with marketing copy and conceptual descriptions of services (AI scoring, ESG reporting, telematics integration) but no concrete operational details (pricing models, fleet minimums, coverage specifics, device requirements). The agent had to extract meaning from fragmented, design-heavy WordPress markup rather than structured data.
  • ›The site lacks a dedicated pricing page (404 on /pricing), about page (404 on /about), and features page (404 on /features) — standard discovery pages for a SaaS/insurance product. The agent bypassed this by using the sitemap and search engine results as navigation aids, then reconstructing positioning from services, motor-fleet-insurance, and who-we-are pages.
  • ›Critical information gaps (minimum fleet size: 15 vehicles, partnership with Greater Than for AI scoring, Recoversure for claims, DKG Group parent company) came primarily from web search snippets and prior knowledge, not from the site's own navigation or content hierarchy. The site mentions these partnerships and minimums in scattered places but does not front them clearly.
  • ›The JSON API endpoints (steps 18, 19, 20, 26, 34) returned the same rendered HTML content as their HTML counterparts, still embedded in shortcode markup and not machine-readable — the site is not structured for semantic extraction or bot consumption.
  • ›No public pricing examples, no comparison tools, no downloadable product sheets, and no FAQ that transparently answers 'how much does it cost' or 'what's the minimum fleet size' — these are advertised as contact-only, which is defensible for B2B but makes the site opaque to evaluation.
  • ›The agent cited seven Fuse Fleet URLs and three external sources (LinkedIn, press release) in its final answer. Only the Fuse Fleet pages actually contained the information it used; external sources filled critical gaps (ESG reporting and Greater Than partnership details).

See every agent that visits fusefleet.com.au

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 →