DEV Community

Cover image for How to Prepare a Website Development Brief in 2027: A Practical Guide for Business Owners
Dmytro
Dmytro

Posted on Originally published at cianbay.online

How to Prepare a Website Development Brief in 2027: A Practical Guide for Business Owners

A business owner wants a website and sends a developer several links to competitors. The message says, 'I want something like this. How much will it cost?' One developer assumes the project involves five pages and a contact form. Another assumes it requires a product catalogue, filters, customer accounts and online payments. Both estimates can be honest and still differ considerably because they describe different projects.

Obtaining a realistic quote and a result that meets expectations does not require the client to know how to code or specify the complete technical architecture. It does require a clear understanding of business objectives, customer needs, desired functionality and the boundaries of the first phase. A developer can then turn these requirements into an actionable specification.

1. The difference between a brief and a technical specification

A website brief describes the project from the client's perspective: what the company sells, who the website is for, which problems it should solve, what content is available and what outcomes the business expects. It can take the form of a questionnaire, a short written document or a summary of a project discussion.

A technical specification makes those agreements more concrete. It defines which pages, functions, integrations and user journeys will be delivered, under what conditions they will operate and how the completed work will be checked. A relatively simple website might need only a compact specification. A store, learning platform or booking system will need separate sections for its more complex requirements.

Project preparation from objectives and requirements through development to testing.
A technical specification turns an idea into a verifiable plan.

The brief should not become a collection of technical terms the client encountered online. If the owner needs to edit prices independently and capture enquiries, those requirements are initially more important than the name of a particular plugin. The developer can select tools according to the business requirements and explain any limitations.

2. Define the website's goals and audience

Begin with a simple question: what should a visitor do? They might request a consultation, buy a product, schedule an appointment, download a catalogue, enrol in a course or find the contact details of the nearest branch. The answer will influence the website structure, calls to action and necessary functionality.

A retailer selling standard products to consumers has different requirements from a manufacturer of specialist equipment supplying wholesale customers. The retailer might prioritise a streamlined checkout process. The manufacturer may be more concerned about quote requests, accurate product specifications and helping customers select compatible components.

Describe the main types of visitors, geographical markets, languages and devices. If an existing website is available, review which pages people visit and where they encounter difficulties. Avoid assuming the new website will produce a particular number of leads simply by existing. Demand, advertising, pricing and the quality of the business offering also influence results.

It can help to distinguish a primary goal from secondary goals. For instance, a clinic might prioritise appointment requests but also need to explain its services, provide directions and answer common questions. Clear priorities help avoid a homepage crowded with competing buttons that make it difficult to decide what to do next.

3. Choose the right type of website and its structure

A landing page, corporate website, catalogue and online store are designed for different purposes. A one-off event might need a single page with information, a programme, registration and payment. A company with several service areas will often benefit from separate pages for those services. If the choice is not yet clear, read our comparison of landing pages and multipage websites.

Prepare an approximate sitemap. A cleaning company, for example, may need a homepage, services, prices, previous work, company information, a blog and contact details. Not every page must be created immediately, but decide which pages are part of the initial launch and which can follow later.

Page count does not necessarily equal the number of unique layouts. A shop containing hundreds of products can use a shared product page template, while a five-page service website might require several distinct layouts. Clarify how much content the developer will enter manually and whether data preparation and import is needed.

4. Assemble content and visual references

Collect the logo, brand colours, photographs, service descriptions, prices, contact details, shipping information, examples of previous work and other relevant content. If some materials are not ready, identify who will prepare them and by when. Doing this makes it easier to plan development without delays caused by missing information.

Links to competitor websites and other references can be very useful, but explain what you like about each example: navigation, readability, colour palette, photography, product pages, appointment forms or the general approach to presenting the information. Two people may interpret the same reference quite differently.

Do not request an exact copy of another website, its photography or its written content. Use original or appropriately licensed material. If the website will support multiple languages, agree who will provide translations, which pages need them and how changes will be maintained after launch. Also establish who is responsible for preparing the business-specific legal and policy documents that may be required.

5. Describe functionality through user journeys

Instead of requesting a 'modern functional website', describe the actions customers and staff need to perform. A shop customer selects a product, size and colour, adds it to their basket, enters an address, chooses delivery and pays. A staff member receives the order, checks the information and prepares it for shipment. The journey reveals required features and dependencies.

A beauty salon has a different workflow. A visitor selects a service, a specialist and an available time, then confirms the appointment. The owner defines working hours, service duration, cancellation rules and whether a deposit is required. When a specialist is on holiday or unavailable, the system must take that into account when displaying appointment availability.

Separate essential launch requirements from desirable future features. For example, a store's first phase might require a catalogue, basket, checkout and payment. Loyalty programmes, automated marketing campaigns and advanced personalisation may belong in a second phase. The initial architecture can still take future expansion into consideration.

Four groups of website requirements: content, features, integrations and acceptance criteria.
Agree on the scope and verification methods before development begins.

6. Specify integrations and account access

If the project involves a CRM, payment provider, shipping service, inventory system, Telegram bot or other external service, name the specific systems. Establish whether the business already has accounts, which plans it uses and exactly what data needs to be exchanged. The word CRM alone does not define the scope of an integration.

In one project, submitting new enquiries to a CRM may be sufficient. Another project may need two-way synchronisation of statuses, contacts, products and inventory. The second scenario requires decisions about which system owns each data field, what happens if an update fails and how conflicting changes are resolved.

When planning online payments, confirm the chosen provider's eligibility requirements and how payment confirmation will be handled. The owner should create business accounts in their own name and provide the developer with appropriate technical access. Passwords, payment details and secret API keys should never be written into a broadly shared website brief.

7. Define SEO, performance and accessibility requirements

Technical SEO is best planned before development. Specify meaningful URLs, headings, editable metadata, internal links, indexability and a sitemap. When replacing an existing website, review old URLs and plan appropriate redirects. Technical preparation provides a basis for visibility in search engines, but does not guarantee a particular ranking for a query.

The mobile experience should not be treated as a smaller desktop layout. Check readability, menus, buttons, forms, checkout and the absence of unnecessary horizontal scrolling on agreed screen sizes. Performance requirements should consider actual pages, images, external integrations and hosting. We discuss the subject further in our website speed guide.

Accessibility should also be included from the planning stage. Clear form labels, suitable contrast, meaningful image alternatives and keyboard access to essential functionality make a website more usable. If a project requires verification against a particular accessibility standard, agree the target and testing procedure explicitly rather than assuming that a general requirement for accessibility defines every necessary test.

When defining performance goals, avoid requiring a single perfect score on every page under every possible network condition. Agree on representative pages, the measurement tools and conditions, and how changes to third-party services or content will be evaluated. This makes expectations more realistic and measurable.

8. Budget, timelines and scope changes

Share the planned budget and preferred launch date. This makes it easier to select a realistic initial scope. Cost depends on the number of templates, content volume, functionality, integrations and data preparation. Our website development cost guide describes the main factors in more detail.

The schedule depends on more than the developer. Time is required to prepare materials, approve the structure, obtain access to external services and conduct testing. Agree the project stages, responsible contacts and method for providing feedback. If several employees make decisions, consolidate their feedback instead of issuing conflicting instructions to the developer.

Distinguish corrections to agreed requirements from new requests. If a contact form is included in the original specification and the client later requests a complete appointment booking system, that represents additional scope. Assess its impact on cost and timing before implementing it. This approach protects both the client and the developer from unexpected work and misunderstandings.

9. Acceptance criteria and website handover

Before development begins, agree how the result will be checked. For a standard website, this might include opening all agreed pages, navigating the menu, sending an enquiry and verifying the mobile layout. A shop needs tests for its basket, payments, delivery, emails, discounts and order statuses. A successful test should have a clear expected outcome.

Clarify who will own the domain, hosting and external service accounts. On completion, the owner should receive the necessary administrative access, information about licences and guidance for routine operations. Where several employees manage the website, assign suitable roles and permissions instead of sharing one administrator password among everyone.

Also agree on maintenance arrangements: what counts as fixing an existing defect, what constitutes new work, who installs software updates, who manages backups and who responds to changes in third-party services. An owner should know how to manage the agreed aspects of the website independently when the development project ends.

10. A sample brief for a small business

Imagine a beauty studio planning a new website. The following answers provide an example of what the business owner could prepare before the first conversation with a developer. They do not constitute a complete technical specification but provide a basis for a meaningful initial estimate.

  • Business: a beauty studio with three specialists, working by appointment.
  • Goal: present services and prices, allow clients to book without messaging staff.
  • Structure: homepage, services, team, prices, contact and booking page.
  • Languages: two language versions, with translations provided by the client.
  • Features: select a service, specialist and time, confirm an appointment and notify the administrator.
  • Content: logo, photos and price list available; service descriptions need preparation.
  • Schedule: launch the basic website by the agreed date; online deposits can be added later.
  • Acceptance: check the mobile version, price editing and successful bookings for each specialist.

The developer can now clarify service duration, scheduling rules, notifications and data handling requirements, estimate the scope and propose a practical implementation. An ecommerce brief would similarly include product range, variants, delivery, payment and inventory sources. At CianBay Studio, we create business websites, corporate websites and WooCommerce stores according to the client's requirements.

Frequently asked questions

Do I need to know WordPress to prepare the brief?

No. Describe your goals, the actions users should be able to perform and the expected result. Specific technologies and extensions can be selected with the developer once the requirements have been established.

What if I do not have all the photos and written content yet?

Explain this before work begins. Agree who will prepare the missing materials, which ones are required for the initial phase and when they will be ready. This helps everyone plan the project realistically.

Can the specification change after development has started?

Yes, but agreed changes should be documented. Where they increase the project scope, agree their cost, schedule implications and acceptance criteria separately.

What a well-prepared website brief should deliver

A well-prepared website brief does not require programming knowledge. It explains why the website is needed, how visitors should use it and what an acceptable result looks like. The more concrete the initial information, the easier it becomes to agree the cost and timeline, allocate responsibilities and create a website that meets the business's real needs.

Sources and documentation

Originally published at CianBay Studio.

Disclosure: This article was prepared with AI assistance.

Top comments (0)