Re:The shittiest project I ever worked on (2013)
by dvh on Friday May 24, 2019 @02:41AM
(#19999055)
If he was paid by the hour it would be typical, perfectly reasonable contractor project.
[ Parent
| on HN ]
Re:The shittiest project I ever worked on (2013)
by erdo on Friday May 24, 2019 @06:41AM
(#20000173)
Or if you really want to play the fixed price game, better add a _large_ buffer which you may keep should the project miraculously complete on time. You transfer the risk from the client by doing fixed price work and risk is expensive.
And of course, _every_ client change, goes through a process that evaluates it for additional cost that gets added to the bill. I think this change process is a considerable money earner for consultancies.
But yeah, personally I always just charge a day rate.
Re:The shittiest project I ever worked on (2013)
by twervle on Friday May 24, 2019 @03:02AM
(#19999138)
Consulting companies know this and they NEVER charge fixed price.
Re:The shittiest project I ever worked on (2013)
by thirdsun on Monday May 27, 2019 @07:37AM
(#20021286)
However there's a case for fixed pricing and it can work to your advantage: Think of a difficult task or problem that you already solved in similar cases - maybe you already have the heavy foundation of that work ready as a template, maybe you automated complex, repeating steps. Or just think of a simple task that has huge value for your customer. Pricing shouldn't always depend on how long it takes you to finish a project.
Re:The shittiest project I ever worked on (2013)
by sdoering on Friday May 24, 2019 @09:38AM
(#20001287)
I beg to differ. Working at an consultancy and we had fixed price projects for large clients. We just had to plan a risk buffer into the price.
But I can also tell from experience that fixed price, more often than not, doesn't work out so well.