1 checklist, 1 timebox, 1 report: the whole product

A short animated timeline plays a small shop's launch morning backwards: 11:40 the owner is reading angry messages; 10:15 the payment page fails on one phone browser; 9:00 a coupon field accepts negative numbers; the night before, nobody tested on a phone. At each stop, a gentle prompt asks: "Which line of your checklist would have caught this?" Tap a checklist line to "un-break" that moment. When the timeline is fully rewound, the screen shows a calm launch — and the checklist lines you tapped become the first draft of your own sweep checklist, saved only on your device.

Tick what you're confident in today; the gaps show you what to learn first.

• Device coverage
• Accessibility basics
• Forms and payments
• Content and links
• Performance feel
• AI-feature check

Most manual testers light up forms, content and devices immediately. Accessibility and the AI-feature check are the two most testers add in month one.

Each entry: what it looks like, where you already did it, how it shows up in a sweep.

The exploratory eye Looks like: noticing that the "Apply" button works but the total doesn't change. You did it: every time you wandered off the script and found the real bug. In a sweep: a timeboxed exploratory session on the riskiest flow, logged as a charter.

Device stubbornness Looks like: refusing to sign off until it works on a cheap Android phone, not just your laptop. You did it: compatibility rounds. In a sweep: a small, named device matrix. Three devices you actually own is honest; thirty you don't is not.

The bug report Looks like: steps, expected, actual, severity, screenshot. You did it: thousands of times. In a sweep: this is the deliverable. A small business owner has never seen a good bug report. Yours will look like magic.

Saying no politely Looks like: "That's outside this release; let's log it for the next one." You did it: triage meetings. In a sweep: the scope line in your proposal. Without it, a two-day sweep becomes a two-week favour.

The AI-feature check (new) Looks like: asking the shop's new chatbot about the refund policy and checking the answer against the actual policy page. You didn't do it before — but it's the same instinct. Many small sites now add chatbots or AI search. A short check against the OWASP Top 10 for LLM applications (2025) gives you vocabulary for what can go wrong: prompt injection, sensitive information disclosure, misinformation. Keep it simple and harmless; you're checking answers, not attacking anything.

Here's a shape I'd start with. Change the numbers to fit your hours.

Write this as a one-page offer. The fixed scope is what makes it easy for a busy founder to say yes.

While you build clients, crowdtesting can bring in some work and keep your testing sharp. Use only the platforms we checked (21 Oct 2026):

• uTest — listed. Community crowdtesting; work volume varies.
• Testlio — listed. Managed testing network; selection-based.
• Test IO — with caution: payouts can be small and irregular.

All of them are free to join, and you should never need a VPN. Treat platform work as runway, not a salary. If a "platform" asks for a registration fee, a training fee or your bank login, walk away.

You need proof before you pitch. Two routes to it:

1. A friend's or relative's site, with written permission. A WhatsApp message saying "yes, please test my site, here's the scope" is enough to start. Never test anything you haven't been invited to.
2. A public demo store built for practice. Several open-source e-commerce projects publish demo sites meant for exploring. Read the site's terms first and stick to normal user actions.

For each, write the report exactly as you'd deliver it to a paying client: summary, ranked issues, steps, screenshots, and three plain-language recommendations.

Mentor's honest advice: don't start with marketplaces. Start with people who are about to launch.

• Small agencies and freelance web developers who build sites but don't test them. They can resell your sweep.
• D2C brands announcing a new site or app.
• Coaching institutes, clinics and local businesses moving bookings online.

A short message works: "I'm a QA tester with [X] years' experience. I run a fixed two-day pre-launch sweep on [n] pages and 3 devices, with a ranked bug report. Here's a sample report. Would it help before your launch?"

You know how releases go wrong: the untested payment page, the broken mobile layout, the email that never sent. Small product teams often have no tester at all. Productised QA means offering a fixed, clearly defined testing package they can buy. You'll build it from your own release checklist.

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

Your first 7 days

Days 1–30: A sample report and a package

Signal by day 30: One founder replies to your sample report.

Days 31–60: First real checks

Signal by day 60: A founder asks for the full package.

Days 61–90: Repeatable

Signal by day 90: A repeat request or referral.

The two worries we hear most about this move

Can I really sell QA as a package? Some small businesses and startups do pay for fixed-scope testing (a launch sweep, a checkout check), but finding them takes time. Start with people you know and keep applying for jobs alongside. How do I set a price without data? We don't publish pay figures because we haven't verified them. Price by hours and scope, check what similar services list publicly, and start with one paid or free pilot to learn how long the work actually takes.

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.

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.

Job-hunt moves that matter for this route

• Founders who just launched (Product Hunt, Indie Hackers, LinkedIn) are realistic first buyers.
• Lead with a free 3-issue mini-report. It shows value fast.
• Write scope and exclusions clearly to avoid endless re-testing.

We haven't verified pay data for QA sweeps or crowdtesting. Look at what local agencies and freelancers in your city publicly charge, then set your own price.

Two scams target new freelancers. A "client" sends more money than agreed and asks you to refund the difference; the original payment later bounces. A "testing platform" asks for a joining fee or software purchase. Never share OTPs or UPI PINs. Use official domains only. Report in India at cybercrime.gov.in or 1930; in the US at ReportFraud.ftc.gov.

Do I need a company or GST registration first? Rules differ by situation; this isn't tax or legal advice. Many people start by checking with a CA once income begins.

Can I do this while job hunting? Yes. A two-day sweep fits around interviews, and the reports are good interview stories.

Take the quiz · Back to Manual tester · Route: Productised QA · Also: AI evaluator · AI red-teamer