Services / digital product testing

What needs checking before your next release?

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

Choose where to start.

You do not need a test plan. Choose the situation closest to your product.

A good starting point

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 details

QA audit

Before a release or product handover

  • Agreed journeys
  • Functionality, UX and mobile
  • Retest of key fixes

You receive

Issue impact and a clear repair order

Estimated 3–5 business days

Request a quote View scope and details

Accessibility audit

When you need to address access barriers

  • Keyboard and screen reader
  • Forms and contrast
  • Assessment against WCAG 2.2

You receive

Barriers report and recommended fixes

Estimated 4–6 business days

Request a quote View scope and details

Ongoing QA support

When your product has regular releases

  • New features and regression
  • Retesting and issue reporting
  • Reporting and consultations

You receive

Test results and release risks

20 / 40 / 80 hours per month or more

Request a quote View scope and details

Durations are estimates for delivery after scope and access are agreed. Dates are confirmed individually.

Scope and working principles

What does each service cover?

Choose a service. See what we test, what you receive and what we agree before starting.

Quick QA review

Check one journey that your product depends on.

1–2 business days

What we test

  • One critical journey

    Start, finish and scenarios agreed before starting.

  • Functionality and error handling

    The selected journey on desktop and mobile.

  • Issue reporting

    Reproduction steps, evidence and priorities.

What you receive

A concise report: confirmed issues, evidence and repair priorities.

Scope and terms

A focused review of one journey. Wider coverage and retesting are agreed separately.

The agreed scope includes a 30-minute results review.

Planning, reporting and working process

Before testing

  • Understanding needs

    Product goals and critical journeys.

  • Scope and environments

    Devices, browsers and required access.

  • Testing priorities

    Agreed scenarios and areas to check.

During testing

  • One critical journey

    Start, finish and scenarios agreed before starting.

  • Functionality and error handling

    The selected journey on desktop and mobile.

  • Issue reporting

    Reproduction steps, evidence and priorities.

After testing

  • Results summary

    What was tested, what was not and which issues were found.

  • Results review

    30 minutes for questions and repair priorities.

  • Further testing

    Wider scope and retesting are agreed separately.

QA audit

Understand issues across critical journeys and prioritise repairs.

3–5 business days

What we test

  • Critical journeys

    An agreed list of journeys and forms.

  • Functionality and UX

    Behaviour and usability obstacles, including on mobile.

  • Issue reporting

    Reproduction steps, evidence and priorities.

What you receive

A report with reproduction steps, issue impact and recommended repair order.

Scope and terms

Journeys, devices and browsers are confirmed before work starts. Process or automation reviews are scoped separately.

Planning, reporting and working process

Before testing

  • Understanding needs

    Product goals and critical journeys.

  • Scope and environments

    Devices, browsers and required access.

  • Testing priorities

    Agreed scenarios and areas to check.

During testing

  • Critical journeys

    An agreed list of journeys and forms.

  • Functionality and UX

    Behaviour and usability obstacles, including on mobile.

  • Issue reporting

    Reproduction steps, evidence and priorities.

After testing

  • Results summary

    What was tested, what was not and which issues were found.

  • Retesting fixes

    Key fixes within the agreed scope.

  • Repair order

    Issue impact and recommended priorities.

Accessibility audit

Find what prevents users from completing important journeys.

4–6 business days

What we test

  • Keyboard and focus

    Using selected views without a mouse.

  • Screen reader

    Forms, messages and information for users.

  • Accessibility assessment

    Contrast and assessment against WCAG 2.2 within the tested scope.

What you receive

A barriers report with evidence, user impact and recommended fixes.

Scope and terms

The report covers the tested scope. It is not a whole-product accessibility certificate.

Planning, reporting and working process
Keyboard and focus
Screen reader
Contrast

Before testing

  • Understanding needs

    Product goals and critical journeys.

  • Scope and environments

    Devices, browsers and required access.

  • Testing priorities

    Agreed scenarios and areas to check.

During testing

  • Keyboard and focus

    Using selected views without a mouse.

  • Screen reader

    Forms, messages and information for users.

  • Accessibility assessment

    Contrast and assessment against WCAG 2.2 within the tested scope.

After testing

  • Results summary

    What was tested, what was not and which issues were found.

  • Barriers report

    Evidence, user impact and recommended fixes.

  • Further verification

    Retesting and results review by agreement.

Ongoing QA support

Make testing part of your team’s work and verify fixes across releases.

20 / 40 / 80 hours per month or more

What we test

  • Testing new features

    Functionality and error handling.

  • Regression

    Checking selected existing journeys.

  • Issue reporting

    Reproduction steps, evidence and priorities.

  • QA coordination

    Communication, blockers and tracking fixes within the agreed scope.

What you receive

Actionable issues, test results and a risk summary for upcoming releases.

Scope and terms

We tailor the level of support to your team’s needs. We agree priorities and allocate hours to onboarding, meetings, testing, reporting and retesting.

Planning, reporting and working process

Agree priorities

  • Understanding needs

    Product goals and critical journeys.

  • Scope and environments

    Devices, browsers and required access.

  • Testing priorities

    Agreed scenarios and areas to check.

  • Working plan

    Hour allocation and communication arrangements.

Test

  • Testing new features

    Functionality and error handling.

  • Regression

    Checking selected existing journeys.

  • Issue reporting

    Reproduction steps, evidence and priorities.

  • QA coordination

    Communication, blockers and tracking fixes within the agreed scope.

Verify and report

  • Retesting fixes

    Verifying fixes within the agreed scope.

  • Results summary

    What was tested, what was not and which issues were found.

  • Release risks

    Testing limitations and open issues.

  • Next steps

    Consultations and priorities for further testing.

Compare all service scopesSee the differences between services
Compare scope and deliverables
Compare byQuick QA reviewQA auditAccessibility auditOngoing QA support
Scope1 journeyAgreed journeysAgreed views and journeys20 / 40 / 80 h per month or more
TestingFunctionality and UXFunctionality, UX, mobileAccessibility: WCAG 2.2Changes and regression
EnvironmentsDesktop and mobileAgreed browsers and devicesKeyboard and screen readerBased on team priorities
DeliverableConcise prioritised reportReport with business impactBarriers and recommendationsIssues and recurring reports
RetestingBy agreementKey fixesBy agreementWithin the hourly package
Results review30 minutesOptionalBy agreementWithin the hourly package
Estimated duration1–2 business days3–5 business days4–6 business days20 / 40 / 80 hours per month or more
Need functionality and accessibility together?

See the deliverable

An issue your team can act on.

A description, reproduction steps, evidence and priority. The sample report shows how we communicate findings to development and release decision makers.

  • Reproduce the issue from the steps.
  • Assess the impact and prioritise fixes.
  • See what was tested and the scope limitations.
View the sample report ↗
Sample QA issue with reproduction steps and evidence
Demonstration report. Sample data with no client information.

From enquiry to quote

A clear scope before you decide.

  1. 01

    Describe your product

    Share a URL or short description, the journey to check and your deadline. Include a budget if you have one.

  2. 02

    Clarify your needs

    We clarify journeys, environments, access and the expected deliverable. We reply within 24 hours on business days.

  3. 03

    Receive the scope and cost

    Before work starts, we confirm the deliverable, dates, retest scope and billing model.

Team and approach

Know who will handle your testing.

Explore our experience, capabilities and the QA Lead’s role. See how we agree risks, report issues and hand over findings.

Test automation

Is regression taking longer?

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

Before you enquire.

Not sure which scope to choose?

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.

When does the delivery estimate start?

After scope is agreed and the required access is provided. Durations are estimates; start and delivery dates are confirmed in the proposal.

Can we start with a small engagement?

Yes. A quick review covers one critical journey. The findings help you decide whether to commission a wider audit or ongoing support.

What determines the quote?

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

Describe your product. Let’s decide what to test.

A short description, the most important journey and your deadline are enough to start. We will clarify the scope and prepare a quote.

Request a quote ↗