Independent release sign-off.
A discrete, time-boxed engagement - the final gate before a specific build goes out. We return a clear pass or fail with supporting evidence.
Request a quote →A structured final gate - before it goes to a publisher, a platform, or live.
Validation is not ongoing QA. It's a structured final gate - a discrete engagement against a specific build at a specific moment. We review the build against defined release criteria and return a written verdict: pass, conditional pass, or fail, with the evidence behind it.
Studios use this service when they want an independent second opinion before a build goes to a publisher, a platform, or live. You get a short signed document - the kind you can hand to someone who wasn't in the room when the decision was made.
What you receive at the end of a validation
- Critical and high-severity bug sweep across the full build
- Regression check on all previously reported and fixed issues
- Platform-specific checks: crashes, save/load, achievements, network behaviour
- Performance baseline check
- Localisation spot-check if applicable
- Signed release readiness report with open issue list by severity
- Explicit recommendation: ship / resolve these first / do not ship
How a validation engagement runs
Brief & criteria
You share the build, the target date, and any known risks or conditions. We define the release criteria together before we start - the bar is documented, not assumed.
Severity sweep
Full pass focused on critical and high-severity issues. Crashes, data loss, blocking progression, platform requirements - anything that would prevent a clean release.
Regression check
All previously filed issues retested in the build under review. No assumed fixes - we verify each one closes cleanly with no regressions introduced.
Verdict & sign-off
Written verdict with full evidence: pass, conditional pass (specific conditions listed), or fail (blocking issues documented). Signed and ready to hand over.