# Hire manual testers who test your releases by hand, inside your team

> Hire Manual Testers for Your Team | Zapple.Tech. Canonical page: <https://zapple.tech/services/hire-manual-testers/>

Hire manual testers through Zapple.Tech when you set your own testing priorities and need more hands to test releases by hand. You describe the role, we propose testers, you meet them, and they join your stand-ups, sprints and tracker for exploratory, regression and end-to-end checks. An engagement can start within two weeks of your go-ahead.

## What you can order

- **Manual testers for exploratory testing of new features**: A tester takes each new feature as it lands, tries the paths a user would and the ones nobody planned for, and reports what broke.
- **Manual testers for regression passes and release checks**: A tester runs the regression pass before each release, on the journeys you name in the role brief as the ones that must not break.
- **Manual testers for end-to-end checks of key journeys**: A tester walks whole journeys from the user's side, such as sign-up to first purchase, on web and on mobile.

## 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](/services/hire-test-automation-engineers/) or
[automate regression tests](/services/regression-automation-testing/).

## 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](/services/manual-testing/). If the role is wider than manual testing, see
[hire QA engineers](/services/hire-qa-engineers/). The table on this page sets the three side by side.

## How does hiring a manual tester work?

1. **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.
2. **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.
3. **Agree the terms.** The quote says how many testers, for how long, the notice period and how a tester is
   replaced.
4. **Start in your sprint.** The tester joins your stand-ups and works from your tracker.
5. **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](/services/manual-testing/) 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](https://testomat.ai/testeiya/) and [Explorbot](https://testomat.ai/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](/services/hire-test-automation-engineers/) |
| You need developers who write and fix Playwright tests | [Hire Playwright developers](/services/hire-playwright-developers/) |
| The work is your iOS and Android app builds | [Hire mobile app testers](/services/hire-mobile-app-testers/) |
| You want a whole team with a lead of its own, working to your priorities | [A dedicated QA team](/services/dedicated-qa-team/) |
| You want an outside company to take over the testing of the product | [QA outsourcing](/services/qa-outsourcing/) |
| You want a written plan before you hire anyone | [A one-week QA audit](/services/audit-and-assessment/) |

## Who you are hiring from

The company behind your tester has been [on the market since 2015](/about/). Its founders created
[CodeceptJS](/codeceptjs/) and Codeception, two open-source testing frameworks, and also built Testomat.io and
Testomat.ai. Clients have left [more than 50 testimonials](/what-our-clients-say/). 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.

## What hiring manual testers does not solve

A hired tester works under your direction, so the decisions around testing stay with you.

- A tester tests what your team puts in scope. What gets priority, and whether a release ships, are still your calls.
- Manual regression grows with every release. At some point the passes that repeat have to be automated.
- A tester needs access, test data, a test environment and one person who answers product questions, all arranged by your team before the start.
- One tester is not a QA function. If nobody owns the test strategy, look at a dedicated QA team.
- AI can draft a bug report, but it cannot tell whether the defect is real. The tester confirms each draft against the product first.

## Three ways to get manual testing done, by who directs the work.

| Option | Who directs the work | What you get | Choose it when |
| --- | --- | --- | --- |
| Hire manual testers | You, task by task | People in your team who test by hand | You have someone to set priorities and need more hands |
| Manual testing services | Zapple.Tech, against an agreed scope | Tested releases and a written view of what to keep manual and what to automate | You want the result, not the people |
| Hire QA engineers | You | Engineers who test and also automate or shape the test process | The role is wider than manual testing |

## How the work runs

1. **Role brief** (Your form, then one call): You send the role through the form on this page. On one call we then write down what the tester will test by hand, how often you release, which tracker and tools they will use, how long the term is and which release they test first.
2. **Meet the testers** (Agreed with you): We put testers forward against the brief. Ask each of them how they would test a feature like yours and how they write up a defect, then choose who joins. The start date is fixed once you have chosen.
3. **Ongoing** (For the agreed term): An engagement can start within two weeks of your go-ahead. The tester works in your sprint and reads stories while they are written. Once a month has passed, we sit down with you, compare the brief with the work the tester actually did, and adjust it.

## FAQ

### What does a manual tester do?

A manual tester tests the product by using it. They explore new features, run the regression pass before a release, walk key journeys end to end, check a feature against its story and file bug reports with steps and evidence in your tracker. They can also read stories before code is written, because QA is involved at every stage of delivery.

### Should we hire manual testers or automate our tests?

Hire manual testers for what changes or is hard to script, and automate what repeats. A changing UI, a rare flow, wording and usability are better tested by a person. The checks that run on every release are the ones to automate, so hire test automation engineers or automate regression tests for those.

### What is the difference between hiring manual testers and outsourcing manual testing?

Hiring means the testers join your team and you direct them task by task. Outsourcing means Zapple.Tech runs the testing against an agreed scope and you receive tested releases and a report. If you want the result rather than the people, see the manual and exploratory testing services or QA outsourcing.

### How quickly can a manual tester start?

An engagement can start within two weeks of your go-ahead. What moves the date most is how soon the tester can get into your tracker, builds and test environment.

### Can we meet the testers before they join our team?

Yes. We propose testers for your role brief, you talk to each one, and you choose. The start date is fixed after that and goes into the quote.

### Can a manual tester run end-to-end tests across our whole product?

A manual tester can run end-to-end checks of the journeys you name in the role brief, such as sign-up to first purchase, and manual end-to-end testing is a current service. Covering the whole product is a question of scope and time, so the brief names the journeys and the first release.

### Do your manual testers use AI tools on our product?

Only the AI tools your team approves, and none if your rules forbid them. Where they are allowed, they prepare test ideas, test data and first drafts of bug reports. The tester corrects every draft before it reaches you, and personal data is kept out of AI tools by default.

### What do you need from us before a tester starts?

Access to your tracker and builds, a test environment with test accounts, and one person who can answer product questions. The role brief also needs your release rhythm and the first release to test.

### How much does it cost to hire a manual tester?

We do not publish prices. What you pay depends on how many testers you need and for how long, both set in the role brief. Send the role through the form and a scoped quote comes back within one business day.

[Describe the role](https://zapple.tech/services/hire-manual-testers/#start)
