# How To Write A Website Brief For A Web Developer In Northern Ireland

URL: https://www.starien.com/blog/how-to-write-a-website-brief-for-a-web-developer-in-northern-ireland
Published: 2026-09-20
Author: Geoffrey Moffett
Topics: website brief, web development, planning, Northern Ireland, small business websites

> A simple website brief template for Northern Ireland businesses: goals, audience, pages, features, content, budget and timings, so developers can quote accurately.

## Quick answer

A good website brief explains why you need the site, who it is for, what it must do, which pages and features you need, who will provide the content, your budget range and your deadline. It does not need to be long or technical. One to three clear pages help developers quote accurately and make different quotes easier to compare.

## Key takeaways

- Start with the business goal, not the design.
- Describe your customers and what they need to do on the site.
- List must-have features separately from nice-to-haves.
- Share a budget range so developers can suggest what is realistic.

If you've ever sent "how much for a website?" to three developers and got three wildly different answers, you're not alone. The fix is a short, clear brief. A website brief for a web developer in Northern Ireland doesn't need to be technical or long. It just needs to explain what you want the website to achieve, so everyone's quoting for the same thing.

Here's what to include, with a template you can copy.

## Why A Brief Saves You Time And Money

Without a brief, developers fill the gaps with guesses. One assumes you need five pages and a contact form. Another assumes a shop with 200 products. Their quotes aren't comparable, and you can't tell which is good value.

A brief also helps you. Writing it forces you to decide what really matters, which makes the whole project faster and less stressful.

## What To Include In A Website Brief For A Web Developer In Northern Ireland

### 1. About Your Business

A few lines on what you do, where you're based and who you serve. "Family-run garden centre near Antrim, selling plants and garden supplies to local households and landscapers."

### 2. Why You Need A New Website

What's the trigger? An outdated site, a new service, a rebrand, too few enquiries, or a site you can't edit? Be honest. "Our current site is six years old, doesn't work well on phones and we can't update it ourselves."

### 3. Goals

What should the website achieve? Make them measurable if you can.

- More enquiries for a particular service.
- Online bookings instead of phone calls.
- Fewer repetitive questions to staff.
- Selling vouchers or products online.

### 4. Your Customers

Who visits, and what do they need? "Mostly homeowners aged 35 to 65, browsing on phones, wanting to check opening hours, see what's in stock and book a garden design consultation."

### 5. Pages

A rough list is fine. For example: Home, About, Services (with a page for each service), Gallery, FAQs, Blog, Contact. Mention if you'll need location pages, landing pages for campaigns or a members' area.

### 6. Features

Split into must-haves and nice-to-haves.

**Must-have:** contact form, booking for consultations, Google Maps, mobile-friendly.

**Nice-to-have:** gift vouchers, newsletter sign-up, blog.

### 7. Integrations

Which tools must the website connect to? Booking software, CRM, email marketing, payments, stock or accounts. Name them if you know them.

### 8. Content

Who's writing the words and providing photos? This is the most common cause of delays. Be realistic about whether you'll have time, or whether you need help with copywriting and photography.

### 9. Who Updates It

Who'll edit the site after launch, and how often? This shapes the platform choice more than anything.

### 10. Websites You Like (And Why)

Two or three examples, with a note on what you like: "clear menu", "big photos", "booking button always visible". Also any you dislike.

### 11. Budget Range

A range, not a single number. It helps developers suggest the right level of solution. If you're unsure, our guide to [what a website costs in Northern Ireland](/blog/how-much-does-a-website-cost-in-northern-ireland/) gives you a sense of the factors involved.

### 12. Timescale

When do you need it, and why? A seasonal business on the Causeway Coast might want the site live before Easter. Allow time for content and feedback, not just the build.

### 13. After Launch

Do you want ongoing maintenance, updates and support? Saying so upfront means quotes include it, or at least mention it.

## A Simple Template To Copy

> **Business:** what we do and where.
> **Why now:** the problem with the current situation.
> **Goals:** two or three outcomes.
> **Customers:** who they are and what they need from the site.
> **Pages:** rough list.
> **Must-have features:** list.
> **Nice-to-have features:** list.
> **Integrations:** tools to connect.
> **Content:** who provides words and photos.
> **Editing:** who updates it and how often.
> **Examples:** sites we like and why.
> **Budget range:** from and to.
> **Deadline:** date and reason.
> **Ongoing support:** yes or no, and what kind.

## Gathering Information Before You Write

Strong briefs are written with a little evidence to hand. Before you start, spend half an hour pulling together:

- **Your most common customer questions.** Ask whoever answers the phone or replies to messages. These become FAQs and shape page content.
- **Where enquiries come from today.** Google, Facebook, word of mouth, a directory? It tells the developer what to prioritise.
- **What's not working.** Pages people complain about, forms that attract spam, things staff avoid updating.
- **Your analytics, if you have them.** Which pages get visits, and which are ignored?
- **Any brand materials.** Logo files, colours, fonts and photography you already own.

Share what you can. Even rough notes give a developer a much clearer picture than a list of pages alone, and they help you spot priorities you might have missed.

## Who Should Be Involved

Write the brief with the people who'll use the website most, not just the owner. Front-of-house staff know what customers ask. Whoever handles social media knows which content gets a reaction. A short chat with each saves surprises later.

## Mistakes To Avoid In Your Brief

- **Describing the design instead of the goal.** "Blue with a big video" tells a developer less than "we need more consultation bookings".
- **Listing every feature you've ever seen.** It inflates quotes. Stick to what supports your goals.
- **Leaving content until later.** It's the most common cause of delays.
- **Hiding the budget.** You'll get quotes for things you can't afford.
- **Forgetting who'll maintain it.** A site nobody updates soon looks neglected.

## What Happens Next

Send the same brief to each developer you're considering, and ask them to explain their recommendations, not just give a number. Then compare how well they understood your goals, not only the price. Our guide on [choosing a web design agency in Northern Ireland](/blog/how-do-i-choose-a-web-design-agency-in-northern-ireland/) has more questions to ask.

If you'd like to talk through your brief, our [web development](/web-development/) team is happy to help you shape it, even if you're still deciding who to work with. A clear brief makes for a better website, whoever builds it.

## Frequently asked questions

### How long should a website brief be?

One to three pages is plenty for most small businesses. Clarity matters more than length.

### Should I tell developers my budget?

Yes. A range helps developers recommend what is achievable and avoids quotes that are miles apart because everyone guessed differently.

### Do I need to know which platform I want?

No. Describe what you need the site to do and who will update it. A good developer will recommend a platform and explain why.
