The usual question
Asked every sixty seconds, by almost everyone.
"Is the server online?"
Yes.
Cheap to answer, easy to automate, and satisfied by a website nobody can buy from.
Most monitoring asks "is the server up?" We ask a harder question.
Can the customer actually do what they came here to do? That single change of question is the entire reason FaultFound exists — and it turns out to be a much more difficult thing to answer honestly.
Our question
Asked by walking the journey, then checking twice.
"Can a customer still buy,
book, or get in touch?"
Not at the delivery step.
Expensive to answer properly, which is exactly why so few people do.
Why FaultFound exists
Because the usual order of business is backwards.
The normal way to sell website work is to send a pitch to a thousand businesses and hope. It begins with a claim, and the business is asked to take it on faith.
FaultFound reverses that. We find a real, reproducible fault first. We record what we saw and when. Only then do we get in touch — and the first thing you get is the evidence, free, so you can check our work before deciding whether we are worth paying.
It is a slower way to build a business. It is also the only version of this business we would want to run, because it means we are never asking anyone to believe us about anything.
1. Find something real
Not a score, not an opinion — a specific page that fails.
2. Prove it isn't a fluke
Check again later. Confirm in a browser. Discard anything that clears.
3. Show the business, free
The full evidence, before any money is discussed.
4. Let them decide
Buy the repair pack, hand it to your own developer, or ignore us entirely.
The evidence-first principle
If we can't show you, we don't say it.
This applies to our reports and to this website. Everything below is a rule we have chosen to work under, and you are entitled to hold us to all of it.
Observation and inference are labelled
What we saw is stated as fact. What we think caused it is stated as an inference.
Uncertainty is a number, not a hedge
Confidence appears on the report. When it's low, that is visible rather than buried.
No invented figures
We will not put a pound value on lost sales we did not observe. Nobody can, honestly.
No borrowed credibility
No logos we don't have permission for, no certifications we don't hold, no awards we haven't won.
Wrong findings get withdrawn
If we got it wrong we say so, explain what the system misread, and don't raise it again.
You can always check our work
Every finding names a URL you can open yourself. That is deliberate.
How FaultFound is built
Automation for scale. Human rules for judgement.
Checking public customer journeys across the UK is only possible with automation. Deciding what is worth a business's attention is not something we were willing to leave to a machine.
Automated discovery
Maintains the queue of publicly listed UK business websites to check.
- Public listings only
- Rate-limited and polite
- Suppression list respected
Browser-based checking
Walks public commercial routes in a real browser and records what happens.
- Renders JavaScript journeys
- Read-only, never submits
- Captures responses and timings
Verification rules
Human-designed logic deciding what is a fault, what is noise, and what needs re-checking.
- Delayed re-checks
- Bot-block detection
- Commercial weighting
Evidence store
Keeps URLs, responses and timestamps attached to each finding so it stays checkable.
- Immutable observation log
- No customer data stored
- Retained with the report
Reporting
Turns a verified finding into a private page a non-technical owner can act on.
- Plain English first
- Technical detail on demand
- Unlisted and not indexed
UK focus
Built around UK businesses, platforms, payment methods and buying habits.
- UK towns and cities
- Sterling pricing
- UK support hours
On the size of the team: FaultFound is a small operation, and we are not going
to invent a floor of consultants to look bigger. What matters to you is whether the
finding is real and whether someone answers when you reply. Both of those we can
stand behind.
Who is behind FaultFound
The functions, honestly described.
Rather than publish invented staff profiles, here are the roles that actually exist and what each is responsible for. Named details will be added here once they are confirmed for publication.
Founder
Responsible for what FaultFound will and will not do — the scope, the boundaries and the decision to show evidence before asking for money.
Name and background to be published here before launch
Technical systems
Builds and maintains discovery, browser-based checking, the verification rules and the evidence store. Owns the false-positive rate.
Awaiting confirmed detail
Customer support
Answers questions about a report, disputes about a finding, and opt-out requests. Replies come from a person, not an autoresponder.
Reachable at support@faultfound.co.ukPlaceholder content. These are role descriptions, not profiles of invented people. No photographs, names or biographies appear here because we will not present anyone as a member of staff who is not one.
Company details
FaultFound is a UK-focused business serving UK companies, with pricing in pounds sterling and support during UK working hours.
Awaiting publication. The registered company name, company number and
registered address will be published here and in the footer once the legal entity
is finalised. Until they are confirmed, this website does not display them —
because publishing a registration number we cannot evidence would undermine the
one thing this company is built on.
For anything at all — a question about a report, a dispute about a finding, a privacy request or an opt-out — contact us or email support@faultfound.co.uk.
The best way to judge us is to read one.
Open the sample report and decide for yourself whether it looks like the work of a company that checked properly.