The agent assembled a substantial profile of 26lights' business model, target customers, and competitive positioning through web search results and service pages, but could not determine pricing because the website does not publish pricing information in a machine-readable or even human-visible form — relying instead on custom quotes obtained via direct contact. The site's heavy JavaScript dependency and Elementor-based architecture made detailed content difficult to extract; the agent relied heavily on search snippets and prior knowledge to fill gaps.

• ›Steps [4], [12], [19], [25] were web searches that returned snippet summaries of services pages; these snippets contained the core narrative (growth architect, venture builder model, three pillars: tech/business/marketing) but the actual service pages ([7], [8], [9]) returned only HTML shells with embedded Elementor iframes, making them unreadable to the agent. The agent had to piece the story together from search result titles and metadata rather than from direct page content.
• ›Pricing information was completely absent from all fetches and searches. Step [15] (search for pricing/cost) and step [26] (search for fees/engagement) returned only navigation links and homepage URLs, not pricing data. This indicates 26lights deliberately withholds pricing from public view — a structural choice, not a site navigation failure.
• ›The agent discovered differentiators (venture builder vs. consultant, 360° expertise, My26 platform, senior talent, agile methodology) through search results ([12], [22], [25]) and inferred positioning from service page titles and blog snippets, not from a dedicated positioning statement on the site. The agent also noted ambiguity in self-description (consulting firm vs. venture builder) that the site does not resolve.
• ›Standard navigation paths (steps [1]–[3]: /pricing, /features, /about) all returned 404s, forcing the agent to rely on web search to discover the actual URL structure (/business, /marketing, /tech). The sitemap ([6]) and WordPress REST API ([13]–[14]) were discovered but did not yield readable content.
• ›The agent explicitly noted it could not access customer stories ([17]: /resources returned 404; step [24] found a link to /customer-stories/ but did not fetch it, suggesting either a dead reference or additional JS-blocking). This represents a gap in the agent's ability to validate claims with concrete examples.