5 ms·

If you're consulting I would suggest not billing by time but by value provided. I'm not a developer so I don't know how impossible that is to convince clients b

• adrianmsmith 5y ago
  > If you're consulting I would suggest not billing by time but by value provided. If you're doing that then accurate estimates become even more important. If you are billing by time and things take longer than you expect then after a while your customer is going to get angry and that's going to have consequences. But if you are billing by value then if things your employees are working on take longer, you're eventually going to make a loss on the project as a company. So you need to price the value right, and that involves knowing how long things will take in advance.
• nobody9999 5y ago
  >If you're consulting I would suggest not billing by time but by value provided. I'm not a developer so I don't know how impossible that is to convince clients but this is something I do as a marketing consultant and it works extremely well. That's certainly possible, and many contracts are done on that basis. Others are done on a time and materials basis. Generally (as I'm sure you're aware), that's negotiated by the parties involved. I'd posit that while it may be a good idea to perform some services at a flat rate, it's not always the right call and is highly dependent on the work being performed. Edit: Fixed awkward usage.
• datavirtue 5y ago
  You hit the nail on the head. Developers are underpaid.