BrainDump
  Home arrow BrainDump arrow Page 2 - Making the Most of Your Design Busines...
Dev Shed Forums 
Administration  
AJAX  
Apache  
BrainDump  
DHTML  
Flash  
Java  
JavaScript  
Multimedia  
MySQL  
Oracle  
Perl  
PHP  
Practices  
Python  
Reviews  
Security  
Style-Sheets  
Web Services  
XML  
Zend  
Zope  
Forums Sitemap 
IBM® developerWorks 
Sun Developer Network 
Dedicated Servers 
E-Commerce Hosting 
Linux Web Hosting 
Managed Hosting 
Small Business Hosting 
Actuate Whitepapers 
VeriSign Whitepapers 
VPS Hosting 
Weekly Newsletter

 
Developer Updates  
Free Website Content 
IBM developerWorks
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
BRAINDUMP

Making the Most of Your Design Business
By: Thomas Granger
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 4 stars4 stars4 stars4 stars4 stars / 9
    2001-05-04

    Table of Contents:
  • Making the Most of Your Design Business
  • Separating from the amateurs

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT

    Stay one step ahead of the competition. Evaluate and give feedback on some of the hottest web development tools on the market today. Make your opinion heard! Click Here

    Making the Most of Your Design Business - Separating from the amateurs


    (Page 2 of 2 )

    This list of steps will separate your design business from the amateurs:

    1) Spend time interviewing the client about the job. Not only will this help you determine first hand what the client's needs are, but also it will help the client view you as a professional. A good first impression will help you later on when it comes time for payment.

    2) Put together a work order based on what was discussed in the interview. This will be your proposal to the client to begin working on their project. You will need to spell out all of the terms, delivery dates, number of pages, editing guidelines, deposits and payment terms. You also need to include all of the options discussed in your interview with the client. A formal proposal says that you are a professional.

    Your proposal should contain no less than the following:

    • Cover letter
    • Site Specifications and layout
    • Development Guidelines
      (include milestones and number of drafts)
    • Payment terms and conditions
    • Storyboards, diagrams, or examples
    • The contract

    In considering each of these elements I cannot stress enough the following point: Leave nothing open-ended! Even if "open-ended" is a vital part of the contract, as in the case of an ongoing relationship for maintenance and updates, you need to spell it out!

    3) Never work without a deposit. Go look at the Golden Rule again in case you forgot. A deposit does two things for you.

    • It helps separate the serious clients from those who are not. A client is less likely to pull out of a project if they've made a financial commitment.
    • See the Golden Rule.

    4) Have a pricing strategy. Know what your time is worth, how long it takes you to do certain tasks, and the value of those tasks in the marketplace. Communicate them effectively to the client, impress on them which tasks are time consuming, and how this will impact pricing. Your client is likely to be a professional, and they will understand that time is money. They understand that their own time is money. They should understand the Golden Rule and so should you.

    Developing a spreadsheet or other form which allows you to track changes to a project as you go helps in the long run. It will not matter whether you charge per page, per project, or a combination of both, because you will know how to price what you are doing for the client.

    5) Test early and often - don't let your credibility erode by forgetting little Q/A issues such as Browser Compatibility (read: Netscape), plug-in issues, load times, and screen resolution. Do as much of this before the client sees it. If the first impression of your creation is a good one, then it will be easier to get paid than if the client could not view the site correctly the first time around.

    6) Have a final invoice - make sure it reflects the work order to the letter. Any agreed upon changes must be billed with the approval method clearly outlined. Attach any copies of emails, faxes, or other communications regarding changes to your site. Your contract should outline the terms of payment, and definitely detail a "late payment" policy. Just slap a statement on your invoice which reads "18% APR for accounts more than 15 days past due" and see what happens. You should always have a plan to enforce non-payments

    Whether you are a freelance web designer, graphic artist, desktop publisher, or programmer you take on a great deal of responsibility every time you accept a new contract. Having ironclad contracts, invoices, and work orders can go along way in protecting your interests early and often, before trouble starts.

    Putting these steps in place takes time and a little money, but you don't need to hire an attorney, an accountant or a business manager to increase your sales and efficiency. Just remember the Golden Rule. Your time is valuable; don't let the client take that from you.

    A good resource for many of the things I've mentioned above is a company called Proposal Kit; you can find the product here. I purchased their "Professional" package for our business and we've been extremely pleased with the results.


    DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware.

     

       

    BRAINDUMP ARTICLES

    - More Amazing Things to Do With Pipelines
    - Pipelines Can Do Amazing Things
    - Better Command Execution with bash
    - Executing Commands with bash
    - Outsourcing: the Hoopla, the Reality
    - MySQL Plays in the Sun
    - All About SQL Functions
    - SQL: Functioning in the Real World
    - More Advanced SQL Statements
    - Beginning SQL the SEQUEL: Working with Advan...
    - Beginning SQL
    - A Look at the VI Editor
    - A Quick Tour of Boo
    - Book Review: Open Source Licensing
    - PGP and GPG: Email for the Practical Parano...





    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 2 hosted by Hostway