Why I Built a Lightweight Manual QA Hub

I’m a QA professional with 10+ years on the tools, and a military veteran. I like hard problems and clean solutions. Over the years I kept running into the same mess. Manual testing is still vital, but the work is split across docs, Jira and scrappy scripts. Devs are shipping faster every week, yet testers are stuck herding files. The work isn’t slow. The setup is.

So I built QA Copilot. Not a ChatGPT wrapper, not a gimmick. It’s my testing playbook turned into a product. A lightweight, pay as you go Manual QA Hub for small teams, contractors and indie SaaS builders who want proper test discipline without a heavy, pricey suite.

What it does

• Site Scanner: point at a live page, get structured test ideas in seconds

• Test Generator: turn user stories or AC into clear test cases

• Story Sizer: quick effort calls so sprint plans are real, not hopeful

• Script Converter: take Playwright or similar and make readable steps for reviews

• Jira Import: pull issues in and kickstart coverage

• Test Hub: keep cases and suites tidy, not scattered across five tools

Why now
CI and automation help your pipeline, great. Real users still break things in the gaps. Manual QA catches the awkward bits. The time sink is the prep. If setup takes hours, you test less or you test too late. QA Copilot shrinks that faff. Scan, generate, size, convert, organise. More time testing, fewer hoops.

Who it’s for

• Small product teams that want confidence without enterprise overhead

• Contract testers who need quick setup and client friendly outputs

• Indie builders who ship fast and want a simple QA layer that grows with them

What I believe

• Keep it simple. You shouldn’t need a training course just to manage tests

• Pay for what you use. Top up when you need a push, keep costs sane

• Human first, AI assisted. Let AI draft the boring bits, keep judgment for risk and edge cases

What it isn’t

• A replacement for every enterprise suite. If you need heavy compliance, you already know your stack

• A chatbot in a fancy coat. Every feature maps to real testing flow

What’s next
Cleaner exports and reporting, a lightweight bug reporter, and steady tuning based on real feedback from testers who use it daily.

If you’ve felt that gap between fast dev cycles and slow prep, I built this for you. Let’s level the playing field and keep manual testing sharp, not slow.

Cheers.