Finding the right web design agency is tough -- very tough. It's never an "apples to apples" comparison. I'm not even sure if it's an "apples to oranges" one, either. Agencies range in price, methodology, creative capability, core competencies, pricing models, technology, and a multitude of other factors that might or might not be relevant. Some factors are obviously more important than others, and firms use a variety of approaches in an attempt to help them narrow the field to ultimately pick the right agency. However, there are a few mistakes that people seem to make time and time again. Below, we explore three of the most common and egregious errors.
Asking for spec work
Spec work might have been the norm in the old days, but there is nothing more insulting and less relevant than being asked for spec work today. Beyond the fact that you're being asked to do unpaid work, the idea that it helps a firm to choose an agency couldn't be further from the truth.
Good design is a product of talented, motivated, and dedicated creative professionals going through a lengthy and established process. Skipping this process means that the spec designs will not be correlated to the creative capability of the agency.
Would you really want to hire an agency that didn't develop a creative brief, establish user personas, develop a strategic site architecture, develop wireframes, create a copy platform, etc., before beginning the design process? Skipping this would be akin to skipping the plans when building a house and just hiring someone to lay bricks and hammer nails without a plan. That's not exactly the best way to build a home, and it's definitely not the best idea when crafting the most visible piece of your brand.
Just remember, don't ask for spec work -- ever. It's insulting to the agency and isn't a good indicator of the creative capability of the agency or the design you'll ultimately launch.
Not understanding the difference between estimates and project fees
Agencies typically provide project estimates or project fees when delivering a proposal. While there is nothing really wrong with either approach, failing to understand the difference can be a costly oversight. Most good firms are very transparent about their fee structure and attempt in good faith to make sure that project estimates are in line with the actual expected costs.
Other agencies don't give estimates, but rather fixed project fees. We happen to be in this group as well and put the burden of estimating the deliverables for a project on us. With the project fee agencies, you have a set fee based on deliverables, not hours.
Knowing which fee structure each agency uses is crucial to making the right choice. Both have their benefits, but unfortunately many clients have found themselves handing over much more than intended due to an optimistic project estimate.
There are plenty of good agencies that give project estimates, but it's important that this be brought up when you check with the agency's references. Were they able to deliver the project near the estimate, or did they abuse the privilege and stretch for more hours?
Don't get me wrong, there is nothing wrong with RFPs -- but good agencies get a lot of them. This means that if an RFP is bloated, asks a ton of irrelevant questions, and is a full 45 pages of administrative BS, the best agencies will just chunk it. By trying to be thorough, you might actually hurt your ability to have the best agencies respond.
At NeboWeb, we have a few rules about RFPs. First, we always contact the sender, even if it says not to. Think about it: If you want an agency to put in hours, or even weeks of work to reply to you RFP, you at least should have the decency to jump on a call and answer a few questions.
Second, we always ask how many agencies it was sent to. If it's more than 10, we don't respond. That means the sender didn't put any forethought or care into which agencies might be a good fit for the project. Good work comes from talented, hard-working people from both the agency and the client side.
If you essentially spammed out your RFP to 40 agencies, that says a lot about how much you value the project. The more choices you have, the harder the decision, and the more likely you will make a poor choice. It basically turns into a crapshoot. Don't believe me? There's research that bears this out -- check out "How We Decide," by Jonah Lehrer, to see the latest research and findings on multi-variable purchasing decisions.
Lastly, we always ask about budget. We're not expecting that a potential client give us an exact figure (although that is nice), but building a site is very similar to building a house. You wouldn't ask a contractor to just quote you on a four-bedroom, two-bath house. The budgets would vary widely depending on the amenities, the features, the neighborhood, etc.
A website is very similar. It's not enough to know the number of pages and technology. Do we use video elements throughout the site? Do we include a Flash tour? What cool factors are we including to add to the user experience? This is analogous to deciding whether you want granite counters, a pool in the backyard, etc. We could look at the same RFP and come up with a broad range of budgets we could work with to complete the project.
Hence, a different mindset sets in. Agencies, assuming price will be the most important factor, ditch all of the more creative ideas and respond with a barebones quote. To simply have agencies race to the bottom for the most simplified and cheap solution in an effort to win the project was probably not the goal of your RFP process.
All too often companies make these mistakes without even realizing it. It's easy to do, especially without someone on the team who has worked in the agency world. Fortunately, the mistakes that companies tend to make when choosing an agency are easily correctable. A little shift in perspective and a heightened awareness of the agency process will yield better decisions as well as more satisfying (and more effective) work.