Hello all,
In the style of questions to ask your accountant, would anyone be willing to share their gems of wisdom in relation to what questions you should be asking someone before you pay them to build your website? Feel free to start from the basics!
Thanks.
I think it probably depends a lot on what you want him to build. Is it a largely visual/graphics affair, or is it search engine bait to attract new customers, or is it an online application, eg online timesheeting system, etc.
I think some general rules apply when hiring a web developer
1) proven track record - can you see details of work they've done before, and speak to customers. Google them - any horror stories?
2) are they local/UK based? If they are outsourcing it all to India it will be cheaper - but it can cause a whole load of other problems. So weigh the budget available against timeframes, etc
3) make sure the division between what the web developer does and what you have to provide is clear. Will you provide mockups of the design, or is the developer doing the conceptual visual design too? Will you design how every page works, or is he using pre-existing software, and your site will largely inherit design and functionality of that
4) who owns the copyright of the designs? In absence of agreement to the contrary your developer will most likely own copyright.
5) how will fees be calculated. Will you agree fixed cost in advance? How much will be paid in advance, how much upon completion? What happens if you change the design during development, or issues arise that weren't dealt with in original spec?
6) What about bugs that surface later? You can't expect the developer to fix bugs that only appear years into the future for free - so will there be a period of support cover, beyond which you pay for continued support?
7) Will the developer host the site, or will you do that separately? Pros and cons to both... hosting separately means you are less dependent on the developer if you fall out, or he disappears. But if its a complex web application there are advantages to having him responsible for hosting as well (when a problem arises, there isn't the debate as to whether its a result of bad code or bad hosting).
8) err probably loads more I haven't mentioned