On Feb 1, 11:16 am, John [email protected] wrote:
While this is a valid method for most people, I found it to be a great
way to limit the amount you can earn - in this case to $93K.
That depends on how successful you are at getting work and retaining it.
For example if you were able to work an average 40 hour week for 48
weeks, you’d earn a tad over $178K.
If you are going to ask for an hourly rate make sure you ask enough,
otherwise you will be a slave for hire. Keep in mind, there is a
judgment of your abilities according to the rate you charge - the more
you charge the more experienced and professional you are. Low rates
attract people who want work done cheaply, but not professionally.
Definitely. Unless you are desperate for work, it’s not a good idea to
undercut yourself. There are plenty of others out there who will do that
The caveat here is that when someone is starting out they may need to
prime the pump a little with a slightly lower rate to build up a
Another way is to try and gauge how much the work is worth to the
client and charge them accordingly. Sure this is sometimes a harder
sell, but every client has an idea of how much they want to spend on
this problem - the time taken to accept delivery is an evil they would
If a job is worth $2,000 to the client then charge them that. If you
have the good fortune of getting it done in 2 days, then best of luck
That’s good advice. As you indicated, it’s not always easy to get this
info. They may be trying to save money, and not be as forthcoming with
all their expectations.
What’s more, if you develop libraries as you go you will be
better setup for the next project (and a Saint if you release them as
a plugin or gem). Sell them on how quickly you can develop a
solution, how well it will be tested and how easily changes can be
made. Be agile and responsive - your client will love you and keep
True as well, but if there is a contract check the fine print for
ownership of the source. If the client wants to own the resulting
sourcecode, it can be a major legal hassle not just for the developer
but all of his clients who have software that uses the code. That’s a
sure way to trash your reputation.
Someone just starting out will need to test the waters while they are
doing so. The divide by 1000 method gives a decent method of estimating
what they should be ‘worth’ to a client until they have the skills to
estimate what a job is really worth.