10 things you need to tell your web developer

You’ve gone through the process of choosing a trusted web developer. You’re excited about the new website they’re going to build for you, not to mention all the business goals it’s going to smash.  

Here are the ten most important things you need to tell your web developer.

Giving valuable input 

To get the absolute most from the project, you’ll need to give them valuable input. They’ll need more than a three-line brief to do your project, and your money, justice.  

While you may want to leave them to ‘just get on with the job’, it’s a fine line crossed when ‘hands-off’ becomes simply lack of crucial input, which then results in a project that doesn’t fit the bill, tick the boxes, and get you where you need to be. 

It’s a two-way street 

It also works the other way. A good web developer wants to do the best job possible for you. Outstanding work reflects well on them and their reputation. As with any business support service, your gains are their gains.  

To get the most out of your working relationship, and the project you’re paying for, so everyone’s happy, here’s what your web developer needs to know.  

1. What you like and don’t like about your existing website 

Be as detailed as you like about the things you love and loathe about your current website. Whether it’s a colour scheme, copy style, navigation, etc. Why? It will help your developer avoid things you hate and having to change, potentially fundamental, aspects of the build later. 

2. What you specifically want the website to achieve 

Be as specific as possible about what you want to achieve with the new website. If not, it won’t be purpose-built to your business goals, and you won’t be able to judge its success. 

Being specific about goals also helps to avoid ‘project-creep’ because it can be set out from the start, what functions, pages and UX (user experience) are required. It doesn’t help anyone to get to the end of the project for you to then decide it doesn’t do what you need it to.  

3. The audience for your website 

The web developer will make a professional judgement on content, design and user journeys based on who your audience is. Again, as with goals, don’t leave this vague. Try to be as specific as possible. 

4. Your deadline 

As early as you can, specify any deadline. It will help your web developer plan ahead and build in time for any last-minute modifications. Maybe you don’t have a deadline, or if you do, perhaps to coincide with a product or campaign launch, make sure you communicate it.  

5. Your budget 

Suppliers understand there isn’t – usually – unlimited budget. Be upfront about funds available for the project so the developer can be upfront about what can and can’t be achieved.  

Depending on funds, there may need to be compromises made and they can then explain these to you so you can make the right decisions.  

6. Your other platforms, online activity and marketing 

Particularly if this website is part of your overall marketing strategy, the developer needs to know what other campaign activity and platform presence you maintain, so the new website can be built accordingly, with the right links, systems and content. 

Similar, if you use certain CRMs, applications and systems the website needs to work with, let your developer know the details. 

7. Other sites or online functionality that inspires you 

Letting your developer know what inspires you helps to guide them as to your tastes, style and aspirations – which is all good direction. 

8. What you value most on the project 

Whether it’s care and attention to improve the design, regular updates on progress, ease of maintenance when the developer has left the project, let them know so they can work in the right way to keep you happy and reassured your focus is their focus too. 

9. How involved you want to be 

There’s no doubt you’ll need to be involved at points throughout the project, but perhaps you’ll struggle to do this due to lack of time. Would it help to put touchpoints in the diary in advance? Or do you have expectations of weekly/bi-weekly catchups? 

Set expectations on contact and updates early in the project so your developer can meet these with ease. 

10. Your brand guidelines 

If you have existing brand guidelines your other material and online present adheres to, the website needs to adhere to these, unless it’s the start of a whole new rebrand. If you have brand guidelines, and they’re pertinent for this project, pass them on to the developer. 

If your brief to your new web developer can cover these 10 points, you’re all set to go ahead. Good luck with your new web project!  

Still need help with a web development project? No problem, just get in touch to chat with our web team. 

< Read more articles on our Web Academy