You might be a good candidate for using Hackystat if one or more of the following are true:
You are interested in lowering the overall cost of software engineering metrics collection and analysis in your organization;
You are comfortable with measurements of your product and process being sent to the Hackystat Public Server, or else you are willing to install your own Hackystat server within your organization;
You would like to do experimental research in software engineering, and are interested in a building a controlled environment with standardized measurements of product and process;
Hackystat has defined sensors for a significant subset of the development tools you use, and/or you are willing to help us develop sensors for those we do not currently support;
You would like to do research on software metrics, and would like to use Hackystat as infrastructure for building new tools and techniques.
On the other hand, you are probably not a good candidate for using Hackystat if one or more of the following are true:
The thought of sensors automatically collecting data about your actions in editors or build tools feels icky;
Your boss does not understand software metrics, and you fear that any data you collect can and will be used against you;
None of the tools you use have Hackystat sensors, and you are not interested in helping us develop support for them, and/or you use tools like Notepad for your software development for which Hackystat cannot provide a sensor.