In my opinion .... considering the dynamic nature of projects and ever changing requirements and different amount of information available .... it is not easy to make a generic tool .... rather you can compile a set of guidelines of DOs and DONTs.
There already exist a set of parameters/guidelines to suggest steps and processes to follow on a high-level to estimate and analyze the project.
Teradata also has a proprietary Teradata Solution Methodology, which helps/guides the implementation team through the life-cycle of the project.
For sure, I know it won't fit into all project reqts :). However, if it fetches a good amount of information and results for projection, then it saves a lot. So on the points, I noted above, if there are some more to be added...
Visibility of the project phase and requirement of planning in the beginning, if it can spell out, then it will be helpful in many facets.