For teams shipping every month
A QA owner for every release, on a monthly retainer
If you ship every few weeks, booking QA one release at a time means explaining the product again each time. The retainer gives every release an owner who isn't the person who wrote the code. That covers test cycles matched to your cadence, defect triage, regression before each release, release notes, risk reporting and go/no-go support.
What you get
What’s included
Test cycles on your cadence
Cycles planned around your release schedule, so testing is ready when the build is.
Defect triage
New defects reproduced, prioritized and passed to developers with steps, so the fix list reflects what matters to users.
Regression before each release
The regression checklist kept current and run on every release candidate.
Release notes
Written notes on what changed in each release, for your team and your users.
Risk reporting
A short summary before each release of what was tested, what's still open and what risk remains.
Go/no-go support
A written recommendation for each release, with the evidence behind it.
A good fit if
- Product teams releasing every few weeks without a dedicated QA person
- Startups after launch, where each update risks breaking something users rely on
- Teams on an app maintenance retainer who want testing owned separately
- Founders who keep booking one-off test cycles before each release
Not included
- Engineering fixes, which sit with your developers or an app maintenance retainer
- Security, privacy or clinical safety certification
- Building an automated test suite, which is scoped separately
How it runs
From kickoff to handover
- Month 1
Learn the product
We agree the critical flows and device matrix, and set up or adopt your test strategy and regression checklist.
- Each cycle
Plan around the release
Testing is scheduled against your release dates and the changes going into each build.
- Each cycle
Test, triage, report
New work tested, regressions checked, defects triaged and written up for your developers.
- Each release
Go/no-go and notes
A risk summary, release notes and a written recommendation before the release goes out.
Questions
Questions about Ongoing QA & release management
What decides where we land in the monthly price range?
The work involved: how often you release, how many platforms you ship on and how wide the device matrix is. We'll quote a monthly figure once we've seen your release schedule.
Can we cancel?
Yes. Retainers run on monthly cycles.
Should we start with QA & Release Readiness?
If you don't have a test strategy, device matrix or regression checklist yet, it makes a good first month, because the retainer runs on those. If you already have them, we can start the retainer directly.
How does this work alongside our developers?
QA stays separate from whoever writes the code, whether that's your in-house team or our app maintenance retainer. Defects go to the developers with reproduction steps, and each release goes out with an owner who didn't write it.
Is this the same as app maintenance?
No. Maintenance is engineering: monitoring, fixes, dependency updates and releases. This retainer is testing and release ownership. Many live apps need both, and they're priced separately.
More from QA & Release
Keep exploring
Often paired with this
Work with us
Ready to start Ongoing QA & release management?
Tell us about your business. We'll confirm the scope and send you a start date.