Oh I'm with you there, Andy! I realised after I sent that email that I could have put that better. I agree that the rate you charge is in many ways a reflection of your knowledge and experience, and that knowledge and experience can lead you to put in more effort in some ways.
I still think, though, that your knowledge and experience adds to the value your client gets out of your web development service and whether you work it out by a higher hourly rate or by perceived total value, it's not important really. But think of it like this - just say you wrote a web application for a client. Then another client comes along and wants something similar. Do you start from scratch? Of course not. You'll adapt the previous app you built. It might take you 5 hours instead of the 50 it took to develop the first app. Do you only charge for 5 hours? No way. You charge for value to the client... that's the kind of thing I was thinking of. I'm not a programmer but that would equate to me spending half a lifetime(!) researching web standards and charging my first customer for all that time, then charging subsequent customers by the hour (thus a pittance) because it took me less time.... Before I tie myself into too many more knots - I think we're both saying the same thing in different ways. (I'm still trying to think of a way to put it better. LOL.) :-) Vicki. :-) Andy Budd <[EMAIL PROTECTED]> wrote: > > Regarding charging - like anything, the more experienced you get the > > faster you get so it's a bit silly to charge across a project on the > > basis of time spent. > > I agree with pretty much everything you've said apart from this. ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
