A public question.
An evidence-led answer.

Agree the public question first.

Send your business website and the question you want answered. We agree the public pages or other public evidence in scope. If the question needs private access instead, I say so before an analysis is commissioned.

I check public pages and navigation, publicly visible behaviour, public DNS records where relevant, and the evidence needed for the agreed question. Public page requests use GET or HEAD. I do not log in, submit forms, probe credentials or change your website.

Use a work address matching the business domain. Where that is not available, the existing authorisation route is a one-line meta tag on the site. No meeting is required for this public-source scope.

A report you can check.

You receive the findings, supporting sources or reproduction steps, and a clear account of what could not be established. Observed facts, reproduced behaviour and inferences are distinguished.

An absence of findings only describes the checks completed. It is not proof that the whole business, website or integration is healthy. You can use the report with your own team; implementation is not part of the purchase.

The existing price and guarantee.

£150 fixed. The report and invoice arrive together. If the analysis teaches you nothing new, the invoice is cancelled. You judge whether it was useful.

The analysis fee is credited against the existing reconciliation scope or a fixed build. Existing agreed credit terms are retained. This guarantee and credit belong to the analysis offer, not automatically to the separate £150 system check.

Only the next step that makes sense.

A public finding may suggest a direct build, a more focused internal investigation, work for your existing team, or no further work. None is compulsory. A known build does not have to start here.