Hacker News new | ask | show | jobs
by emp_ 2820 days ago
Amazing how I wrote this post without typing anything in it, I bill by estimate so if something is estimated 40 hours and I do it in 2, I can get more work or just chill, I usually book my time around 200 "hours" a week and some good weeks I work 18 real hours and the bad ones around 70, pays extremely well but has very little margin for error so the bad weeks have to be rare. I had 18 straight months of good weeks and now I'm in a 6 week streak of bad ones, great/awful clients make or break this system.
1 comments

How do you handle deployments on those "40" hour projects? I understand that you provide that much value, but it the client thinks they are paying for hours, even if not directly, seeing a contractor push code in 2 hours and then bill me for 40 has to hurt a bit.

Obviously if your estimate is devoid of any hourly numbers, this conversation is moot.

Those are closed price projects, they do use hours for reports and all but its really a fixed payout for a fixed amount of features.