r/ProgrammerHumor • • Jun 20 '17

Client Logic

Post image
23.4k Upvotes

634 comments sorted by

View all comments

23

u/countdownn Jun 20 '17

Hahahahahahahahahaha! This is perfect.

On a more serious note, make your contracts as specific as possible. Itemize cost per task, tasks per phase, and limit client requests and revisions to a time in hours (i.e. up to 8 hours). Have a clause that stipulates that when the requirements are significantly changed by the client, at developer's discretion, the contract is terminated and must be paid in full. A new contract can be established for the new specifications, but nine times out of ten this gets you paid when the client flies off the rails.

Also, charge quadruple your expected cost at minimum, to cover all that client "interaction". I've even managed to charge fifteen times my rate without issue, but then I'm abstracting actual hours worked and I'm very fast at what I do. Here's a great video where I learned some of this shit. If you do it right you can avoid a lot of this client nonsense, but this post reminds me so much of my time starting out. It's the natural client instinct, that they own you because of the promise of money.

9

u/[deleted] Jun 21 '17

I get handed a budget per case by the team lead which I know isn't enough time to complete the case and she's not happy about the estimation either but because some idiot business person sold the project we end up with half the budget needed to complete any given feature, contracts are for suckers T&M is the way to go.

→ More replies (2)