Quick Answer
A good brief for WordPress development in Edinburgh explains what your business does, what the website must achieve, who it's for, which pages and features you need, who will supply content, your timeline and your budget range. Clear briefs get more accurate quotes and fewer surprises.
Key Takeaways
- Start with goals and customers, not colours and fonts.
- List must-have features separately from nice-to-haves.
- Be honest about who will write content and supply photos.
- Sharing a budget range gets you more realistic proposals.
In This Article
Most website projects that go wrong don't fail because of bad code. They fail because the developer built exactly what they were asked for, and what they were asked for wasn't quite what the business needed. If you're planning WordPress development in Edinburgh, the single most useful thing you can do before speaking to anyone is write a clear brief. It doesn't need to be technical. It needs to be honest and specific. Here's how.
Why The Brief Matters So Much
A brief is the shared picture of what you're building. Without one, every developer you speak to fills in the gaps with their own assumptions. Quotes vary wildly, timelines slip and halfway through the project someone says, "Oh, I assumed it would do that."
A good brief:
- Gets you quotes you can actually compare
- Helps developers suggest better, simpler solutions
- Reduces changes and extra charges later
- Gives everyone something to check the finished site against
What To Include In A Brief For WordPress Development In Edinburgh
1. About Your Business
A short paragraph on what you do, who for and what makes you different. If you're a made-up wine bar in Leith, say so, and mention that most of your custom comes from locals midweek and visitors at weekends.
2. What The Website Must Achieve
Be specific. "Look modern" isn't a goal. These are:
- Get more table bookings direct, rather than through third-party sites
- Generate enquiries from businesses wanting private events
- Help festival visitors find us and our opening hours quickly
- Sell gift vouchers online
Pick one main goal and two or three secondary ones.
3. Who It's For
Describe your main customer types and what they want when they arrive. Edinburgh businesses often have more than one audience: locals, tourists, students, corporate clients. Each may need a slightly different path.
4. Pages You Need
A simple list, such as Home, About, Services, Menu, Book, Contact, Blog. Note which pages exist already and which are new.
5. Features And Integrations
Separate these into two columns:
| Must have | Nice to have |
|---|---|
| Booking system | Gift card sales |
| Contact form | Live chat |
| Email sign-up | Instagram feed |
Mention any tools the site must connect to, such as a booking platform, email marketing tool, CRM or payment provider.
6. Content And Photos
This is where projects stall most often. Be honest:
- Who will write the words?
- Do you have good photos, or will you need a photographer?
- Is existing content being moved across?
7. Examples You Like, And Why
Share two or three websites you admire, and say what you like about each. "The menu is easy to read on a phone" is far more useful than "I like it".
8. Timeline
When do you need it live, and why? A hard deadline, such as the start of the festival season, changes how a project is planned.
9. Budget Range
You don't have to name an exact figure, but a range helps enormously. It lets developers suggest what's realistic rather than guessing.
10. After Launch
Who will update the site? Do you want ongoing support, updates and search work? This affects how the site should be built.
Things You Don't Need To Specify
You don't need to choose a theme, pick plugins or decide on technical architecture. That's the developer's job. Tell them the problem; let them suggest the solution. If you have strong preferences, mention them, but stay open.
Common Brief Mistakes
- Starting with design. Colours and fonts matter, but goals come first.
- Listing every possible feature. More features means more cost, more maintenance and more confusion for visitors.
- Forgetting mobile. Most of your visitors, especially in a city full of tourists, will be on their phones.
- Assuming content will appear. It won't. Someone has to write it.
- Not mentioning ownership. Say you want the hosting, domain and admin accounts in your business's name.
What Happens After You Send It
A good developer will read your brief and come back with questions. That's a healthy sign. Expect them to ask about your customers, your competitors, what's not working on your current site and how you'll measure success. Some may suggest dropping features you thought you needed, or adding something you hadn't considered. Listen, but stay anchored to your goals.
When proposals arrive, check each one against your brief. Does it cover every must-have? Does it explain what's not included? Is there a clear plan for content, testing and launch? If one proposal is much cheaper, look carefully at what's been left out. If one is much more expensive, ask what the extra buys you.
A Simple Way To Start
Open a document and answer these five questions in plain English:
- What does my business do, and for whom?
- What should the website help people do?
- What must it include?
- Who's providing the words and pictures?
- When do I need it, and roughly what can I spend?
That's the skeleton of a brief. Add detail from there. If you want a framework for what the pages themselves should do, our guide to a simple website framework that converts is a useful companion, and our post on how long it takes to build a website will help you set a realistic timeline.
How Starien Can Help
We're a small team based in Coleraine, and we work with businesses in Edinburgh and elsewhere remotely. Our Web Development service starts with understanding your goals before anything gets built, and we're happy to help you shape a brief. After launch, Orbit, our monthly website plan, covers updates, SEO and AEO, with ad hoc work billed hourly.
Frequently Asked Questions
What should a website brief include?
Your business background, the site's goals, your audience, the pages and features you need, examples you like, who supplies content, any integrations, your timeline and a budget range.
Should I tell a developer my budget?
Yes, a range at least. It helps developers suggest what's realistic and avoids proposals that are far too big or too small for what you can spend.
How long should a website brief be?
Two to four pages is plenty for most small business sites. Clarity matters more than length.
Filed Under