How to charge clients: flat fee vs. hourly rate?


Having been back in the freelance world for a while now, I once again have to deal with quoting my clients an hourly rate for long-term contract work on an ongoing basis. I've been able to raise my rate several times in recent years, and now it's to the point where most people balk when I give them the figure.

But in reality, the amount of work I can do in an hour is the equivelant to what might take a less experienced person twice as long (or longer). In addition, more experienced people can cut down on potential revision time and avoid costly problems in the future by utilizing the knowledge they've built up of their work. And in general, if you've performed the same skill for a while, you're going to have all the tools you need and be much more comfortable doing it. So one hour of my time can easily be equivelant to four hours of a less experienced person's time.

Unfortunately the average client doesn't see it like this. They just see a high number and look to the next person. That's why hourly rates are hard to use, especially on long-term, open-ended contracts.

A designer named Clay Butler wrote about this problem. He also points out that hourly rates actually punish good designers:

Another problem with charging by the hour is that it punishes for getting get better and faster. To keep up with your increasing speed and skills your hourly fee must keep rising. With an hourly rate you can paint yourself into a corner because at a certain point an hourly rate will just sound ridiculous, where the same total fee, when presented as a flat fee, sounds reasonable because it focuses on value received and not the commodity (hours).

Clay Butler's opinion is that a flat fee works for both the contractor and the client. But rather than calling it a flat fee, he calls it a "value-based fee."

His suggestions are good, but I'm not so sure they work for me, given the fact I mostly do long-term contract work rather than one-off, short-term projects.

The challenge I face is to try to avoid the sticker shock that potential new clients might feel. The best clients understand the high rate and everything factored into it, but many others don't. So I don't know if I've found the solution for this problem yet. If you have a solution to this, I'd love to hear it.

Close game-ending play in 19th inning of Braves/Pirates baseball game. Did the umpire get it right? You decide.

Normally when I mention Major League Baseball umpires on my blog, it's to rant about a bad call (like here and here). This time, however, the ump got one right. And this call was big, because it was the 19th inning (for those not familiar with baseball, games usally go for 9 innings unless there's a tie, and games can't end on a tie) and this play ended the game.

It's funny how, even when things are black and white, people still see all sorts of colors. It's pretty clear (based on the replay in the clip above starting at 2:08) that the tag was never applied (simple contact between players doesn't matter - the catcher has to touch the player with his glove or the ball directly). It's just about as close as a play can get, but umpire Jerry Meals made the right call because that contact wasn't made, yet he's getting tons of flak for it. I just don't understand how people don't see that the runner wasn't tagged.

Here's the clip from the Braves' broadcast, if you want to see it from some slightly different angles.

What do you think? Do you see what I see?

McDonalds and Microsoft: a winning partnership for bad design

I'm seriously thinking I need to start a blog that only highlights bad design. There's certainly enough content for it.

Today's episode features the instructions provided at McDonalds to connect to their free wifi. (But I'm kind of thinking if you can't connect to the wifi on your on, I'm not so sure this pamphlet will help...)

From the comments on the original TwitPic post:

Connecting to a WiFi network with a PC is the equivalent of a hostage negotiation.

- @Mikey129