Hey guys I recently am in contact with a person who wanted me to make a recruitment solutions website, like a job finder site, and he wanted me to make a proposal stating how long it would take to finish and of course how much.
so thats my question, how long should it take me to finish it in a proffessionals view?
because i might propose a very long timeline and i might not get the job.
also how much should i ask?
here is a sample of what i should make http://www.jobsdb.com
Question to people who has expreience with job contracts
Moderator: General Moderators
I recommend you break down the whole project step by step.
Figure out how long it'll take you to complete what you need to do and give yourself plenty of time to complete each section.
Then from here you can calculate a total project fee based on an hourly rate if you wish, and also give the client a good deadline for completion.
I also recommend checking out the articles in this Freelancer Resource sticky thread:
viewtopic.php?t=19980
Figure out how long it'll take you to complete what you need to do and give yourself plenty of time to complete each section.
Then from here you can calculate a total project fee based on an hourly rate if you wish, and also give the client a good deadline for completion.
I also recommend checking out the articles in this Freelancer Resource sticky thread:
viewtopic.php?t=19980
I've always found a contract fee most appealing, as opposed to an hourly rate. In my contracts, I state exactly what I promise to deliver, and what I expect to be paid. If it's a really big project, it's probably best to outline a pay schedule too.
A big problem would be feature-creep. An hourly rate usually tames that a bit, and clearly stating the features should also tame it down.
The reason I like stating the total project amount, is because sometimes clients are leary when you don't tell them exactly how much the project will cost. In their minds, it's easier for you to rip them off if you can keep racking up the costs.
This is, of course, my opinion. I'm sure some people have counter-points.
A big problem would be feature-creep. An hourly rate usually tames that a bit, and clearly stating the features should also tame it down.
The reason I like stating the total project amount, is because sometimes clients are leary when you don't tell them exactly how much the project will cost. In their minds, it's easier for you to rip them off if you can keep racking up the costs.
This is, of course, my opinion. I'm sure some people have counter-points.
Real programmers don't comment their code. If it was hard to write, it should be hard to understand.
Another piece of advice is once you determine the price and time to build throw in completion milestones. This will keep you on track and give the client something to measure you by to show you are progressing. Also, make sure you have all the requirements in writing and anything outside of said requirements would be an additional cost at a set hourly price.