What does a manual tester do in your team?
A manual tester checks your product the way a user meets it. In your team, a manual tester can take on five things in each two-week sprint:
- Exploratory sessions on new features, before any script exists for them.
- A manual regression pass before a release, on the journeys that must not break.
- Manual end-to-end checks of the journeys that earn money, from the first screen to the last.
- Acceptance checks against the story, so “done” means what the story said.
- Bug reports with steps and evidence in your tracker, written so a developer can reproduce the defect.
QA is involved at every stage of delivery, so the tester also reads stories while they are written. A question asked before code is written is cheaper than a defect found after.
When should you hire manual testers instead of automating?
Hire testers for the work that changes, and automate the work that repeats. This is practitioner judgement, not a measured rule.
- The interface is still changing. A script written today breaks next sprint.
- The flow is rare or runs once, such as a migration or a launch. Writing automation costs more than running it.
- The question is about wording or usability. A script confirms a label exists. A person notices it is confusing.
- The flow is slow to automate, for example one that depends on a person or a device.
The checks that run on every release are the ones to automate. For those, see hire test automation engineers or automate regression tests.
Hire manual testers or outsource manual testing: which fits?
Decide who directs the work. If you have someone to set priorities and need more hands, hire testers into your team. If you want the result and not the people, have Zapple.Tech run it: see the manual and exploratory testing services. If the role is wider than manual testing, see hire QA engineers. The table on this page sets the three side by side.
How does hiring a manual tester work?
- Send the role. Use the form on this page. One call follows, and the answers go into a role brief you approve: what to test by hand, how often you release, the tools, the term and the first release.
- Talk to the testers. We put testers forward against that brief. You ask each one how they would test your product, and you decide who joins.
- Agree the terms. The quote says how many testers, for how long, the notice period and how a tester is replaced.
- Start in your sprint. The tester joins your stand-ups and works from your tracker.
- Look back after a month. The brief is compared with the work done so far and changed where it was wrong.
Not sure you need a person in your team? Start with a one-week exploratory test of one release, described on the manual and exploratory testing services page. Pricing is by quote.
How do manual testers use AI, and what does AI not do?
AI tools can draft test ideas from a story, prepare test data and write the first version of a bug report. The team uses Testeiya and Explorbot, agents from Testomat.ai: Testeiya is a QA agent that works with Testomat.io, MCP, GitHub, GitLab and Jira, and Explorbot is an AI agent that scans a live UI, runs exploratory tests and generates Playwright code. It also uses Playwright MCP, and Testomat.io for test management. Zapple.Tech was founded by the founders of Testomat.io and Testomat.ai.
What AI cannot do is use your product the way a customer does. It does not notice that a flow is confusing, and it does not decide which defect matters for the release. The tester does both, and fixes every AI draft before it reaches your tracker. Which tools may touch your product is your decision; personal data stays out of them by default, and where your rules allow none, the tester works without any.
What if a manual tester is not what you need?
| If this is closer to your situation | Look at |
|---|---|
| You need people who write and maintain test code | Hire test automation engineers |
| You need developers who write and fix Playwright tests | Hire Playwright developers |
| The work is your iOS and Android app builds | Hire mobile app testers |
| You want a whole team with a lead of its own, working to your priorities | A dedicated QA team |
| You want an outside company to take over the testing of the product | QA outsourcing |
| You want a written plan before you hire anyone | A one-week QA audit |
Who you are hiring from
The company behind your tester has been on the market since 2015. Its founders created CodeceptJS and Codeception, two open-source testing frameworks, and also built Testomat.io and Testomat.ai. Clients have left more than 50 testimonials. Your tester follows that company’s test process and its rules for AI drafts. Whether a tester is right for your product is for you to judge in the conversation before they start.