Larry,

>Reading another post, the question was raised (at least in my mind), "What constitutes due diligence?".
>
>If 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? Shouldn't they have done that already before they came to me? If they wanted me to research something for them, then that would be the contracted task not the creation of something new.

I'm with the others. It depends... <g>

Here's the deal though.. I've seen enough times where a client comes and says, "I want a such & such program." I'll always try and figure out a way to ask them "why?" as the answer to this lets me know if they've thought there side through. IOW, I don't trust that the client knows what they really need. Remember, I'm an independent contractor in this case and I have IMO a fiduciary responsibility to give my client what is best for them as best as I am able even if it means less business initially for myself. Some may disagree but I will remain convinced that the quality of one's character is paramount here. Keep your word - even if it hurts. You'll be ok and you'll learn how to bid better. <g>

Many many clients don't really know what they need. They just are panicked that they might be left behind and they are grasping at traws and making emotional, not rational, decisions at that point. Too many consultants take advantage of folks at a time like this for the easy sell. Bad bad bad IMO...

There are too many folks who want to get rich quick off the client's back and that is simply just not right IMO.

Charge them for the discovery time if it's an area I'm not familiar with and take some off the back end of the contract if I get the work as a courtesy for them paying me to learn a new business if you'd like.