Choosing a web developer

I recently had the privilege of helping a client choose a web development company.  It was quite a rewarding task because - even though it means by definition that I don't get the development job - it's great to look at the whole selection process from a new angle. Having hired and been hired, it was new to be objectively assessing other companies and translating the techno-babble into real English that my clients could understand. 

I was brought in, after brief consultation on the writing of the tender documents, to look at and compare the different tenders and then to lead interviews with the candidates. I saw my role chiefly as that of a facilitator and translator. There was little point in my choosing a company for the client: it was they who would need to be able to work with the chosen company. My job was to make that choice work.

The process brought home the golden rules one should apply when attempting to select a web development company, which to my mind are as follows:

1. Compare like with like. This starts with the tender document. Be as specific as you can to get actual answers rather than vague "you could do it this way or that". Then follow through on receipt of tenders and ask questions to get clarity on what is on offer.
2. Check the portfolio. If you don't like any of the previous work, you're unlikely to like the new stuff. But do not be put off by a single bad example if there are many good examples! Remember some companies are stronger in design and some stronger in development. Be aware what you need.
3. Check the proposed platforms. You may not care what your site is built on. You may, in a year's time, care if it is on a proprietary, esoteric system and you cannot upgrade it.
4. Enlist the help of a techie. Techies talk tech and miscommunication can be the bane of a relationship between client and designer. Get someone who can help decode the acronyms and spot hollow sales promises.
5. Meet them. You'll have to work with these people, so it is important that you get on with them. If you just don't gel or continually misinterpret eachother, this is not a good foundation for a stable relationship.

I am happy to report that the client found a developer they were happy with and the last I heard they were deep in information architecture territory. A win all round!