Focused exploratory testing
Exploratory bug hunting before your users find the problems
Our QA team goes through your web app the way a real user would and finds what scripted tests miss: broken states, dead ends, confusing steps, and things that only fail on one browser or device. Start with one focused session.
EUR 299one 6-hour session · testing and documenting findings
Need recurring hunts, or more browsers and devices? We scope and price that with you.
One bug, on its way out. Watch the page.
Fresh eyes
Does your product make sense to someone who sees it for the first time?
You use your software every day, so nothing in it feels confusing to you. A new user has none of that context. During a bug hunt we go through your product like a first-time user and tell you where it breaks, where it confuses, and what we would improve first.
What you hear back
- What is broken, with steps to reproduce
- What is confusing or easy to get wrong
- What we would change first, and why
How we work
From the first call to a clear result.
- 01
Agree the scope
Before the session we agree which part of the product to test, on which browsers and devices, and what access we need.
- 02
Hunt like a first-time user
Our QA team works through the product the way a new user would: changes data and order, interrupts flows, switches devices, and follows anything that looks off.
- 03
Report what we found
Findings land in your dashboard, most important first, with steps to reproduce and screenshots. Send them to Jira, Linear, or any tracker, and get a Slack, Teams, or email message when the hunt is done.
Results, evidence, and QA requests live in your Release Shield dashboard. Bugs go to Jira or Linear, updates to Slack, Teams, or email. See the dashboard
Example exploratory route
Hunting around subscription changes
The session might move beyond the happy path to explore state and timing combinations.
- Change plan in two open tabs
- Return after an interrupted payment
- Compare account, invoice, and confirmation states
What you receive
- Exploratory testing of the agreed scope
- Every finding in your dashboard with steps and screenshots, one click from a Jira or Linear ticket
- Notes on what confused us and what we would improve first
What we need to start
- The product area or journey to explore
- Working access, accounts, and test data
- Agreed browsers, devices, and known concerns
Common questions
What does EUR 299 include?
One session of 6 hours of senior QA time, including testing and documenting findings. We agree scope, browsers, and devices before the session.
Can you test more browsers and devices, or run bug hunts regularly?
Yes. We can cover more phone, tablet, and desktop combinations, or schedule recurring hunts before each release. We quote these separately based on scope, devices, and frequency.
Is this the same as bug bounty hunting?
No. A bug bounty pays outside security researchers for vulnerabilities. Our bug hunt is an exploratory QA testing session on your own web app, booked by you, at a fixed price, with a written report of functional and usability bugs. It is not a penetration test.
Book a demo. After setup, you request hunts straight from your dashboard.
30 minutes on Google Meet. Pick a time directly in our calendar.