Welcome to WebmasterWorld Guest from 220.127.116.11
Do you bill hourly?
What do you charge per hour.
Do you bill per line of code?
What do you charge per line?
If you bill per line do you include a comment as a line?
I am curious because I bill per hour but there are times when this method seems deficient. I can do x amount in one hour vs you can do x more/less in the same hour.
As an example I recently picked up some code work and am having trouble figuring out how long it will take. The code I am working with is pretty poorly written and once I start working on it I have no idea of what issues I will run into.
The initial communication with the client started off as me just installing a script on his website that another company coded. Normally with a well written script this is a fairly strait forward process but this took about 4 hours to track down all of the missing extensions and fix the path issues (had to install pear on his server and Smarty). The previous devs left behind a mess when they turned the code over to the client all of the paths had been based off their dev servers paths with no less than 5 different config and ini files strewn all over the place.
Once I got the site viewable There are additional issues regarding the admin login and some other client side login and just a multitude of other issues that need to be dealt with.
So at this point do I highball an already taken advantage of person then if I come under budget refund a portion with the fear he will think I am trying to rip him off too or can I just say I don't know what it will take and bill on a per changed/new line basis. I don't like the idea of an open ended hourly development cycle
Thanks for your thoughts.
So Do you have tips on properly bidding for a project? I am not asking for trade secrets but some ideas.
I guess I look at something with the regards of how long I think it will take me to complete the requested tasks. But when you have no real idea, what do you fallback to? In that situation what formula do you use? If anything other than experience and screwing yourself in the past to come up with a price that is fair to both you and the client.
I have been taking on more risky projects recently with the hopes of additional income stuff I would have backed away from a year ago so I find myself in uncharted territory.
Thanks for the reply
I can do x amount in one hour vs you can do x more/less in the same hour.
...am having trouble figuring out how long it will take. The code I am working with is pretty poorly written and once I start working on it I have no idea of what issues I will run into.
I see this as another argument in favor of billing by the hour, since it is your experience and judgment they are paying for, especially if the full scope of the work can't be anticipated in advance.
There are diplomatic ways to tell the client that the existing code is likely to present unforeseen difficulties, without unnecessarily bashing the previous programmer.
If a client is overly paranoid about hourly billing, that to me is a warning flag about them, since it reflects something about their world view, or about the environment they are used to existing within, and thus possibly about their potential behavior.
An hourly rate is easy to justify if you can deliver preliminary work product after a short time, which they can evaluate and decide if they want to keep you working on the project.
Those are just my opinions, and not particularly strongly held ones. I'm interested in seeing the other advice you receive.
Diplomacy goes a long way ... keep your mouth shut instead of bashing previous work. We don't always know the situation or boundaries under which the previous programmer(s) worked. Or if they were related/family! You never know if the owner's kid had his hands in there at some point and just didn't change any "author" information in the code comments. You bash away openly to your client and the next thing you know you are eating crow. Take the high road and keep your frustration and comments to yourself, your client doesn't want to hear them anyway as he has to tend to problems of his own. That's why you are being hired in the first place.
If the project is difficult to break down, then offer a price range and perhaps even a phase approach. Break down the work into milestones that you can indeed project more precisely. For those areas of uncertainty, add an unforeseen contingency percentage.
I guess it comes down to the fact I still have more to learn and since I am taking on riskier jobs means I will learn more, faster (crosses fingers).
Everyone's input has been valuable to me and I do appreciate the time and well thought out answers.