3 ms·
Bill by the project. You can use your hourly rate to estimate the fixed cost. The more projects you do, the more accurate your estimate will become. Over time y
by cgs 17y ago
Bill by the project. You can use your hourly rate to estimate the fixed cost. The more projects you do, the more accurate your estimate will become. Over time you develop your own time-saving methods, such as pulling code out into reusable libraries you can use on your next project. Say you do a project that takes you 50 hours and you charge $5,000. If you get another similar project but this time you know it will only take 25 hours, are you going to charge $2,500 for it? Hell no! Charge as much as the market will bear, but set some kind of a minimum threshold for yourself. Here's an old article relating to technical writing, but I think it still applies to software development: http://www.writerswrite.com/journal/jan98/kent.htm http://www.writerswrite.com/journal/jan98/kent.htm
- jamesbritt 17y ago"You can use your hourly rate to estimate the fixed cost" Only if you know how long it will take. Which assumes you know what you are going to build, which assumes the client really knows what they want. If you are doing a more agile project, you expect new requirements to come up, current requirements to drop out, things to change along the way. But you almost certainly have no solid idea how long it might take. A mixed approach might be to make a big project into a series of smaller projects (e.g., well-defined and doable in 1-2 weeks), and bill each at a fixed price.