Hacker News new | ask | show | jobs
by zenocon 4996 days ago
You make some valid points. I am undercharging. Most projects I go into, I end up doing the work of 5-10x of their engineers. I know this. I've known it for a long time.

It is the reason I went into consulting in the first place -- that and the fact that I don't want to deal with the politics and bullshit that goes with the standard corporate environment. I build stuff and get out.

That said, I think we're still talking about the single revelation of just "raising your rate". I'm not sure I need a book to do that, and you haven't sold me on the examples, anecdotes, worksheets, and other practical advice. I think it really, singly comes down to just raising your rate -- am I wrong?

Quite frankly, the reason I haven't raised my rate is that I live a comfortable lifestyle. I can afford the things I need and the things I desire. I have a family - I provide well, and we are far ahead of the curve on retirement. I plan to retire early, and I'm on track for that. I also live in a geographic environment that has been hit significantly hard economically. Doubling my rate would be a hard pill to swallow for local clients -- albeit most of my clients have been on the coasts.

The question I raised, and still do raise, is this: is it really an ebook that made you that extra income, or is it just having the balls to raise your rate? I'm arguing it is the latter, and questioning the value in an ebook whose main point is summarized in the title...

3 comments

I think it really, singly comes down to just raising your rate -- am I wrong?

For me, it was two things:

1. Realizing that I should (and can) raise my rates in a simple type-in-a-higher-number sense. Yes, I knew this in a vague sense, but the book really drove it home for me.

2. The other rate increase that I plan to work on over the next 6-12 months is a transition from "freelance programmer" to "engineering consultant who delivers business results". Like you said in your example, if you're doing the work of 5-10 engineers, I think there's real value in being able to demonstrate this in a quantitative way and charge accordingly. And the book definitely helped in that regard as well.

Again, for me it was worth it to pay the money just to read some examples, hear about some rates that others were charging, and dedicate some time to thinking about this. $25 just isn't that much money to me in the scope of being able to improve my business. Maybe I could have done it without the book, but I figured it was worth risking $25 to find out if I could do it better with the book.

Quite frankly, the reason I haven't raised my rate is that I live a comfortable lifestyle.

Earlier you say,

I do feel like it is time to raise my rate, though, and the next project I start I will.

Could Brennan's $49 ebook resolve the tension between raising and not raising your rate?

Could some other $49 ebook have done it?

What is resolving this indecision worth to you?

Or is it, as you put it, "just having the balls" deciding either way?

Why not charge the higher rate, but give a discount to local clients, and invoice as such?