Services
Three services. Each scoped to a specific situation.
Every engagement is fixed-scope and fixed-fee. This page covers what each service includes, who it fits, and what you receive.
Where most engagements start
Release Readiness Review
Before a significant release, your team needs a clear answer to a specific question: is this build safe to ship? The Release Readiness Review is a focused manual testing engagement that answers that question directly.
We test the highest-risk areas of your release — core user flows, edge cases, error states, and anything that changed in this build — and deliver a structured report with a go/hold recommendation. Testing runs over a 3-business-day window. A 30-minute scope call before the window opens confirms what gets covered.
What your team receives:
- A complete record of every test case run, with pass/fail results
- Full bug reports with reproduction steps, screenshots, and a severity rating for each finding
- A release readiness checklist covering all tested areas
- A written go/hold recommendation with the reasoning behind it
For teams that ship regularly
Standing Release Coverage
For teams that found the Release Readiness Review useful and ship on a regular cadence, re-engaging from scratch before every release adds unnecessary overhead. Standing Release Coverage brings the same structured review to every release cycle on a standing basis, at a lower per-engagement rate.
Scope is agreed upfront and updated each cycle to reflect what changed. Context from prior cycles carries forward, reducing initiation overhead each time. The arrangement covers a minimum of 3 release cycles.
Same structured report and go/hold recommendation each cycle, with accumulated context from prior work.
For teams ready to automate
Regression Test Suite Setup
Manual regression checking before every release does not scale indefinitely. The Regression Test Suite Setup is a fixed-scope Playwright automation engagement targeting the flows most likely to cause a release incident — the ones that have come up repeatedly and are stable enough to automate.
The result is a working TypeScript test suite in your repository, covering 3 to 8 critical flows, with a walkthrough session and written handoff documentation. Your team owns and maintains it from there.
This engagement works best after a team has built up enough history to know which flows carry the highest regression risk.
Right fit
Who this is for
Startup and small software teams — roughly 2 to 15 engineers building a web application or SaaS product without a dedicated QA function. Most teams engage when they have a launch, a significant feature release, or a customer-facing milestone coming up and need more confidence in the build than internal review alone provides.
If your team already has an internal QA function or a large testing organization, this is not the right fit.
See the actual deliverable
The clearest way to evaluate a Release Readiness Review is to read the report. The sample report is a complete, real-format deliverable for a fictional B2B SaaS application. The format, depth, and reasoning are identical to what every client receives.
Read the sample reportPricing
Fixed scope. Fixed fee.
All engagements are fixed-scope and fixed-fee. The cost is confirmed before testing begins and does not change. There is no hourly billing.
The fee for a Release Readiness Review is based on the scope of the engagement — the number of workflows to cover, the complexity of the application, and any extended browser or device coverage needed. Scope and fee are confirmed on the initial call. Standing Release Coverage is priced at a lower per-engagement rate than individual reviews, reflecting the committed volume and reduced overhead per cycle. The Regression Test Suite Setup is priced as a fixed-scope technical engagement; scope and fee are confirmed after an initial scoping session.
Common questions
Before you reach out
What do we need to provide before testing starts?
A staging environment URL, test account credentials, and test data in the staging environment. Release notes or acceptance criteria are useful but not required. We work entirely in your staging environment — nothing touches production.
What happens if a serious issue is found?
Critical or blocking findings are flagged directly via the agreed communication channel as soon as they are confirmed, not held for the final report. Your team can start triaging before the report is complete.
How quickly can we get started?
The testing window is 3 business days. From first contact to report in hand is typically 5 to 7 business days, depending on scheduling and how quickly environment access can be set up.
More questions? Read the full FAQ
Have a release coming up?
Get in touch and we can confirm whether the timing and scope work. No commitment required.