Posted by : Tom Doyle in (Rantings, Web Design, Web Development) 17th Sep, 2007

Web Design - Why we don’t provide concepts with proposals

Lately, we’ve seen a significant increase in the number of RFP’s requesting a “few” concepts to be included with the proposal for the web design job. I know some companies have no problem doing this, but for us, we just won’t do it. There are a number of reasons for this.

1. It takes time and costs money
Probably the most obvious reason for not providing concept designs with proposals. With a small company, generally everyone is busy, it’s not in our best interest to take a designer off a paying job to create a design in the hope that you might win a new contract. How many builders would you expdect to build an extension to your house before they’ve got the job and run the risk of not being paid a cent? So why should we?

2. Design is subjective
In a lot of cases, it’s the design that makes or breaks a job. If you’re lucky enough to get a client that simply loves your work and will take anything you put before them, regardless of taste, you are on the pig back. However, this is rarely the case. Design is so subjective, what we think is modern and funky is someone else’s dull and lifeless.
For this reason, I think it’s a really bad idea to submit a design with a proposal, without going through a proper design brief.

3. Devaluing our work
If you do the design work for free….. what else do they expect for nothing????

So all in all, it’s up to us in the industry to cut this culture out.

Share and Enjoy:
  • Digg
  • StumbleUpon
  • del.icio.us
  • Sphinn
  • Spurl
  • Technorati
  • Furl
  • Facebook
  • Mixx
  • Google
  • description
  • Fleck
  • LinkedIn
  • Slashdot
  • TailRank
  • TwitThis
  • NewsVine


Comments:

Make a comment