Scope the Package
Four client requests. Inside the package, or a paid extra?
Scope the Package
Productised QA means selling testing as a fixed package instead of hourly work: for example, a pre-launch sweep of a web app's main journeys on named browsers and phones, with a report and automated smoke tests, delivered in a set time. Small startups and agencies that have no QA team buy this kind of package. Automation testers already have the skills; what's new is defining the package and finding buyers.
Try this first: are you ready to sell testing?
(Takes about a minute; answers stay on your device.)
- Have you written a test plan that a manager signed off? (yes / no)
- Can you set up Playwright or Selenium from scratch? (yes / no)
- Have you explained a bug to a non-technical person? (yes / no)
- Are you comfortable quoting a fixed price for fixed work? (yes / no)
- Would you enjoy finding your own clients? (yes / no)
Four or five yeses: this bridge is short for you. Two or three: still reachable. Fewer: start with the automation tester role page and come back.
Build the package: scope, sweep, report
Design one package and run it once for free or as a demo.
- Write a one-page scope: journeys covered, browsers and devices, turnaround, what's excluded.
- Run it on a public demo app or a friend's startup (with permission).
- Deliver a sample report: summary, severity table, screenshots, and steps to reproduce.
- Hand over a small Playwright smoke suite with a README.
The scope page and sample report are your sales material.
Automation skills that become a product
Wrote automated regression suites. In the new role: deliver smoke tests as part of a package. Wrote test plans. In the new role: write a clear scope page buyers can sign. Logged bugs in Jira. In the new role: write a client-friendly bug report. Ran cross-browser tests. In the new role: list exactly which browsers and devices are covered.
The new parts are pricing, saying what is not included, and finding clients. Crowdtesting platforms can be a bridge while you build a client list, but read their terms carefully.
Your realistic 90 days
You can already test a web app end to end. Productised QA packages that skill with a fixed scope, a fixed turnaround and a report a founder can read. You'll design the package and run it once.
Assumes 2–3 hours a day alongside job applications, a laptop and a phone, and free plans only. Every step has a smaller version and a way to pause. Use them. It runs in three blocks of 30 days, each ending with a signal that you're on track. A signal is not a promise of a job or income.
What AI changed in your old tasks
| You used to… | Now you… |
|---|---|
| Wrote automated regression suites | Deliver smoke tests as part of a package |
| Wrote test plans | Write a clear scope page buyers can sign |
| Logged bugs in Jira | Write a client-friendly bug report |
Your first 7 days
| Day | Task | Done when |
|---|---|---|
| 1 | List the 5 bugs you're proudest of finding | 5 stories |
| 2 | Write a draft one-page scope for a pre-launch sweep | Draft done |
| 3 | Pick a public demo app to test | App chosen |
| 4 | Run the sweep on two browsers and one phone | Notes saved |
| 5 | Write the sample report | Report done |
| 6 | Write 3 Playwright smoke tests | Tests pass |
| 7 | Save 10 QA contract or freelance postings | 10 links |
Days 1–30: A package you can show
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Polish the scope, report and smoke suite | about 10 hours over 3 weeks | package folder | Report only. | Stop at the end of the step you're on and write two lines about where you stopped. Pick it up from those notes later. |
| Offer one free sweep to 3 founders or agency owners | about 2 hours | 3 offers | Just one instead of 3. | Optional. If reaching out feels like too much this week, skip it and put the time into your proof. |
Signal by day 30: Someone asks what the package costs.
Days 31–60: First real client
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Run a sweep for a real client (paid or free) and collect a testimonial | about 10 hours | delivered report | Half scope. | Put it on hold until your current interviews are done, then come back to it. |
| Apply to 8 QA contract roles while you build clients | about 4 hours | 8 logged | Apply to 4 QA contract roles while you build clients. | Stop sending for now. Keep a list of who you've contacted so you can follow up later without doubling up. |
Signal by day 60: A paid sweep or a serious enquiry.
Days 61–90: Repeatable
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Turn your process into a checklist and template | about 3 hours | checklist | Outline. | Write it as a draft and publish later. A saved draft still counts. |
| Ask 2 clients or contacts for referrals | about 1 hour | 2 asks | Just one instead of 2. | Optional. If reaching out feels like too much this week, skip it and put the time into your proof. |
Signal by day 90: A second client or a repeat booking.
Job-hunt moves that matter for this route
- Search 'QA consultant', 'freelance QA', 'contract test engineer' and 'pre-launch testing'.
- Startups, agencies and founders' communities are the main buyers.
- Lead with the scope page and sample report.
One search that fits your background
The full set of search strings for this move is on the route page. They work on LinkedIn, Naukri and foundit; Instahyre and Cutshort are worth a weekly look too. Add your old job title to any of them with AND, so recruiters who want both skills find you first.
The two worries we hear most about this move
I've never found my own clients. Where do I start? Start with people you know: ex-colleagues who joined startups and agency owners. One free sweep with a testimonial is your first sales asset. Isn't fixed pricing risky? It is if the scope is vague. That's why the scope page lists exclusions and one re-test round. Anything else becomes a paid extra.
Other worries, such as age, a career gap, no degree, English, family pressure and savings, are covered on the route page and the role page.
Your 30/60/90 quests
XP: learning 20 · proof 60 · outreach 40. Ranks: Wayfinder → Builder → Pathmaker. Progress stays in your browser only.
Testers ask about productised QA
Do I need a company? Not to start. Check tax and invoicing rules with a qualified adviser when income starts. What about crowdtesting? It can fill gaps between clients. Pay and availability vary; read each platform's terms.
Scams aimed at freelance testers
Be careful with "test tasks" that are really unpaid client work, recruiters asking for fees, or anyone asking for OTPs or UPI PINs. Use official domains only. Report: cybercrime.gov.in / 1930 (India), ReportFraud.ftc.gov (US).
QA package pricing: not verified
We haven't verified pay data for productised qa roles. Rates differ by city, company and contract type.
Next: route page · Automation Tester role page · Quiz
Quick quiz: does this path fit?
Answer each, then press Check. Every answer explains itself.
Make your Path Card
A shareable reminder of where you're heading. The day count starts the first time you open this page; quest XP comes from your log above.
Scam check before you apply anywhere
- Real job and gig platforms are free to join. Never pay a "joining" or "training" fee.
- Never share an OTP or UPI PIN — no genuine employer needs them.
- Use official domains only; type the address yourself.
- India: report at cybercrime.gov.in or call 1930.
- US: report at ReportFraud.ftc.gov.
Small steps, every day.
Each quest has a smaller version for hard weeks, and a pause button. Nothing is lost.
Keep exploring
Sources
Checked 25 Oct 2026. We opened every link below ourselves. Search volumes on this site come from OpenSEO keyword research (Oct 2026).
| What we checked | Where |
|---|---|
| ISTQB (testing certifications) | istqb.org |
| Playwright documentation | playwright.dev |