Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

One thing that surprised me was milestone billing with approvals, but moving on to the next milestone without getting approval on previous ones.

I agree with you, this project structure sounds… much worse than T&M billing, but if I were going to take on a contract in this structure I would have a simple rule of “I won’t work on the next milestone, without getting approval on the prior one” (for something like this, where the milestones are pretty small, maybe I’d be willing to work one milestone ahead).

But I’d absolutely use the schedule pressure as a tool to get them to care about approvals. Because, from the described contract structure, what incentive does the client have to give timely approvals or rejections? None!



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: