What's the organization of your tests? Different project suites? One suite with multiple projects? One project with multiple test items?
We have a setup where the test itself determines what needs to be tested based on different criteria. So from the command line, we send in things like an environment, client name, etc., and whether we're running an entire project suite, or a single project. Then within each project, the test items determine whether they need to be executed based on the command line parameters and what is found on the screen.
Kicking off tests in an automated way, and knowing what tests to run has been a negative for TestComplete for some time. We've figured out workarounds, but it'd be nice if more was supported out of the box.