• 0

How much to charge?


Question

I've been asked by a friend to build his company a website. All he wants is Ajax(tabbed navigation) to display the product features and tweets which I'm going to use jQuery to do. I'm also designing the site for him.

Roughly how much should I charge? I've never done freelancing before. So any rough estimate? I'm confused.

Thanks sooooo much :p

Link to comment
Share on other sites

10 answers to this question

Recommended Posts

  • 0

I would say it depends on the size of the company - bigger company would definitely be willing to pay more... All of the web developers I know work full time for a company...

If all else fails, just tell them you'll work on a salary (you can look up an average web developers yearly salary somewhere) and work by that - the longer it takes the more you get paid; but of course you'll tell them the quicker you get it done the cheaper it'll be for them hehe...

If they prefer on a hard set amount for the entire site, do the same thing as above (find the average salary) and set a time frame for yourself. Go by that :)

Link to comment
Share on other sites

  • 0

Make an estimate of how many hours it will take you to complete and support. Then decide on your going rate per hour - this should depend on your expertise and experience. Quoted amount = hours x hourly rate.

If you are expected to meet a really tight deadline, multiply the amount by 1.2 to 1.5.

If you are expected to support and maintain the site, make allowance for that in your quote.

Most importantly, be very clear what your responsibilities are (and set them in writing) before you make your quote.

Link to comment
Share on other sites

  • 0

When I'm on a project I typically charge anywhere from $25-50 an hour depending on the work required. I don't give the estimate as an hourly payment. I will just estimate how many hours are necessary and give them the actual price. When a client sees an hourly estimate they think that you'll paddle your feet along the ground to take as long as possible.

I would also put together a very firm contract outlining what you'll be doing and what your price includes. That way he doesn't keep tacking on extra "fix this, do that" without you being paid.. and to ensure that you get paid.

Tread carefully working with a 'friend' though.. They might expect you to go as cheap as possible.

Hard to reply to a member who is banned.

It's called a personal title.

  • Like 3
Link to comment
Share on other sites

  • 0

When I'm on a project I typically charge anywhere from $25-50 an hour depending on the work required. I don't give the estimate as an hourly payment. I will just estimate how many hours are necessary and give them the actual price. When a client sees an hourly estimate they think that you'll paddle your feet along the ground to take as long as possible.

I would also put together a very firm contract outlining what you'll be doing and what your price includes. That way he doesn't keep tacking on extra "fix this, do that" without you being paid.. and to ensure that you get paid.

Tread carefully working with a 'friend' though.. They might expect you to go as cheap as possible.

+1 Exactly this. Also, a general rule with freelancing, ask for a 50% deposit before you even start anything. That will guarantee that you get payed something, even if he stuffs you around much like the "fix this, do that" bit Cupcakes mentioned.

Link to comment
Share on other sites

  • 0

even if he stuffs you around much like the "fix this, do that" bit Cupcakes mentioned.

just HATE those questions.. realmad.gif

Certainly follow his advice and ask money.. enough money shifty.gif

Link to comment
Share on other sites

  • 0

There are lots of things you can do to control client expectations.

Meet with them and iron out every detail. Don't make any assumptions. If they want a shopping cart, for example, ask whether that means they also want the facility to send newsletters, blog about new products, etc. You may both be surprised to learn what the other expected is or is not included.

Make a functional requirement document detailing exactly what the system will do and how it will do it. Note in your contract that these specifically are your obligations. Also have specific time allowances in the contract for changes and support. Don't leave anything open-ended.

Show the client your progress every so often. Don't keep them in the dark just because it's fun to imagine how blown away they could be by your final product. Instead, as you go along make sure that what you are creating is what they actually want.

Be confident and know how to sell your decisions. If you can explain to the client why exactly what you did is better for them than the change they are asking for, most of the time they will gladly come aboard.

Don't be afraid to discount nitpicking outside of the project focus. Sometimes when I am asked for aesthetic changes on a web application or functional changes on a design, I point out that really, those elements were always secondary and if the client wants them fancier, I can quote that separately.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.