directivesystems.com.au
success
Claude Code
intent

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

17steps
78.6sduration
$0.8384cost
210,716tokens
25 steps8 reasoning steps5 searches
home
docs
docs
search
sitemap
sitemap
/case-study
/systems
/composer
/faq
/memory
/contact
search
search
search
search
/in/mashjprime
92%
on-site discovery
83%
reliability
83%
link following
path origin
  • previous resource83%
  • web search8%
  • prior knowledge8%
insight

The agent successfully gathered a comprehensive understanding of Directive's business by fetching the homepage, about page, case study, systems page, and product pages (Composer, Memory), along with FAQ and contact pages. The site proved highly navigable via its sitemap; however, pricing information was deliberately absent, forcing the agent to acknowledge this gap and flag it as a significant limitation in the final answer.

  • ›Steps [1], [3], [10], [11], [14] directly returned business-model and positioning content: the homepage established 'AI systems, automation and products' philosophy, the about page confirmed founder-led structure, the systems page explained custom-build approach, Composer/Memory pages described two packaged products, and the case study provided concrete proof of impact (40 hrs/week recovery, 99.7% reliability).
  • ›The site surface the core narrative through its IA (homepage → about, systems, products, case study, FAQ, contact) which the agent discovered via sitemap [8] rather than organic link-following, indicating the site publishes its structure clearly but relies on navigation discipline rather than inline cross-linking.
  • ›Pricing was conspicuously absent: step [2] returned a 404 for /pricing, and neither the FAQ [12] nor contact [15] pages exposed actual price figures — only statements like 'addresses cost' and 'email for details.' This forced the agent to classify the business model as custom/bespoke by inference and note the friction explicitly.
  • ›Competitor differentiation and 'dry run' mechanics were inferred from messaging (steps [1], [10], [11]) rather than explained in detail, leaving the agent to flag ambiguities (what 'dry run' costs, exact deliverables, when to use custom vs. packaged products).
  • ›The site's clarity on *what* Directive does (products, philosophy, use cases) was high; clarity on *how much* and *exactly how* was deliberately low, suggesting a consultancy-sales model that requires human contact.

Help the next agent finish on directivesystems.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 →