ora
nuloft.co.uk
success
Claude Code · Haiku 4.51:53
intent

What does nuloft.co.uk do and who is it for? Explain it back to me.

22steps
113.1sduration
$0.7890cost
320,528tokens
29 steps7 reasoning steps3 searches
home
docs
/wp-json/wp/v2/pages/283
docs
/services
home
/wp-json/wp/v2/pages
/wp-json/wp/v2/pages
/get-a-quote
search
/how-much-does-a-loft-…
/wp-json/wp/v2/posts/560
search
/loft-conversion-types
search
/wp-json/wp/v2/posts/1…
/contact
docs
/case-studies
/why-nuloft
/process
/wp-json/wp/v2/pages/348
89%
on-site discovery
68%
reliability
58%
link following
path origin
  • previous resource58%
  • web search11%
  • prior knowledge32%
insight

The agent successfully assembled a comprehensive explanation of Nuloft's business model, target audience, and positioning by combining explicit web content (pricing guides, process pages, about section) with prior knowledge and web search. The site was reasonably navigable for discovery, with clear loft-type and pricing pages accessible through search, but pricing transparency and competitive differentiation information were scattered across multiple pages rather than centralized, requiring the agent to synthesize fragments.

  • Steps [19] and [26] returned the most concrete pricing data (£30k–£120k ranges by loft type), but this was buried in blog-style articles rather than published in a dedicated pricing table or API endpoint. The agent had to extract ranges from narrative content.
  • Step [24] (About page via REST API) and [25] (Process page) provided the 'chartered specialist' positioning and 6-step process claims, but neither explicitly articulated why this matters vs. competitors. The agent noted this gap and filled it by synthesizing the framing across pages.
  • The site was discoverable through web search (step [18], [22], [27] searches surfaced URLs) but not self-documenting—no /pricing, /pricing-comparison, or /why-us page existed (steps [3], [4], [14] returned 404s). The agent had to guess common URL patterns, then fall back to REST API enumeration and search.
  • Step [23] (Loft Conversion Types post via REST API) provided architectural context (Velux, Dormer, Mansard etc.) but not differentiation vs. competitors. The agent had to note this explicitly as a limitation.
  • The site lacks a machine-readable pricing or service schema. Pricing is narrative (blog posts) and custom-quote-driven, making it hard to extract structured data. Lead times, quote turnaround, and warranty details were mentioned but not centralized.
  • The agent discovered the 'Chartered Construction Manager' differentiator primarily from external PR (step [27] Manila Times mention), not from the site's own positioning pages, suggesting weak on-site communication of key differentiators.

Want to run your own?

Join the waitlist for early access to point your own agents at any domain, with the intents you choose.

or talk to us about agent readiness →