To be clear, we’re not suggesting you simply provide your agency with a list of answers to all of these questions. But if you have these in mind whilst designing your brief, and if you can engineer it in such a way that whoever reads it feels as though they could answer them, you’ll be on the right track.
Key section - your customers
Your brand would be nothing without its customers so pay special attention to them throughout your storytelling. Tell your agency about your customer base and (if they aren’t the same thing) your ideal customer. How old they are, where they live, how much they earn, their beliefs and values, their hopes and fears.
Tell your agency why you want to target specific customers over others. If you’re facing any challenges doing so, explain what those challenges are and how you hope to overcome them.
Top tip: If you don’t know much about your customers, Google analytics reports can provide good info for both demographics and psychographics.
2. Your current e-commerce platform
Our next piece of advice is to give your agency as much information as possible about the current state of your e-commerce platform - if you have one. Tell them what you like about it. Tell them what it does well and in what areas it’s improved your business. Simultaneously, tell them what you dislike. Where is it letting you down, and how do you picture it working for you in the future? If you have specific requirements - multilingual, multi-currency, augmented reality etc. - make sure to stress these (more on this later).
If you don’t have a site yet, and you’re writing a design proposal for your first e-commerce platform, tell your agency why you want to sell online. What stage is your business at now? What challenges do you face? And why do you see an e-commerce platform as the answer to these issues? Don’t worry, this isn’t a test. But the more information you provide about where you’re at, and where you want to be, the better your agency will understand the project.
3. Requirements
This is a big one. Alongside letting your agency into the world of your brand, telling them exactly what you want from your website is the most important aspect of your brief.
Must-haves vs nice-to-haves
A good task to perform before you begin writing is to separate your needs into two categories: must-haves and nice-to-haves. Pretty self-explanatory, but must-haves are those features that you cannot do without. Nice-to-haves are add-ons. If you already have an e-commerce platform in place, it’s quite likely that must-have features are the reason you’re writing this brief in the first place.
If your brand is on the brink of bursting into a new international market, for instance, but your store can’t handle more than one language and currency, multilingual and multi-currency capabilities are sure to be must-have features.
Nice-to-haves are features you want, but aren’t pivotal. They’re the things you’ll add if time (and budget) allows, but won’t be the focus of the project. Sometimes it can be difficult to differentiate between must-haves and nice-to-haves. Ultimately, there’s no right and wrong way to decide which is which. It’s up to you and depends on the things you want for your business.
If you’re finding it difficult to decide, or if you don’t know which ones will be most effective for your business, explain this dilemma to your agency. If you’ve chosen well, they’ll be industry experts with a wealth of experience. They’ll know how to get your brand from A to B, and they’ll know which website features will make that journey easiest.
It’s important, therefore, not only to write a good website brief, but also to pick the right digital agency.
Listing requirements as must-haves vs nice-to-haves helps you and your agency to collaboratively define the MVP (Minimal Viable Product, also known as V1 scope). This is the minimum set of features that must be in place from the moment you go live. We advise our clients to begin with an MVP and only expand functionalities later, once they have data analytics and user feedback to guide their decisions. This prevents them buying a Ferrari before they know how to drive.
How to structure your requirements
When structuring the platform requirements in your website brief, these are good divisions to follow:
1. Platform pages - the pages you need on your new platform and a brief explanation of what the page is about.
2. Platform features - the features you need and why you need them.
3. Platform integrations - state which other system(s) your platform needs to ‘talk’ to. If available, add a link to the API documentation of the tool (this is usually found on the company’s website).
4. Platform scalability - the languages and/or currencies you want to sell in.
Scope of responsibilities - stating what you want the agency to do for you. Design and development, or only the latter?
5. Migration work - Where necessary, state the work to be done for the migration from your previous platform, and who will be responsible for it.
Top tip: always remember this process is collaborative. The creative brief needs to be as detailed as possible but your agency will have their own input. You’re not expected to have the full website design ready to go all by yourself!
Requirement research
We’re going to bet that you have at least some ideas about which new features you’d like on your website. Even if this is the case, even if you already have the entire project mapped out in your mind, it’s still good to get as many relevant opinions as you can. You may not have thought of everything.
How to do this? Firstly, give everyone in your organisation a voice. Ask the people that’ll be working with your site each day which features they’d like to see. Perhaps they’ll have some requirements that you hadn’t previously considered, and which could ultimately streamline workflows and boost sales.
Secondly, ask your customers. They’re the ones that’ll be using your website, so it’s with the customer in mind that every change should be made. If there’s a feature that they unanimously request, you’ll know that it’s a must-have. Keeping the customer engaged like this is also a good way to make them feel appreciated. This will in turn boost brand loyalty and minimise the risk of them defecting to a competitor.
4. Don’t panic
In 2021 it’s more important than ever for brands to move online. However the digital world isn’t as familiar to some as it is to others. We know there are many people that want to run a business and build a brand, but have little-to-no knowledge of e-commerce. Our advice here: don’t panic.
Your agency will understand that not everybody is an e-commerce, design, and/or development guru. Even if you have absolutely no idea what you want your website to do and/or look like, any information is useful. Even down to the most basic suggestions like colour palettes and images you’d like to use can spark ideas from your development agency.
Alternatively, give a list of websites you use frequently. Name what you like about them, and anything that irritates you or you think should be different. Give a list of competitor’s websites you envy. Or ones you think are terrible.
Even if you think it is trivial, any scrap of information about your tastes and interests here will turn out to be useful.
5. Budget
This can be an uncomfortable one for some, but talking about your budget is an important moment in your briefing. A clear budget lets your agency know from the start what will be possible and what won’t. It’s all well and good having strong ideas about your website’s requirements. But some features will simply cost more than others to implement. If you don’t have the budget to match, it’s a waste of everyone’s time to start thinking about them.
Top tip: Give your agency a budget range rather than just one figure. They’ll then offer you a few options - a website at the top-end of your budget, and a website more in the mid-to-low range. You’ll see the differences between the two and you can decide whether you want to invest the extra money.
6. Schedule and measurability
A schedule is a massive asset to any website briefing. Deadlines, even if only rough estimates at an early stage, help to keep a project on track and give everyone involved an idea of the necessary hours. Managing expectations is an important part of any website development project and the website brief is where this begins.
But don't worry if you have no idea how long something should be expected to take. If your website briefing has an unrealistic schedule, your agency will explain why. You can then discuss whether to scale the requirements back, or extend the length of the project.
If you set off on the development journey without a clear schedule in mind, you risk a misunderstanding between all parties about how long each stage will take. So it's always best to propose a schedule that can be adjusted later than to give nothing at all from the very beginning.
Top tip: Together with your agency, discuss a schedule that has some room for manoeuvre. Unforeseen problems are all part of the process and can bring a project to a halt for a small period. If you don’t have any leeway in your project, you run the risk of missing your deadlines.
Measurability is a similar feature to a website brief. Goals are an important feature and the best goals are specific and measurable.
Here's an example:
Briefing 1: Brand X wants to increase traffic to their site.
Briefing 2: Brand X wants an increase in traffic of 20% by date Y.
Both are ambitious. They want to increase traffic to their site. That's great, however the added details in briefing 2 make it easier for us to prioritise how best to achieve the specific goals.
There’s a number of ways to increase traffic to a website. But giving us a target, and a date by which to achieve it, helps us to work backwards from the goal and select the best strategy for reaching it.
Top tip: Think of goals in terms of: conversion rates, average order value, sales, returns and so on.