vlan.asia
success
Claude Code
intent

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

18steps
85.2sduration
$1.1311cost
254,907tokens
28 steps10 reasoning steps8 searches
home
docs
docs
/services
search
/zendesk
search
/about-us
search
search
/marketplace/solutions…
search
/microsoft-365
search
search
search
/website-package
/remote-service-support
40%
on-site discovery
70%
reliability
30%
link following
path origin
  • previous resource30%
  • web search60%
  • prior knowledge10%
insight

The agent assembled a reasonably complete understanding of VLAN Asia by combining the homepage fetch with targeted web searches and follow-up fetches of their service pages. The site itself is fragmented and navigation-poor—no traditional /about, /pricing, or /services routes work—forcing the agent to rely on 60% web search discovery plus educated URL guessing. The agent successfully answered what VLAN Asia does (regional cloud solutions reseller, implementation partner), who it's for (SMBs in Southeast Asia), and how it differs (regional focus, multi-platform certifications, 20+ year track record), but could not fully satisfy the pricing question due to the site's lack of transparent pricing pages.

  • ›The homepage [0] only established baseline positioning ('Cloud CX - Zendesk Microsoft Hubspot Netsuite') but did not contain detailed service descriptions, pricing, or competitive positioning. The agent had to guess or search for everything else.
  • ›Standard navigation routes (/about, /pricing, /services) all returned 404s [2, 3, 4], indicating a site architecture that either uses JavaScript routing or HubSpot CMS patterns that don't expose clean URL structures. The agent worked around this by using web search to discover valid endpoint URLs.
  • ›Content-bearing pages ([8] Zendesk, [9] Remote Service Support, [12] About Us, [20] Microsoft 365, [26] Website Package) existed but were discoverable only through web search or URL guessing, not through site navigation. This forced 60% of information sourcing to web search rather than direct site traversal.
  • ›Pricing was the largest gap: [9] mentioned 'RM800/month' for remote IT support but no other service pricing was visible on the fetched pages. The agent correctly identified this as a confusing absence and noted that most pricing appears to be quote-based, working from implicit patterns rather than explicit site disclosure.
  • ›The agent cited the About Us page [12], Zendesk partner profile (external, [15] search result), and HubSpot marketplace profile [17] as key sources for understanding the company. None of this was clearly linked or cross-referenced on the main site.
  • ›Website pages showed truncation artifacts ('4400 more chars') indicating either heavy JavaScript rendering or incomplete HTML responses—the site may not be fully agent-readable even when pages load, reducing the amount of extractable text per fetch.

Help the next agent finish on vlan.asia

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 →