Beans

22
Jun
2012

As I have gotten better at what I do, I have gotten faster as well. The same type of complex website that took me 40 hours to accomplish 3 years ago, I can now do in 20 or less. I have only raised my rates about 25% in that time, so people actually are getting websites for a lot less money from me these days. And yet, people balk at an hourly wage that they consider to be too high. I am considering starting to quote project fees (which I hate to do) instead of hourly estimates, because then people can imagine hundreds of hours going into their project, whether it is true or not. This is the problem of bean counting, and I have been fighting against it my whole life. The quality of a project is almost completely divorced from the amount of time one puts into it, but people are loathe to understand that, mostly because they don’t have the intellectual tools at their disposal to evaluate quality. Hours are a fixed value that they can measure. In their head, more hours = more work = better product. People love the illusion of¬†quantifiable¬†results. But they are just that alas, an illusion. The crappiest designer in the world can spend 500 hours on something that won’t look as good as the best will produce in 5 hours. If the cost of the crappiest designer is $10 per hour and the cost of the best is $100, you just saved $4500 by hiring the best.