How we work
How we work: from a free call to a tested release
Working with BugsQA is simple. We start with a free call to understand your product, recommend the plan that fits, then test, report and retest until your release is ready. Here is every step.
- ✓Free consult call
- ✓We recommend a plan
- ✓Kickoff
- ✓Test plan
- ✓Testing and bug reports
- ✓Retest and sign-off
Six steps, no surprises
Each step has a clear output, so you always know what is happening and what you will get next.
- 01
Free consult call
A free 30-minute call about your product: what you are shipping, where it runs, your release dates, how you test today and what worries you most.
You get
Honest advice on what to test first, even if you decide not to work with us.
- 02
We recommend a plan
Based on the call, we recommend the plan that fits: Release QA, Ongoing QA, QA automation, or an hourly contract for smaller or irregular work.
You get
A written proposal with scope, platforms, timeline and price.
- 03
Kickoff
We sign the agreement (and an NDA if you want one), get access to your builds and test accounts, and join your bug tracker and chat.
You get
One point of contact and an agreed way to report and rank bugs.
- 04
Test plan
We map your key user flows and write test cases, starting with the areas where a bug would hurt most.
You get
A test plan you can review before testing starts.
- 05
Testing and bug reports
We test on the agreed browsers and devices: functional, exploratory and regression testing, plus automation where it pays off.
You get
Clear bug reports with steps, expected and actual results, environment, severity and screenshots or video.
- 06
Retest and sign-off
When your developers fix the bugs, we verify the fixes and check that nothing else broke before you release.
You get
A short summary of what passed, what failed and what is still open. On Ongoing QA, this repeats every sprint.
Pick a plan or pay by the hour
After the call we recommend one of these. You do not need to choose before talking to us.
Release QA
Best for launches, major updates and pre-release validation.
From
$1,500
fixed price / release
Ongoing QA
Best for teams shipping every sprint.
From
$1,700
per month, part-time (40 hours, about 10 h a week)
QA automation
Best once your core flows are stable.
From
$6,500
setup for your first suite
Hourly contract
Best for small fixes, one-off checks and teams with irregular release schedules.
Manual QA
$45/hr
Test automation
$55/hr
What we need from you, and how we keep you updated
To get started, we need
- A build to test: a staging URL, a TestFlight invite or an APK
- Test accounts, or a way for us to create them
- The user flows that matter most to your business
- Where bugs should go (Jira, Linear, GitHub, Trello or a shared sheet)
- One person on your side who can answer product questions
Missing something? That is fine. We sort it out together at kickoff.
While we test, you get
- Bugs reported as we find them, critical ones flagged right away
- Quick questions answered in Slack, Teams or email during your working hours
- A written summary at the end of each test cycle
- Weekly QA reports on Ongoing QA plans
We work from Colombia, in hours that overlap with teams across the US and Canada.
What clients say about our work
Reviews from our individual Upwork profiles, quoted as written.
5 out of 5 stars
“Great to work with. He knows testing very well and works efficiently.”
5 out of 5 stars
“Juan did a great job on this project. He always replied quickly and met every deadline, going above and beyond. He paid close attention to details improving the quality of the product and made sure customers were helped in the right way. His work was clear and well organized. I would be happy to work with him again in the future.”
5 out of 5 stars
“Camilo is an excellent SEO specialist and I’d trust him with any of our client work. Kudos and bravo for excellent execution!”
Is the consult call really free?
Yes. The first call is free and there is no commitment. We use it to understand your product and tell you honestly whether BugsQA is a good fit, and if it is not, we will still tell you what we would test first.
How quickly can you start testing?
Most projects start within 2 to 3 business days of signing, once we have access to a build and test accounts. If you have a release date coming up, tell us on the first call and we will plan around it.
Do I need to sign a long-term contract?
No. Release QA is a fixed-price project, Ongoing QA runs month to month, and hourly work is billed for the hours used. You can change or stop a plan with notice, as set in our agreement. Ongoing QA also starts with two risk-free weeks, and our nearshore QA services page explains every QA outsourcing model we offer.
Can we switch plans later?
Yes. Many teams start with Release QA or hourly testing to see how we work, then move to Ongoing QA once releases become regular, and add automation when the same regression tests keep repeating.
We already have a tester. Can you work alongside them?
Yes. BugsQA can add capacity before a big release, cover platforms your tester does not have time for, or take over regression so your tester can focus on new features. We follow your existing process and tools.
Free QA consultation
Book your free consult call
What happens next:
- 1
We reply within 1 business day
A QA lead reviews your request and asks about scope and platforms.
- 2
Free 30-minute QA consult
We map your app, risks and release schedule.
- 3
Proposal and test plan
You get a recommended mix of manual testing and automation, with a quote.
Email: contact@bugsqa.com