The agent successfully assembled a comprehensive explanation of Lillio's business, target audience, positioning, and competitive differences, but had to work around a critically opaque pricing model and rely heavily on external comparison articles rather than Lillio's own website. The site itself publishes only high-level product value and requires sales contact for pricing; the agent filled gaps using third-party review sites, competitor comparison blogs, and user reviews, which were more informative than Lillio's own pages.

• ›Step [1] (homepage) and step [8] (about page) provided only marketing-level descriptions of features (parent messaging, daily reports, check-in, assessments, curriculum) and positioning ('all-in-one' for daycare centers); they explicitly stated what Lillio does but did not explain who it targets, how it's priced, or how it differs from alternatives.
• ›Step [17] (illumine.app comparison article) was the richest content-bearing source, providing detailed feature-by-feature comparisons with Brightwheel and Procare, user experience differences, pricing model context (per-child vs. flat-rate), and specific weaknesses (photo/video issues, mobile UI, reporting limitations). This external article contained more actionable positioning than any Lillio-owned page.
• ›The pricing page (step [4]) redirect loop and 404 on /pricing (step [2]) forced the agent to rely on web search results and third-party pricing aggregators. Lillio does not publish transparent, machine-readable pricing on its own domain—the canonical source (lillio.com/features/pricing) exists but was not directly fetched due to truncation, and search evidence suggests it requires a sales contact form rather than displaying rates.
• ›The agent had to conduct 7 separate web searches (steps [6], [7], [10], [11], [14], [15], [16], [18], [19], [20], [21], [22]) to answer questions the site itself should have addressed: pricing tiers, feature breakdowns, competitive differentiation, and known user complaints. This indicates poor information architecture on Lillio's core evaluation pages.
• ›Steps [12] and [13] hit Cloudflare/bot-detection walls on G2 and Capterra, forcing reliance on cached search results rather than primary review data. The agent worked around this by iterating search queries.
• ›The site is poorly navigable for agent evaluation: no public pricing, no feature-tier comparison table, no explicit positioning against competitors, and customer pain points (app performance, photo upload issues, dated mobile UI) are absent from Lillio's marketing—visible only in external reviews the agent had to search for.