How to Write Your Own Website Brief (Even If You've Never Done It Before)

You know you need a website. You’ve probably even started conversations with designers or agencies. But when they ask “what are you looking for?” you freeze. “Something modern” sounds vague. “Make it convert” doesn’t tell them much. And listing features—contact form, blog, nice photos—misses the actual point of why you need this site.

Writing your own brief before talking to web studios saves weeks of back-and-forth, prevents expensive misunderstandings, and dramatically increases the chances of getting a website that actually works for your business. Here’s exactly what to include, even if you’ve never written a brief before.

Why Writing Your Own Brief Matters

Most website projects fail not because of bad design or poor coding, but because the brief was unclear from the start. According to research on web project success factors, projects with comprehensive pre-kickoff preparation experience 40% fewer revision cycles and ship significantly faster.

When you arrive at a web studio with a clear brief, you’re not just saving their time—you’re saving your own money and getting better results. A designer who understands your audience, objectives, and constraints from day one can propose smart solutions. Without that context, they’re guessing.

The brief doesn’t need to be perfect. You don’t need final copy polished to the word. But you do need to have thought through the fundamentals: who this site serves, what action you want them to take, and what success looks like. Three hours spent writing a brief prevents three weeks of revision cycles later.

The Essential Brief Template

Copy this template into a Google Doc and fill in each section. Don’t skip the questions that feel hard—those are usually the most important ones.

1. Business context and core offer

Start with the basics. Your web studio needs to understand what you do and why this website matters to your business right now.

Answer these questions:

What does your business do? (Explain it as if to a friend who’s never heard of your industry)
Who are your ideal clients or customers? (Be specific: “Series A SaaS founders” beats “tech companies”)
Why do you need this website now? (New launch, rebrand, existing site failing, expanding into new markets)
What’s the primary business goal for this site? (Lead generation, direct sales, brand positioning, resource hub, booking consultations)

Example brief snippet:

“We’re a Nottingham-based accountancy practice helping manufacturing SMBs with 10-50 employees manage VAT compliance and year-end accounts. We currently win clients through referrals and networking, but we’re expanding geographically and need a site that converts cold traffic from Google search. Main goal: generate 8-12 qualified consultation bookings monthly from organic search.”

This context shapes everything from page structure to CTA placement to the words your designer chooses. Without it, they’re designing blind.

2. Target audience pain points

Your designer can’t create compelling messaging without understanding who you’re speaking to and what keeps them up at night. Generic statements like “small business owners” don’t cut it.

Map out these audience details:

What specific problem does your service solve? (Not “poor performance”—actual scenarios like “they’re manually tracking inventory in spreadsheets and losing stock”)
What are they currently doing instead of working with you? (DIY, competitor, suffering without a solution)
What makes them finally decide to look for help? (Trigger events: regulatory change, rapid growth, breakdown of current system)
What worries them most about hiring someone like you? (Cost, time commitment, whether it will actually work, trusting an outsider)

When Fernside Studio runs Launch Sprint strategy calls, we spend half the conversation on audience understanding. If you can’t articulate why your ideal client should care within 30 seconds, your designer will struggle to create a hero section that converts.

3. The single most important action

Every page should guide visitors toward one primary action. What is it?

Define your primary conversion goal:

Book a consultation call
Download a pricing guide
Request a quote
Purchase a product
Subscribe to a newsletter
Fill out a project brief form

Be specific. “Get in touch” is vague. “Book a 20-minute scoping call using our Calendly link” is clear. Your designer needs to know exactly what success looks like to optimise the entire site around making that action easy and obvious.

Secondary actions exist too—maybe you also want people to follow you on LinkedIn or download a case study. But identify the one action that matters most to your business. That’s what gets the prominent placement above the fold.

4. Budget range and timeline

Designers can’t propose appropriate solutions without knowing your constraints. A £1,200 budget suggests different approaches than a £6,000 one.

Be upfront about:

Total budget you’re working with (or realistic range)
Any hard launch deadline (conference, funding round, contract renewal, seasonal factors)
Whether this is a fixed budget or flexible depending on value
Payment structure preferences (deposit, milestones, final balance)

If your budget feels tight, say so. Good studios will suggest phased approaches or simplified scopes that deliver value within constraints. Surprises about budget limitations mid-project damage trust and outcomes. We cover realistic website budgeting in how much does a website cost in the UK.

5. Sites you admire (and why)

Nothing clarifies requirements faster than concrete examples. Share 3-5 websites you like and explain specifically what appeals.

For each example site, note:

What specifically do you like? (Layout, colour treatment, navigation style, copy tone, section structure)
What would you do differently? (Too busy, not enough white space, confusing navigation)
Is this a competitor, adjacent business, or just visual inspiration?

“Like this hero layout but with stronger CTA prominence” is infinitely more useful than “make it modern.” Visual references give your designer a starting point and reveal your aesthetic preferences faster than a thousand words.

Include sites you dislike too, with brief notes on why. “Avoid carousel sliders like this example” prevents your designer from proposing something you’ll hate.

6. Content and assets inventory

Take stock of what you already have. Studios can’t quote accurately or plan timelines without knowing content readiness.

Document these assets:

Copy: Existing content to repurpose, drafts in progress, needs writing from scratch
Photography: Professional photos available, stock images acceptable, photoshoot required
Logo and branding: Logo files (.svg preferred), colour palette (hex codes), fonts, brand guidelines
Testimonials and proof: Client quotes, case studies, results data, awards, certifications, client logos (with permission)
Video content: Existing videos to embed, or not applicable

Be honest about gaps. Finding out mid-project that promised content doesn’t exist creates delays and frustration. If you’re unsure what copy you need, ask your studio for a content outline during the brief review—most will provide this.

For projects like Fernside’s Launch Sprint, content readiness directly determines whether you can hit the five-day timeline. Our clients who prepare content in advance get better results faster.

7. Features and functionality

List what the site needs to do, separating must-haves from nice-to-haves. Be specific about functionality rather than prescribing design solutions.

Must-have features (site doesn’t work without these):

Contact form with specific fields (name, email, company size, project type, timeline, message)
Mobile-responsive design
SSL certificate and security
Fast loading times
Analytics tracking

Nice-to-have features (valuable but not critical):

Blog functionality with category filtering
Client portal or resource library
Booking system integration
Newsletter signup
Case study showcase
FAQ section

Don’t prescribe solutions (“I want a carousel”) when you should be describing problems (“I need to showcase five different services clearly above the fold”). Your designer can propose better solutions when they understand the underlying goal.

Most successful SMB sites launch with must-haves only, then add features based on actual user behaviour rather than assumptions.

8. Technical preferences and constraints

If you have strong technical preferences or constraints, state them upfront. Don’t assume your studio will know.

Cover these points if applicable:

Hosting: Self-hosted, studio-managed (like Fernside’s included hosting), or specific platform requirements
CMS needs: Do you need to edit content yourself (Fernside CMS style), or are you happy with ticket-based updates?
Performance targets: Any specific page speed requirements or mobile-first priorities
Accessibility: WCAG compliance level if required by your sector
SEO considerations: Existing site to preserve rankings, keyword priorities, migration planning
Integrations: CRM, email marketing, payment processors, booking systems

Fernside Studio builds exclusively on Astro and Cloudflare Pages for performance reasons. If you have strong technical preferences, voice them during studio selection rather than mid-project. Understanding how long a website takes to build helps set realistic expectations too.

Common Brief-Writing Mistakes (and How to Avoid Them)

Mistake 1: Being too vague

“Make it modern and professional” tells your designer almost nothing. Modern to whom? Professional in what industry context? These words mean different things to different people.

Instead, be specific:

“Clean, minimal aesthetic like [example.com] with generous white space and typography-led design”
“Professional but approachable—think boutique consultancy, not corporate law firm”
“Monochrome palette with single accent colour for CTAs, avoiding busy patterns or stock photography”

When you can’t find the words, find example sites and screenshots. Visual references eliminate ambiguity.

Mistake 2: Fixating on features instead of outcomes

Briefs often prescribe solutions (“I want a blog, newsletter signup, client portal, and video backgrounds”) rather than explaining what you’re trying to achieve.

Your designer can’t optimise solutions if they don’t understand the underlying goal. Instead of dictating implementation, explain what you want to accomplish.

Problem-focused brief language:

“Visitors need to understand our three service tiers immediately” not “I want a pricing table”
“We need to build trust with risk-averse prospects” not “Add more testimonials”
“70% of our traffic is mobile” not “Make buttons bigger on phones”

This collaborative approach leverages your studio’s expertise while keeping your goals central. We cover this in how to brief your web studio so they nail it first time.

Mistake 3: Not having content ready

“We’ll write the copy later” sounds efficient until you realise the site can’t launch without it. Content creation takes longer than most founders expect, and discovering mid-project that you need to write 3,000 words across seven pages derails timelines.

Prepare content realistically:

Draft at least rough outlines for each page (bullet points of what needs covering)
Gather existing copy to repurpose from proposals, LinkedIn, pitch decks
If hiring a copywriter, factor that into timeline and budget now
Consider what proof points and testimonials you actually have permission to use

The Netlify website brief guide notes that missing content is the single biggest cause of project delays. Address it upfront.

Mistake 4: Ignoring mobile entirely

You’ll review designs on your laptop, but according to BrowserStack’s mobile usage data, 58% of website traffic now comes from mobile devices in the UK. What looks perfect on a 27-inch monitor becomes three scrollable screens on a phone.

Think mobile-first:

What information matters most to someone researching you on a phone? (Probably pricing, contact methods, and proof you’re legitimate)
How does your hero section work on a 375px screen?
Are your CTAs obvious and tappable on mobile?

Every Fernside build is responsive by default, but mobile-first thinking must inform your content hierarchy from the brief stage.

Mistake 5: Unrealistic timeline expectations

“Can we launch in two weeks?” depends entirely on scope and preparation. A simple one-page site with ready content? Potentially, through something like our Launch Sprint. A ten-page site with custom features, no content, and multiple stakeholder approvals? Not remotely realistic.

Common timeline mismatches:

Five-day timeline with extensive custom features and no content ready
Multi-page site expecting launch while copy is still being written
Complex integrations without API access or authentication sorted
Perfect-pixel design matching mockups but no design phase budgeted

Studios appreciate clients who understand what’s achievable within constraints. Our post on how long does a website take to build breaks down realistic timelines by project type.

Making Brief-Writing Manageable

Writing a comprehensive brief sounds overwhelming if you’ve never done it. Break the work into focused sessions.

The three-hour brief sprint

Block focused time and tackle the brief systematically:

Hour 1: Core content (60 minutes)

Business description and objectives (15 min)
Target audience detail and pain points (20 min)
Primary conversion goal and success metrics (15 min)
Budget and timeline parameters (10 min)

Hour 2: Direction and assets (60 minutes)

Find and annotate 3-5 example sites you admire (20 min)
Gather brand assets: logos, colours, fonts, photos (20 min)
Document content inventory and gaps (20 min)

Hour 3: Requirements and refinement (60 minutes)

List must-have vs. nice-to-have features (15 min)
Technical requirements and integration needs (15 min)
Review for clarity and fill in missing details (30 min)

This structured approach prevents brief-writing from becoming an endless task that never gets completed. Set a timer and work through each section methodically.

Use a simple template structure

If your chosen studio provides a brief template, use it—they’ve designed it to capture exactly what they need. If they don’t, this structure works well:

Executive Summary (1 paragraph): Business, goal, audience, timeline, budget
Business Context (1 page): What you do, who you serve, why you need this site now
Audience and Objectives (1 page): Target audience pain points, primary conversion goal, success metrics
Scope and Features (1 page): Must-have and nice-to-have functionality
Visual Direction (1 page): Example sites, brand assets, aesthetic preferences
Content Inventory (0.5 page): What you have, what you need, who’s creating it
Technical Requirements (0.5 page): Hosting, CMS, integrations, performance needs
Appendices: Brand guidelines, content drafts, reference screenshots

Keep the core brief to 3-5 pages maximum. Detailed appendices for supplementary materials. Use headings, bullets, and white space to make it scannable.

What to Do with Your Brief

Once you’ve written it, your brief becomes the foundation for conversations with web studios and the reference document throughout the project.

Shopping for the right studio

Share your brief with 2-3 potential studios during initial conversations. This helps you compare not just pricing, but how well each studio understands your needs and proposes solutions.

Good studios will ask clarifying questions: “When you say ‘modern design,’ can you point to specific examples?” or “Your timeline is tight—would you consider phasing the launch?” These questions indicate they’re thinking critically about your requirements.

Studios that quote immediately without probing your brief are either guessing or working from templates. The best partners engage deeply with your goals before proposing solutions. We walk through what to look for in how to choose a web designer in the UK.

Using it during the project

A good brief doesn’t disappear after kickoff. It becomes the touchstone for project decisions:

Scope questions: “Is this in scope?” Check the brief.
Prioritising tradeoffs: “Which matters more?” Refer to stated objectives.
Evaluating proposals: “Does this approach serve our goals?” Compare to the brief.
Measuring success: “Did we achieve what we set out to?” Review success criteria.

Keep the brief accessible throughout the project in a shared Google Doc. Both you and your studio will reference it regularly. Update it if significant requirements change, but resist the urge to expand scope without adjusting budget or timeline.

When your brief can be simpler

Not every project needs five pages of specifications. Some scenarios warrant streamlined briefs:

Simpler briefs work for:

Single-page sites: Launch Sprint builds need clarity over comprehensiveness—single conversion goal, tight messaging, ready content
Repeat engagements: Studios familiar with your brand need less background context
Studios with strong discovery: Some prefer conversations to documents, then create the detailed spec themselves
Templated approaches: If using a platform with limited customisation, extensive briefs matter less

When in doubt, ask potential studios what level of detail they need. They’ll tell you if you’re over-preparing or missing critical information.

Real Examples: Weak vs. Strong Brief Language

Seeing the difference in practice clarifies what works.

Business objectives

Weak: “We want more traffic and better conversion.”

Strong: “We currently get 800 monthly visitors (mostly from organic search for ‘Nottingham accounting services’) but only 1.2% book consultations. Goal is to increase consultation bookings to 4% conversion rate within three months of launch by clarifying our service offering and reducing form friction. Success means 30+ qualified consultation requests monthly.”

Visual direction

Weak: “Something clean and modern that stands out.”

Strong: “Monochrome palette (black, white, one grey tone) with forest green accent for CTAs. Generous white space, typography-led design, no stock photography. Reference sites: [example.com] for layout structure and how they handle service descriptions, [example2.com] for their minimal navigation approach. Avoid: busy background patterns, carousel sliders, generic hero images with overlaid text.”

Target audience

Weak: “Small business owners who need websites.”

Strong: “Manufacturing SMBs, 20-80 employees, £3-12M revenue. Typically Operations Directors or Marketing Managers dealing with outdated websites that don’t reflect their actual capabilities. They’re time-poor, risk-averse, need clear pricing and process, and choose providers based on portfolio quality and local presence. Current frustration: their site looks amateur compared to competitors.”

Feature requirements

Weak: “Contact form, blog, and mobile-friendly.”

Strong: “Contact form with fields: name, email, company, service interest (dropdown: Accounts, Tax, Payroll, Advisory), timeline (dropdown: Urgent, 1-3 months, Exploring options), message. Spam protection via Cloudflare Turnstile. Form submissions email to [email] with auto-confirmation to user. Blog structure for 2-3 posts monthly, category filtering by service type, RSS feed. Responsive design optimised for mobile (60% of our traffic), Lighthouse score target 90+ mobile.”

The specificity difference is clear. Strong briefs leave minimal room for misinterpretation while still giving designers creative freedom within defined parameters.

Getting Internal Alignment Before Writing

If you have a team or multiple stakeholders, brief quality often suffers when people aren’t aligned internally. Resolve disagreements before briefing external studios.

Pre-brief alignment checklist:

Agreement on primary website objective and success metrics
Consensus on target audience and positioning
Aligned understanding of scope and budget constraints
Clear decision-making authority established (who has final approval?)
Visual direction that all stakeholders support
Content responsibilities assigned (who writes what, by when?)

Briefing a studio while your team still debates fundamentals wastes everyone’s time and creates conflicting feedback later. Sort strategic alignment first.

How Fernside Studio Uses Your Brief

When you come to Fernside Studio with a well-prepared brief, it transforms our entire approach.

For Studio Site engagements, we start with an onboarding workshop where we review your brief together, ask clarifying questions, and expand it into detailed page-by-page specifications. Your preparation determines whether we’re teaching fundamentals or optimising details. Prepared clients get better sites faster.

For Launch Sprint projects (five-day, one-page builds at £750 fixed), the brief becomes even more critical. The compressed timeline demands absolute clarity on audience, message, and conversion goal. Ambiguity derails five-day builds faster than technical challenges.

In both cases, your brief becomes our reference document. When design decisions arise—“Should this CTA be prominent or subtle?” or “Do we need to explain this service in detail or just link to it?”—we refer back to your stated objectives and audience needs.

We also share your brief with our Fernside CMS implementation if you add that service. Knowing which content areas you’ll want to edit yourself helps us structure the CMS intelligently from the start rather than retrofitting it later.

When You’re Ready to Move Forward

Writing your own brief before talking to web studios is the single highest-leverage activity in website projects. Three hours of focused preparation prevents weeks of misaligned development and expensive revision cycles.

A great brief balances completeness with clarity. It provides context without overwhelming, specifies requirements without prescribing solutions, and establishes success criteria without unrealistic expectations.

Start with the template above. Fill in what you know, flag what you’re unsure about, and be honest about constraints. Your web studio can work with uncertainty if you’re upfront about it—but they can’t work with assumptions that turn out to be wrong mid-project.

If you’re preparing to work with a web studio, invest the time in your brief. The project that follows will be faster, smoother, and far more likely to deliver exactly what your business needs.

The more thought you put into your brief, the better website you’ll get. But don’t let brief-writing become an excuse to delay. Every week without a working website is a week prospects are landing on your competitors’ sites instead.

We only take on a handful of projects each month, and well-prepared founders fill slots fast. Check availability and we’ll confirm your earliest build slot within 24 hours. Share your brief with us — even if it’s rough — and we’ll help you refine it during a scoping call. Whether that’s a focused Launch Sprint or a comprehensive Studio Site build, the time to start is now.

Sources

A Comprehensive Website Planning Guide (Part 1) — Smashing Magazine, 2018
How To Write A Website Design Brief (+ Template) — Yellowball
13-Step Checklist for Website Requirements Documentation — BugHerd
How Long Should a Web Design Project Take, and How Can I Speed it Up? — Bold August Design Studio
Ideal Screen Sizes for Responsive Design — BrowserStack
Website Design Brief Template — Splitpixel