[ryanwaggoner]

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.