Beta

×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Comments

top

Freelance Web Developer Best Practices?

klassicd bill hourly (438 comments)

Per-project pricing can be very difficult. Clients always request new improvements or changes once they see your work. If you're stuck with per-project pricing you will end up battling the client over important changes they request. Bill by the hour and always create a statement of work. Your statement does not have to be very detailed. It should be a high level overview of your development goals. It should include time estimates for each phase of the project. If you are going to be investing over 40 hours of work into a project it's a good idea to request a retainer. The client should be willing to put 10% to 25% down. New clients may be weary of putting down a deposit. In this situation it's a good idea to break down the project into smaller phases. After each phase they should be required to pay you whatever hours you have logged. Always keep detailed track of your time. It's important that your quotes are very close to the time billed. This will be trust with clients. Time everything you do and always compare it to your original quote.

more than 5 years ago

Submissions

klassicd hasn't submitted any stories.

Journals

klassicd has no journal entries.

Slashdot Login

Need an Account?

Forgot your password?
or Connect with...

Don't worry, we never post anything without your permission.

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>