4 ms·
I'm in a similar boat and I'd like to also know if anyone has any resources for setting up a good pricing model for the initial implementation vs potential futu
by zSplash 4y ago
I'm in a similar boat and I'd like to also know if anyone has any resources for setting up a good pricing model for the initial implementation vs potential future updates. If they just want a one off project I'd probably just hardcode most data. If they asked for a CMS or I thought it fit their need then I'd recommend setting it up and probably charge more for that initial implementation. However, when it comes to actual code maintenance/updates does anyone have any experience with varying levels of pricing for this? Do you just charge the same hourly rate you would've charged before?
- c0re0xA0 4y agoThat really depends on what I have to do. If I’m using a Web UI to update a plug-in I charge less. When I have to use a terminal or an IDE I charge the normal development rate. When doing content updates (yes some clients want a CMS but still don’t do content alone) I charge the least.