In most cases, finding a requirement problem in a requirements review is far cheaper than waiting until the application is designed, coded, built, and intesting to find the problem.
If your QA team has been together for a while, and if it's become effective in its testing, then it must have built a fair number of automated tests and a framework in which to run them.