6 ms·
Entertaining story - although as advice to anyone reading it, running up the clock without proactively notifying people that you're going way beyond your origin
by ryanbrunner 7y ago
Entertaining story - although as advice to anyone reading it, running up the clock without proactively notifying people that you're going way beyond your original estimate is a very good way to make getting paid incredibly difficult.
- _bxg1 7y agoIt was my impression that that's what he did. Of course the whole situation still could've made it difficult to get paid, but I don't think there's anything else he could've done.
- Semiapies 7y agoSpecifically telling them that they had kept him over his initial estimate (and so his estimate was increasing) when he neared or passed that point. He didn't sound terribly proactive about bringing this up while talking to people, either. Lunches with the manager where they didn't talk any business, etc.
- megaremote 7y agoNo, he clearly didn't. He only worked out the costs at the end.
- im_new_here 7y agoI don't disagree, but it's worth noting that at the end of it all, he billed them for $18k and they decided it was too little.
- Aeolun 7y agoI mean, if I’m not paying with my money. And I know the guy has just been there waiting for stuff to happen for weeks, I’d happily do the same thing.
- tomcam 7y agoAccording to the article he emailed them daily.
- spiderfarmer 7y agoYeah but not to let them know his estimate was off.
- ceejayoz 7y agoYeah. Maybe it's just an omission in the story, but once the original scope was exceeded, an "I wanted to let you know that we've reached the number of hours I estimated for the task; let me know if I should continue on this project on an hourly/daily basis of $x" email was probably warranted.
- makapuf 7y agoWhat if you don't get any answer ? Shall you go on ? Leave unexpectedly? Apparently his staying on the job for his hourly rate wasn't an issue and was even expected.
- ceejayoz 7y agoIt won't always work out like it did for OP, so it really depends on how much risk you're willing to take. $18k probably isn't enough to be worth a lengthy lawsuit over, so a more aggressive client might've cost OP significant unpaid time. For some, that's an acceptable risk. For others, not.
- chc 7y agoIt sounds like he gave them an hourly rate, not a project rate, and emailed every day to let them know how many hours he'd worked and what he still needed, both before and after the estimated time frame was blown. It doesn't sound like he did anything irresponsible.
- jkingsbery 7y agoAlternatively (or in addition): sending invoices periodically.
- vidarh 7y agoI thought no that's the reason why right answer. He could be as much in the right as possible, and but he still took significant risk that they might argue, delay and force him to go to court or negotiate to get them to pay. Sometimes it might be worth it - maybe the plug would have been pulled sooner if he had invoiced regularly. But it's still a risk.
- deleted 7y ago[deleted]
- atoav 7y agoPrecisely the oposite. People are usually willing to pay far more, if they are to blame for you beeing slow. If they only get the slightest hint of a feeling that you might be kicking the can down the road, they will blame it on you entirely. This is, why you leave a paper/email trail.
- awb 7y agoJust to clarify, he got paid $21k for 7 weeks of time. He just so happened to only deliver a static HTML page, but was on prem as requested during the engagement. Still, it's a quick way to get a reputation for running up the clock.
- collinmanderson 7y agoIn fact, it's actually only about $50/hr.