Quick QA review
Before a launch or important change
- 1 critical journey
- Desktop and mobile
- 30-minute results review
You receive
Issues, evidence and repair priorities
Estimated 1–2 business days
Request a quote View scope and detailsServices / digital product testing
Review a critical journey, audit your product or add ongoing QA support. Choose a scope and get issues with evidence and repair priorities.
We reply within 24 hours on business days. Scope and cost are agreed before work starts.
Four ways to work together
You do not need a test plan. Choose the situation closest to your product.
Before a launch or important change
Issues, evidence and repair priorities
Estimated 1–2 business days
Request a quote View scope and detailsBefore a release or product handover
Issue impact and a clear repair order
Estimated 3–5 business days
Request a quote View scope and detailsWhen you need to address access barriers
Barriers report and recommended fixes
Estimated 4–6 business days
Request a quote View scope and detailsWhen your product has regular releases
Test results and release risks
20 / 40 / 80 hours per month or more
Request a quote View scope and detailsDurations are estimates for delivery after scope and access are agreed. Dates are confirmed individually.
Scope and working principles
Choose a service. See what we test, what you receive and what we agree before starting.
Check one journey that your product depends on.

1–2 business days
Start, finish and scenarios agreed before starting.
The selected journey on desktop and mobile.
Reproduction steps, evidence and priorities.
A concise report: confirmed issues, evidence and repair priorities.
A focused review of one journey. Wider coverage and retesting are agreed separately.
The agreed scope includes a 30-minute results review.
Product goals and critical journeys.
Devices, browsers and required access.
Agreed scenarios and areas to check.
Start, finish and scenarios agreed before starting.
The selected journey on desktop and mobile.
Reproduction steps, evidence and priorities.
What was tested, what was not and which issues were found.
30 minutes for questions and repair priorities.
Wider scope and retesting are agreed separately.
Understand issues across critical journeys and prioritise repairs.

3–5 business days
An agreed list of journeys and forms.
Behaviour and usability obstacles, including on mobile.
Reproduction steps, evidence and priorities.
A report with reproduction steps, issue impact and recommended repair order.
Journeys, devices and browsers are confirmed before work starts. Process or automation reviews are scoped separately.
Product goals and critical journeys.
Devices, browsers and required access.
Agreed scenarios and areas to check.
An agreed list of journeys and forms.
Behaviour and usability obstacles, including on mobile.
Reproduction steps, evidence and priorities.
What was tested, what was not and which issues were found.
Key fixes within the agreed scope.
Issue impact and recommended priorities.
Find what prevents users from completing important journeys.

4–6 business days
Using selected views without a mouse.
Forms, messages and information for users.
Contrast and assessment against WCAG 2.2 within the tested scope.
A barriers report with evidence, user impact and recommended fixes.
The report covers the tested scope. It is not a whole-product accessibility certificate.



Product goals and critical journeys.
Devices, browsers and required access.
Agreed scenarios and areas to check.
Using selected views without a mouse.
Forms, messages and information for users.
Contrast and assessment against WCAG 2.2 within the tested scope.
What was tested, what was not and which issues were found.
Evidence, user impact and recommended fixes.
Retesting and results review by agreement.
Make testing part of your team’s work and verify fixes across releases.

20 / 40 / 80 hours per month or more
Functionality and error handling.
Checking selected existing journeys.
Reproduction steps, evidence and priorities.
Communication, blockers and tracking fixes within the agreed scope.
Actionable issues, test results and a risk summary for upcoming releases.
We tailor the level of support to your team’s needs. We agree priorities and allocate hours to onboarding, meetings, testing, reporting and retesting.
Product goals and critical journeys.
Devices, browsers and required access.
Agreed scenarios and areas to check.
Hour allocation and communication arrangements.
Functionality and error handling.
Checking selected existing journeys.
Reproduction steps, evidence and priorities.
Communication, blockers and tracking fixes within the agreed scope.
Verifying fixes within the agreed scope.
What was tested, what was not and which issues were found.
Testing limitations and open issues.
Consultations and priorities for further testing.
| Compare by | Quick QA review | QA audit | Accessibility audit | Ongoing QA support |
|---|---|---|---|---|
| Scope | 1 journey | Agreed journeys | Agreed views and journeys | 20 / 40 / 80 h per month or more |
| Testing | Functionality and UX | Functionality, UX, mobile | Accessibility: WCAG 2.2 | Changes and regression |
| Environments | Desktop and mobile | Agreed browsers and devices | Keyboard and screen reader | Based on team priorities |
| Deliverable | Concise prioritised report | Report with business impact | Barriers and recommendations | Issues and recurring reports |
| Retesting | By agreement | Key fixes | By agreement | Within the hourly package |
| Results review | 30 minutes | Optional | By agreement | Within the hourly package |
| Estimated duration | 1–2 business days | 3–5 business days | 4–6 business days | 20 / 40 / 80 hours per month or more |
See the deliverable
A description, reproduction steps, evidence and priority. The sample report shows how we communicate findings to development and release decision makers.

From enquiry to quote
Share a URL or short description, the journey to check and your deadline. Include a budget if you have one.
We clarify journeys, environments, access and the expected deliverable. We reply within 24 hours on business days.
Before work starts, we confirm the deliverable, dates, retest scope and billing model.
Team and approach
Explore our experience, capabilities and the QA Lead’s role. See how we agree risks, report issues and hand over findings.
Test automation
We can assess which recurring scenarios are worth automating. Start with a selected journey and agree implementation and maintenance scope separately.
Explore test automation ↗FAQ
Describe your product, the most important journey and your deadline. You do not need a test plan. We will suggest a scope based on what you need to check.
After scope is agreed and the required access is provided. Durations are estimates; start and delivery dates are confirmed in the proposal.
Yes. A quick review covers one critical journey. The findings help you decide whether to commission a wider audit or ongoing support.
The number and complexity of journeys, platforms, devices, available environments, deadline and retest scope. Scope and cost are agreed before work starts.
Your next step
A short description, the most important journey and your deadline are enough to start. We will clarify the scope and prepare a quote.