Functional behaviour
Check whether forms validate, actions complete, errors are explained, and the product responds as expected. Examples include sign-up, account changes, and checkout paths.
Services
Testing that gives your team clear next steps.
We review agreed user journeys and product behaviour, then give your team reproducible findings and a practical view of what to address before release.
The starting offer
Release Readiness Review
An independent review of your most important customer journeys before launch or handover.
A focused starting review
Start with up to three agreed user journeys in one website or app build, checked on two agreed browser or device setups. We confirm the environment, test accounts, permitted actions, and dates before testing begins.
We provide a written report and talk through the findings with you. The quote confirms the exact journeys, setups, price, delivery date, and whether a retest of fixes is included. Extra journeys or environments can be added to the scope.
Tell us about your releaseWhat you receive
- Coverage summary of what was checked
- Prioritised bugs with reproduction steps
- Screenshots or recordings where useful
- Separate usability observations
- Browser, device, and environment details
- Handover discussion of the findings
Areas of review
What we can examine.
The exact checks depend on your product and agreed scope.
User journeys
Follow complete tasks from a user's point of view, including the steps between screens. We note broken paths and confusing moments that can prevent completion.
Browser and device behaviour
Check the agreed browsers, screen sizes, and devices. We document the environment for each finding so developers know where to reproduce it.
Regression checks
After a change or fix, revisit agreed flows to see whether the issue is resolved and whether those key journeys still behave as expected.
How a review works
A clear scope. A useful handover.
Testing starts only after we agree on the environment, access, dates, and permitted activities. We prefer test accounts and representative data.
We record what we actually observe, separate bugs from observations, and discuss the priorities with your team. The written quote sets the price, timing, and any retest allowance before work begins.
What is outside the standard review?
Full security assessments, load testing, accessibility certification, exhaustive device coverage, and unlimited retesting are not included by default. We make exclusions explicit in the scope.
View an illustrative deliverableQuestions
Before we test.
Have a different product or deadline? Tell us about it and we can discuss a suitable scope.
Do you need our source code?
Not for a standard functional review. We agree on access and test accounts during scoping.
Can you test a staging site?
Yes. We prefer a safe test environment with representative test data where possible.
Can you test a live product?
Only within a written, agreed scope and with the owner's authorisation.
Do you test mobile apps?
We can discuss the platform, build access, devices, and specific journeys during scoping. We only quote work we can cover properly.
How long does a review take?
It depends on the agreed journeys, environments, access, and reporting depth. We set the timeline in the quote.
Is this a penetration test?
No. The initial service is functional and user journey testing. Specialist security work requires a separate scope and method.
Your next release
Tell us what needs checking.
We will discuss the important journeys and propose a practical scope and quote.