
Ready for a better website?
Serious about growing your business online?
Describe the customer task and business problem before listing features or visual preferences.
Separate confirmed requirements, assumptions and questions so agencies can price the same underlying work.
Inventory existing pages, content and connected systems, with an owner for each missing input.
Define acceptance through observable tasks, including enquiry delivery, mobile use and editing.
Ask proposals to explain exclusions, dependencies and ongoing costs alongside the build price.
Three agencies can receive the same request for a new website and price three different projects. One assumes you will supply finished copy. Another includes interviews and writing. A third allows for a booking integration that the others have treated as a link.
A useful website redesign brief makes those differences visible before you choose a partner. It explains the business problem, provides evidence, and identifies the decisions the proposal must resolve. You do not need to design every page first. You do need to say who the website serves, what must work, and who can approve the result.
Start With a Problem You Can Explain
“Make it modern” tells a designer something about taste. It does little to explain why the project matters. Start with a short description of what customers struggle to understand or do today.
A hypothetical kitchen company might write: homeowners cannot tell whether we supply cabinets only or manage installation, and our sales team repeatedly clarifies that distinction before discussing a project. That is a useful starting point. The redesign can explore how service descriptions, project evidence and the enquiry journey explain the scope.
Keep the observation separate from the proposed fix. “Visitors need clearer installation information” is an observation to investigate. “We need a five-step calculator” is a proposed solution with its own cost and maintenance implications. A simpler page or better form may meet the need.
The GOV.UK discovery guidance recommends understanding the problem, users and constraints before committing to a solution. That principle is useful here, although its government delivery process is not a required timetable for a small-business redesign.
Write down what you know and how you know it. Customer questions, support messages and sales notes can support a brief. A personal impression can be included too, but label it as an assumption. Avoid turning an untested explanation for low enquiries into the project's only objective.
Describe the Customer and the Next Action
A website aimed at homeowners comparing renovation options has a different job from one aimed at procurement teams checking supplier capability. Describe the decision your main customer is making, rather than supplying a broad demographic profile.
Include the services you most want to sell, the locations you genuinely serve, and the projects you cannot take on. Explain whether a visitor should request a quote, book an introductory call, send drawings, or first review a detailed service page. If several actions matter, identify the primary one and explain the others.
For example, a consultancy may need an initial conversation before it can estimate a project. Asking for a fixed-price purchase flow would misrepresent that process. A contractor might need a location and project description to assess fit, while detailed measurements can wait until the enquiry is reviewed.
Then describe what happens after the click. Who receives the request? Who responds? What information lets them decide whether the project is suitable? The brief should connect the public website to that real working process. A successful submission message alone does not prove an enquiry reaches the right person.
Set a measurement baseline where evidence exists. Record qualified enquiries and the team's definition of qualified, alongside the date range and traffic source limitations. If you have no reliable baseline, ask for measurement setup and a later review. Do not invent a conversion target just to make the brief appear precise.
Inventory Pages and Content Before Counting Screens

A proposed ten-page website can mean ten fully written pages or ten empty layouts. Give each page or page type a purpose, content status and owner. The inventory is more useful than a page count by itself.
Item | Decision to record | Input or owner needed |
|---|---|---|
Core service page | Keep, rewrite, combine or create | Service expert confirms scope and exclusions |
Project collection | Which projects have enough usable evidence? | Named person supplies approved images and facts |
Location content | Which areas need distinct information? | Operations confirms coverage and local details |
Articles and downloads | Which existing assets remain useful? | Content owner reviews accuracy and destination |
Contact journey | What should happen after submission? | Person responsible for responding to enquiries |
Include public URLs for existing content. Mark material that is outdated, duplicated or still earning useful attention. A redesign should not quietly remove an important answer just because it does not fit the first visual concept.
Ask whether repeated content will use a CMS template and how much population is included. Designing a project template, importing forty projects and editing forty project stories are different pieces of work. Identify them separately in the brief and proposal.
You do not need final prose for every page before contacting an agency. You should know which facts are available, who can provide missing material and whether you want writing included. Treat photography, permissions, diagrams and downloads as deliverables too. An attractive empty frame cannot solve a missing content decision.
Name the Systems That Must Keep Working
List the website's connections in plain language. Include forms, scheduling, CRM, payments, newsletter subscriptions, analytics and any protected client area. For each connection, describe the intended outcome and identify the account owner. Do not paste passwords or private customer records into a proposal brief.
“Connect our calendar” is incomplete. Does it mean opening an existing booking page, showing available slots, creating appointments, sending reminders, or managing cancellation? Which account controls availability? What should happen if the connection fails? Those answers change the scope substantially.
Separate features already working from features you hope to add. A provider should be able to test or investigate an existing integration before promising to preserve it. If access is not available yet, the proposal should identify that dependency and explain how the estimate may change after inspection.
Use a small requirement record for each important flow:
Trigger: A visitor submits a consultation request.
Destination: The request appears in the team's agreed workspace.
Acknowledgement: The visitor receives the agreed confirmation.
Failure handling: The team can identify and resolve a delivery failure.
Owner: A named person checks the flow after launch and when connected accounts change.
This is a proposed requirement pattern, not a claim that your current tools support every step. Ask the agency to state what is native, what needs another service, and what requires custom development. Include recurring fees and account responsibilities in that answer.
Define What Must Be Preserved at Launch
Treat existing URLs, search visibility and customer access as project inputs. Give the agency access to the relevant evidence through appropriate account invitations when needed. The initial brief can identify the accounts and owners without distributing credentials.
Where URLs change, ask who inventories the old addresses, decides their new destinations and checks redirects. Google's site-move documentation describes preparation, URL mapping, redirects and monitoring. It also cautions that rankings can fluctuate during a move. A proposal should explain the work and checks, rather than promise that traffic cannot change.
Record constraints around the launch itself. Perhaps enquiries must continue during the switch, an advertising campaign uses a particular landing page, or a downloadable specification is linked from printed material. A small business can have important dependencies that do not appear in its main navigation.
Keep this part of the brief focused on responsibility: who approves the switch, who can change domain settings, who checks critical paths, and who handles problems afterward. For the broader implementation sequence, our website redesign practices guide covers protecting useful existing work while improving the site.
Turn Quality Expectations Into Acceptance Tasks
Words such as premium, intuitive and fast can start a conversation, but they are difficult to use as final acceptance criteria. Pair the intended quality with a task someone can actually perform.
Instead of asking for an easy-to-edit website, specify that the responsible team member should be able to add a project with a title, image, summary and service link without changing the layout. Ask for that task to be demonstrated with the actual editing permissions the team will use.
Instead of saying mobile-friendly, identify the main customer journey to check on a narrow screen: find the right service, read the relevant evidence and submit an enquiry without clipped content. Include keyboard interaction and visible focus when agreeing navigation and form testing.
W3C's accessibility planning resources place accessibility within project planning and responsibilities, including the involvement of users. Specify the standard and evaluation scope with your provider where relevant. Neither this brief nor an automated scan establishes legal compliance or guarantees that every accessibility need has been addressed.
For performance, ask which page types and conditions will be measured, how third-party tools affect the result, and what happens when a test misses the agreed target. A single score from an empty homepage is not a useful acceptance test for a media-heavy project page.
Assign an approver to each category. The owner may approve commercial content while a service specialist verifies technical facts. One person should consolidate feedback, so the delivery team receives an agreed decision rather than contradictory comments from separate conversations.
Give the Budget and Deadline Some Context
If you can share an investment range, explain what it must cover. Separate the initial build from platform fees, subscriptions, content production and ongoing support. If you do not know the range yet, ask for a scoped discovery or options with clear trade-offs rather than a precise quote based on missing requirements.
Tell the agency what makes the deadline real. A booked event, expiring contract or new service launch creates a different constraint from a preferred date. Include your own team's availability for interviews, content review and approvals. An ambitious delivery date is not credible if essential inputs arrive after it.
Ask for a minimum useful launch and a later phase where that distinction makes sense. For example, the first release might include verified service content and a reliable enquiry journey, with a larger project archive added once the evidence is prepared. The first release still needs to work properly; phasing should reduce scope, not remove essential checks.
The trade-off should be visible in the proposal. If a provider recommends a smaller first release, ask what is deferred, why, and how it will connect to the initial build. Compare that with a larger quote on the same basis before concluding that one provider is cheaper.
Copy This Brief Into Your Working Document
Use these prompts as a starting structure. Keep the main brief short enough for a decision-maker to read, and attach inventories or evidence separately. Mark unanswered questions rather than filling the gaps with guesses.
Business and offer: What do we sell, to whom, and in which areas? Which work is outside our scope?
Current problem: What is difficult for customers or the team today? What evidence supports that observation?
Primary journey: What should a visitor understand and do? What happens inside the business afterward?
Success and baseline: Which outcomes will we measure, over what period, and who will review them?
Content inventory: Which pages, projects and resources exist? What stays, changes or needs creating?
Content responsibilities: Who provides facts, writing, images and permissions? What should the agency produce?
Connected systems: Which tools must work, which accounts own them, and what still needs investigation?
Design references: Which examples help explain our preferences, and what specifically do we want to learn from each?
Acceptance and handover: Which customer and editor tasks must pass? Who approves each area?
Commercial constraints: What is the investment range, what does it include, and what makes the deadline important?
Open questions: Which assumptions should the proposal challenge? Which decisions require discovery?
When adding visual references, describe the reason for each one. You might value clear service comparisons on one site and restrained motion on another. That gives a designer a direction to interpret without asking for a copy of someone else's work. Include any existing brand rules and explain whether changing them is in scope.
Compare the Responses Against the Same Brief
Ask each provider to return a scope that distinguishes included work, optional work, exclusions and dependencies. Read the assumptions before comparing the total price. If one quote includes writing and another requires finished copy, you are not yet comparing equivalent offers.
Look for a response to the difficult parts of your brief. Does the proposal address a complicated enquiry flow, identify missing project evidence, or explain who will review redirects? A polished presentation that skips those questions leaves the underlying uncertainty with you.
Create a decision log once you choose a partner. Record changes to the brief, who approved them, and any effect on cost or timing. Keep one current version. A decision about a new feature made in a call should not remain disconnected from the agreed scope.
Handover also belongs in the initial agreement. Our Framer website handover checklist explains the ownership and editing questions to resolve. Knowing who will maintain the website helps you choose an appropriate structure before it is built.
Next steps
Prepare the customer journey, content inventory and open questions before requesting a final price. Those three inputs give an agency something concrete to assess and give you a better basis for choosing its response.
If you need a clearer starting point, request a website audit. We can use the findings as a basis for a conversation about the work your website actually needs. You can also explore our Framer website design service when you are ready to discuss the brief.



