The time versus the value
August 10th, 2008 @ 10:20 pmFreelance Switch once did a blog entry on the benefits of charging by the project, rather than by the hour. They argue that the benefits outweigh the costs, including the benefit of increasing efficiency.
I’ve often debated this myself, and I’ve wondered whether or not charging by the job was better than by the hour. When a person charges by the hour there’s always an unknown for the client, and always a question about whether or not the contractor should be efficient and get the job done quickly, to their detriment financially.
I debated this with a few people, including Keith Casey, who seemed to think that being efficient for a client was a benefit in that they would see the developer as an efficient, honest individual. After my discussions I think I’ve devised a method.
I think it might be best on some projects to charge by the hour. I think that the points mentioned in the Freelance Switch article are reasonable. I don’t favor abandoning the by-the-hour model entirely, since some clients will prefer it or demand it, but I think that if we as developers start charging based on value (which is what every retailer does) rather than by the hour, we may see our business increase.
Tell me what you think in the comments.
The original work of Brandon Savage.
No related posts.
Categories: Business Management, Contract WorkThere are currently no comments.
Web developer, amateur photographer, lover of the outdoors and travel. Expect to find me writing code, hiking or visiting new places. I own Blueprint DC and live in Washington, DC. Follow Me On Twitter!- July Slides
- Some Thoughts On Software Licensing
- Interfaces Make Testing Easier
- Revisiting: Why Every Developer Should Write Their Own Framework
- The Fallacy of Sunk Cost
- PHP: The Good Parts – Book Review
- 1st Amendment, Meet 4th Amendment: The Gizmodo Search Warrant
- A Closer Look At ArrayObject
- TEK Webcast Notes
- Caching For WordPress – A TEK-X Webinar
