Frequently Asked Questions


These pages describe the systems supporting discovery, campaigns and service. Advertising and content production need an explicitly agreed scope.

Yes. Referral, partner, dealer and other relationship models can be designed where a standard contact-and-deal structure is insufficient.

No. Predictable steps often work best with rules. AI is useful when interpreting variable language or documents adds value.

Pages should reflect real differences in services, teams, access and local information. Shared templates can maintain consistency.

No. Evaluation, source controls, refusals and escalation remain necessary.

Changes are reviewed for their effect on scope, cost and timing before approval. Post-launch support, response expectations and continuing improvement are agreed as part of the engagement.

Select a useful set of questions and approved sources for a bounded pilot, then evaluate answer quality with real users.

We define necessary data, authorised access and source-system boundaries before implementation. Your organisation approves privacy and retention requirements.

Relevant measures include location discovery, valid enquiries, response time and routing errors. We agree which signals are available before work begins.

The programme controls URL mapping, redirects, canonicals, internal links, metadata, staging access, launch validation and post-release monitoring. No migration is risk-free, so evidence and rollback decisions remain visible.