Earlier quoted context omitted.
How about if you invert it. If somebody came to you and asked for a system that can send emails when certain conditions are met in a database and track the results, would you assume that to write the program you would have to hang out with sales people? The actual work (in the two weeks to implement it) is development.
The actual work of being a lawyer is writing and talking, but just because you can write and talk doesn't mean you can be a lawyer. Every client I've ever had has asked "how many hours?" And "how much per hour?" If a restaurant wants to increase business by building a patio and they get a bid based with pricing based on increased business and not hours. They're gonna throw it away. Patio11 was in a unique position to…
That's when you explain you charge per project or per week instead of per hour, and the fee is based on value, because in the end they won't really care how many hours you spent as long as their problem is solved. (Similarly, if you _fail_ to solve their problem, they're not going to care how many hours you put in.)
I get this question from prospects too, and then I explain the above, and then we move on with the conversation.
And in my 4+ years of consulting, nobody's asked me _at the end_ of a project how many hours it took. At that point, as I said, it doesn't matter.