PACKAGES
Fixed price. Written scope. Re-test included.
We don’t bill by the hour. Take a ready-made package or tick your own criteria and build the scope yourself; the price appears as you select in the panel.
| Package | ScoutTeams who want one product or one new feature checked quickly before it ships.€680single test, fromChoose this package | Most chosenReleaseTeams auditing the whole product ahead of a major release or launch.€1,650per release, fromChoose this package | FleetProduct teams shipping often who want regression cover before every release.€1,300per month, 6-month termChoose this package | EnterpriseRegulated sectors, on-site requirements or specific compliance obligations.Let's talkscope-basedLet's talk |
|---|---|---|---|---|
| SCOPE | ||||
| Exploratory testing sessions | yes | yes | yes | yes |
| Scenario-based functional testing | yes | yes | yes | yes |
| Real device / browser matrix | 1 platform | 3 platforms | 3 platforms | full |
| Maintained regression suite | no | no | yes | yes |
| AUDITS | ||||
| Performance and load testing | no | yes | yes | yes |
| Security review (OWASP Top 10) | no | yes | yes | yes |
| API contract testing | no | yes | yes | yes |
| Accessibility audit (WCAG 2.2 AA) | no | optional | yes | yes |
| DELIVERY | ||||
| Video and console log per finding | yes | yes | yes | yes |
| Jira / Linear export | no | yes | yes | yes |
| Re-test round after fixes | 1 round | 2 rounds | unlimited | unlimited |
| Time to first report | 72 hours | 48 hours | 48 hours | 48 hours |
| ENGAGEMENT | ||||
| Dedicated test engineer | no | no | yes | yes |
| Response time | 2 business days | 1 business day | 4 hours | 4 hours |
Prices are starting figures and exclude VAT. The final amount appears in the panel once your services and device matrix are settled.
Frequently asked
Do we have to give you a test environment?
No, but we strongly recommend it. If we have to test in production we exclude every scenario that writes data and work only with read-only checks — which narrows the scope considerably.
Do you fix the bugs you find?
No. We don't ship fixes, because that's what keeps us independent. We give you the finding, the cause and the reproduction steps; your team fixes it and we verify it in the re-test round.
Can you tell us how many bugs you'll find?
We can’t, and you shouldn’t believe anyone who does. What we do give you up front, in writing, is how many cases we’ll test, which devices we’ll use and which services are in scope.
Will there be a surprise invoice?
No. The price is fixed together with the scope. If something outside it comes up, we ask you first and don't continue without approval.
Do you need to see our source code?
Not for functional, compatibility or usability testing — we work black box. For performance bottleneck analysis and the security review, code access makes the results noticeably better, but it isn't required.
Do you sign an NDA?
Yes, as standard. We can send ours or sign yours. All test data is deleted 90 days after the run ends.
Do you write automated tests too?
On the Fleet package we automate the critical flows of the regression suite with Playwright. You own the tests; when the contract ends they stay in your repository.
How soon can you start?
You join the queue the moment you sign up, pick your criteria and pay. Thanks to the network, testing usually starts within 2 business days; for urgent launches we sometimes start the same day.
Don't test the next release alongside your users.
Sign up in the panel, pick what you want tested, pay. The first findings start landing in the same panel within hours.