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 WorkTags: , charge per hour, charge per project, small businessThere are currently no comments.
Web developer, amateur photographer, traveller, and amatuer chef. Expect to find me writing code, visiting new places or trying a new recipe. I live with my wife in Olney, Maryland. Follow Me On Twitter!- Excited About PHP Again
- Rethinking The Technical Resume
- We The State, Not We The People
- Working To Defeat the Stop Online Piracy Act
- Diversifying This Blog
- What do you want the web to be?
- Why I Love Being An Engineer
- Validation Blind Spots Hurt Real Users
- Finding A Job Without A Recruiter
- Why Recruiters Are Bad For Your Career


