Every bug comes with a recording.
No "cannot reproduce" arguments. Each finding in the report links to a session recording of the moment it happened: the clicks, the input, the broken result. Your client sees the evidence, not a claim.
For agencies and dev shops
White-label QA for the apps you ship.
Before you hand a project over, we put it through a structured human test pass and send back a findings report with a screen recording of every bug: what broke, where, and exactly how it happened. White-label, so the report goes straight to your client as your own QA deliverable.
First project €249 flat · Report within 72 hours · No subscription required
Why agencies plug us in before handover
Independent QA your client can watch.
White-label by default.
The report carries your logo if you want it to. Forward it to your client as your own independent QA step, or bill it through as a line item. We stay invisible; you look thorough.
Fixed price, fast turnaround.
€249 flat for a first project, findings back within 72 hours. No scoping meetings and no calls: send a URL and test credentials, get a report. Everything runs async over email.
From recent test passes
The bugs that reach clients are the quiet ones.
We recently tested ten freshly built apps and found shippable bugs in every single one. Two patterns, anonymized, from those sessions:
Silent data loss
The contact form that lost every message.
A quote-request form showed its success state on submit, but the data never arrived anywhere. Every lead sent through it simply vanished. The team had no idea, because nothing looked broken. This is the worst class of bug precisely because it is invisible without a real test pass.
Trust killer
The error message that would not leave.
Valid input was accepted and processed correctly, but the validation error stayed on screen anyway. Users assumed the app was broken and retried, or gave up. The feature worked; the experience said otherwise.
More patterns like these in our write-up: the five bugs we find in almost every AI-built app.
The proof format
Every finding links to a recording like this.
This is a demo session from our own recorder. Reports on your projects reference recordings in exactly this format, so your client can watch any finding happen instead of taking it on faith.
0:00 / 0:00
This replay has no events to show.
The replay player couldn't load. An ad or privacy blocker is the most common cause here.
Disable it for this site, or try a different browser, and it'll play. Your testers' own recordings
work the same way: an occasional blocker gets in the way, which is why we ask testers to
whitelist the recording origin before they start.
If you can't see it play: this is a recording of a tester clicking, scrolling and typing through a staged demo app, with their written findings alongside it. It's the same replay and report you get from every TestTorch session once the recorder snippet is installed.
How a pilot works
Three emails, no meetings.
-
1
Send us a project.
Email a URL (staging or production), test credentials, and anything you specifically want covered. We confirm scope and start date by reply, with a VAT invoice for the €249 pilot.
-
2
We run the test pass.
A structured walkthrough of the real app: core flows, forms, payments, edge cases, the places polite users break things. The whole session is recorded end to end.
-
3
You get the report within 72 hours.
Findings ranked by severity, each linked to its recording, delivered white-label. Forward it to your client, or keep it internal and fix before handover. Afterwards, if you want us on tap: €499 per month covers up to two test packs, cancel monthly.
Ship your next handover with proof it works.
One email starts it: a URL and test credentials. Report back within 72 hours, €249 flat, white-label. We reply within one business day.
info@testtorch.com · TTB Software Development B.V., Netherlands