Absolutely, David. And as I said, the NEXT project may be one it applies to. Certainly I used a similar argument on the project BEFORE this - I just didn't have it formally laid out. Next time I'll be able to use the argument and even call it "Value Based Pricing" which will sound MUCH more important (read expensive). < grin >

Thanks,
Barbara

>Barbara,

>The idea Cindy mentioned was taught in a consulting seminar I attended years ago -- they called it "value-based pricing". It's the idea that a project should NOT be based solely on how much time we spend producing it, but rather on the value to the business.
>
>From that perspective, you can sometimes find projects that are worth $30,000 to a client, that cost only a few hours to develop. If you are locked in to hourly pricing, you will probably feel guilty about the above scenario, but the business owner may feel that the price is very fair.
>
>I'd say add "value-based pricing" as an alternative view on every project -- it can often keep you from unreasonably underpricing a job due to fear of client's reaction.