> a client comes to me with a certain task, "Create a custom piece of software", is it my job as a consultant to go out and do research to find a third-party tool that does this job?

interesting point Larry, I've contemplated this in the past... the way I've opted to handle this is apart of my general development process. I have the client sign a legally binding engagement letter initially that covers the process of writing the spec. As I write the spec, I do some minimal research (well more than minimal if that app will be sold commercially) to see if there is anything out there 'ready-made' for any or all aspects of the proposed application. If so, and I think it's suitable thing to serve the client's needs, I include that as an option in the spec. Therefore I do everything I can to empower the client to make a well informed decision on how I should proceed.

Personally I feel that during this stage (gathering requirements & writing the spec) it is my job to tell the client what's available and what their best options are. So what if I give the bigger job away because I found a ready-made tool that can do the job... the client's best interests are served and that's really the bottom line of my job. I still get paid for the writing the spec, and the client holds me in high regard for be honest.

But now on the other hand, if I dont happen to find something when I research possible options well then I note that in the spec somehows. Or if I find something that I dont consider a good fit and dont include in the spec as a posssible option, I still note in the spec. That way, come the end of the job my butt is covered no matter what and the client cant very well catch me off guard with "why did you reinvent the wheel when there is already a product out there like this?"