Ask HN: Does anyone else hate consulting on a per hour basis?
I'm disgusted with the whole thing. Hourly billing is hard enough because even when I'm asked to complete tasks outside of my realm of expertise, I have trouble billing for my learning curve. On top of that, I'm working on an under-producing e-commerce site and I see the figures, I'm sure money is tight for my client. However, I find myself disgusted, because I'm working less, doing less-than my all, because my client isn't willing to pay for the time. To add insult to injury, the client is non-technical, so he doesn't see the value in anything but more sales.
Have other people run into this problem? Is this how most hourly consulting gigs go, or is it just my client? Did you switch to project related fees? Drop consulting for a salary job? Any advice would help.
You are actually defending his side of the story.
...On top of that, I'm working on an under-producing e-commerce site and I see the figures, I'm sure money is tight for my client....
You drank the Kool-aid.
Go back and negotiate on a per day basis. Do not let any insecurity about your work creep in. If the client barks (he will), then tough luck. Keep your ground and dont move.
He will either fire you or find somebody else. A tech-clueless business person will think twice before hiring someone else if the project is more than half way done.
Also, the client is technical. The person is building an e-commerce site!
Knows that internet + website + products = money.
You are the key to his/her plans. He/she may not know how to code, but does understand how things work.
He/she is just playing dumb to get you to lower the prices. Its working.
You need to develop your hustle, or else your startup wont make it.
Remember: They have your money on their pockets. It your job to get it. Dont break any laws, dont be immoral/unethical. But get that money.
Good luck.
I guess you are either doing the hustling or getting hustled. And I know which one I'd rather be.
rm at innovafy dot com
I'll gladly help you out.
The projects which can be problematic are those which create death by 1000 cuts...an hour here and an hour their when no progress is made.
The most important thing is to select clients who are educated in regards to the costs going in. I will give them a fairly realistic estimate of my hours based on their description of the scope. The key is to educate the client when working hourly.
That's not to say I don't take work at fixed fee, but the project and client have to be right.
1. I prefer easing clients mind by letting them know how much they will be paying 2. I'm confident in estimating 3. I draw the line in the sand by making it clear that working outside of the contract is non-negotiable unless we mutually agree to revise/update it and the cost
Two exceptions. 1. They do not have a clear spec (or no spec). It will be hourly until that is defined. 2. Maintenance mode
It's hard, and I am bad at it, but I think doing this is key to "growing up" and being a successful freelancer.
The only caveat is that you need to be explicit when you define the project. This is hard for a lot of developers, which is why they prefer hourly billing.
Every once in a while, you get really lucky, and something that you estimated 8 hours for takes 2, in which case you can split the difference with the client and:
1. Look like a hero.
2. Make a bit of extra change.