A quote is a quote precisly becasue that is what your bill will be, changing a quoted price simply shouldn't happen unless the scope changesminiConvert said:You need to charge in relation to the amount of time and effort you think it'll take, and add on any extra charges you're likely to encounter. Figure out how many hours you think it'll take, how much you think you deserve an hour, and do it that way. You can always inform the customer that your final bill will be +/- 10% of your quote depending on how it goes.
Just don't be greedy
That's good advice, I'm fairly new to the business and I want to build my portfolio, but I don't want to work for free per se.theappleguy said:It really depends on how much work it is going to be and how skilled you need to be to do it. Determine how many hours you think it will take and then determine a reasonable rate per hour. eg. 100 hours x $20/hour = $2000 for the site. If it is the first time you are designing a site for someone else, then it is probably best to under sell yourself until you have built up a portfolio.
hulugu said:That's good advice, I'm fairly new to the business and I want to build my portfolio, but I don't want to work for free per se.
How long does it typically take to build a website? Do you have a general average?
ThunderLounge said:If you're having to ask these questions, then your end result is going to be a rather low price.
I could be very wrong, but here is what my assumptions are based on what you have written so far. This isn't personal, as everyone has to start somewhere. But at the same time, you'll need to understand that your end result will be very different than that of someone with much greater experience.
1) You'll be using software to generate the pages.
2) Pages may not be standards compliant, or cross-browser compliant.
3) You may have "tinkered" around with a few basic pages, but actual design (both visual and underlying code) experience is extremely limited.
To be honest, from your shoes I wouldn't punch much over $50 a page, maybe a little less. Regardless of time consumed. Most likely you'll be learning as you go, and a client shouldn't be charged for your learning curve.
Reasons for this would be mainly a lack of experience, and therefore the end resulting product will not be as well crafted as from a professional designer.
Again, it's not personal. Everyone has to start somewhere, and at one time was sitting with a page full of code going... OK, WTF now? Even Zeldman and Meyer had to start somewhere. We all did.
IMHO, the best thing you could do with this situation, is simply learn from it. Don't be greedy, and definitely undersell in comparison to anyone else out there. If the site is 10 pages or less, I personally wouldn't recommend anything over $500.
This way the client isn't paying an outrageos price for a site by someone without much experience, if they find in the long run they need a professional solution they aren't out much from the experience, and at the same time you get the benefit of something for the new portfolio and some on the job training as well.
This way, everybody wins.
As you build your portfolio, you can slowly start to charge a little more. Also, never stop learning. There's always something new to learn out there. Make it a daily or weekly ritual to spend at least an hour learning something.
First, is obviously HTML and CSS. Next would be (x)HTML, Php, and MySQL.
Personally, I'd shy away from ASP and .NET, mainly because it's M$ crap, and not every server out there can run it. Php/MySQL can work on *nix, and win platforms, and the client won't need to pay for anything extra to run the site (like MSSQL, etc).
Learn the right way the first time, and get very comfy with web standards. The W3C is your friend.
Final shot, remember:
Tables are for tabular data, not layouts!
hulugu said:I've designed pages before, but I don't want to charge based on how long it will take me, but rather a reasonable average. Essentially, I want to undersell as much as possible, but I don't want it to be free (especially because once you do something for free, it becomes harder to charge later.)
I'm reading the O'Reilly books, and don't worry I'll be testing the site against W3C standards and several browsers to make sure it's lean, done right, and hopefully easy to update and extend later.
I just don't know what is a reasonable amount of time. I'm considering a low-hourly rate at $15 per hour at 40 hours for 9+/- pages or $600.