Every release breaks something, and we hear about it from users
We write automated tests (scripts that click through the app like a user) for key flows: signup, payment, checkout. They run before each release.
We find the bugs before your customers do
We test your web app by hand and with automated scripts, then hand you a clear report: what is broken, how to reproduce it, and how serious it is.
Quote and schedule after your brief
Who it's for
- SaaS founders who ship updates and worry about breaking things
- Companies that outsourced development and want an independent check
- Teams with no dedicated tester
- Online businesses about to start paid ads and send traffic to the site
Problems we solve
My vendor says everything works, but I can't verify it
We go through the app against a checklist and deliver a report with reproduction steps, screenshots and a severity for each issue. You get evidence, not assurances.
It looks fine on my laptop but customers see something different
We test across the main browsers and phone screen sizes. We also check forms, payments and the emails your system sends.
We pay for ads and visitors leave because of a bug
We test the full path from ad click to lead or purchase, so your ad budget isn't spent on a broken form.
What's included
- Requirements review and test scenarios (checklists)
- Manual testing of main and edge cases: empty fields, odd characters, double clicks
- Checks in Chrome, Safari, Firefox and on mobile devices
- Testing of forms, payments, authentication and transactional emails
- API testing (the data exchange between parts of the system) in Postman
- Automated tests in Playwright or Cypress for critical flows
- Basic checks of page speed and common security settings
- Bug report with reproduction steps, screenshots and priorities
- Re-testing after fixes (regression)
- Running tests in CI (automatically on every code change) if you have a repository
Choose the scope
Use a package to describe what you need. We agree on the quote and schedule after reviewing your brief and requirements.
01
Pre-launch audit
An app or site that is about to go live
- Checklist built for your product
- Manual testing of main flows
- Cross-browser and mobile checks
- Prioritised report
- One re-test after fixes
02
Manual + automated
A product in active development that needs protection from regressions
- Everything in the audit
- API testing
- Automated tests for 5–10 critical flows
- CI setup
- A guide to running and reading results
03
QA subscription
Teams that release monthly and have no tester
- Testing of each release
- Maintenance and growth of the test suite
- Regression before releases
- A report after every release
How we work
Brief and requirements
You describe the task and current workflow. We clarify requirements, choose a first stage and prepare a quote.
Pilot with a KPI
We start with one module and agree a measurable goal, for example covering payment and signup with tests. You see the quality of the work before paying in full.
Testing
We run the scenarios by hand and write automated tests in parallel. AI speeds up test data and draft scenarios, and a senior tester reviews everything.
Report and fixes
We deliver the report in your tracker: Jira, Trello or a spreadsheet. Your developers fix, and we re-test.
Handover
All tests, scripts and access are yours under the agreed terms. Payment is made in stages.
Scope and limits
- We don't promise a bug-free app. Testing lowers risk but does not remove it.
- We don't fix the code unless agreed separately. We find and document issues.
- We don't do full penetration testing. We only check basic security settings.
FAQ
What do you need from me to start?
Access to a staging environment, a few test accounts and a short description of the main user flows. If you have specs or designs, send them. If not, we help build the checklist.
Can you test on the live site?
A staging copy is better, so we don't create real orders or damage data. If there is no copy, we test carefully and only safe scenarios.
Why automated tests if manual testing exists?
Manual testing is good at finding new bugs. Repeating the same checks after every update is slow and costly, while automated tests do it in minutes. They are worth writing for stable, important flows.
Which tools do you use?
Playwright or Cypress for automation, Postman for APIs, BrowserStack or real devices for screen checks. We adapt to your tracker.
What does it actually cost?
We prepare a quote after reviewing your brief and requirements. A first stage can cover: checklist built for your product; Manual testing of main flows. Scope, payment and schedule are agreed before work starts.
Who owns the tests and access?
We agree on the handover of code, materials and account access before work starts. Third-party licences and services are listed separately when needed.
Start with your task
Describe your business, the outcome you need and your current workflow. We will clarify the requirements and prepare a quote after your brief.