The one-page brief: deciding what a website must do before anyone designs it
The short answer
A one-page website brief is a single signed document that states who the site is for, what it must get them to do, which pages that needs, what will not be built, and how success will be checked. It is written after a short diagnosis and signed before any design starts, so every later decision has something to be judged against.
On this page
- The short answer
- What is a one-page website brief?
- Why should the brief come before design?
- What goes on the one page?
- How do Diagnose and Decide produce the brief?
- How does the brief change for India, the UAE and the UK?
- What are the most common mistakes in a website brief?
- What happens after the brief is signed?
- What to do next
- What to take away
- Questions, answered
The most expensive part of a website project is usually not design or development. It is the decision nobody made at the start, which then gets made five times during the build, by different people, in different review rounds.
The fix is boring and it works: write the decisions down on one page and sign them before anyone opens a design tool. We call it the one-page brief.
What is a one-page website brief?
A one-page website brief is a single signed document that records the decisions a website depends on: who it is for, what it must get them to do, which pages that needs, what will not be built, which technology it runs on, and how success will be checked. It is written after a diagnosis and signed before design starts.
It is not a creative brief full of adjectives, and it is not a requirements document listing every feature. It sits between the two. It is short enough to read in five minutes and specific enough that a designer, a developer and a copywriter would build roughly the same thing from it.
Why should the brief come before design?
Because design makes decisions visible, and visible decisions are expensive to reverse. Once a home page layout exists, every stakeholder reacts to it, and the conversation drifts from "what is this page for" to "I prefer blue". A signed brief gives every reaction something to be measured against.
This is the passage we share with clients who want to see designs first. A design shown before the decisions are made is a guess presented as a proposal. People respond to what they can see: colours, photographs, the size of a headline. They cannot respond to what is missing, such as the fee question the page never answers or the WhatsApp button that should have been the main action. So review rounds fill up with taste, and the real gaps surface late, after code is written. When the brief is signed first, the first design review starts with a different question: does this layout do the job we agreed? That question has a right answer. It also shortens the build, because the designer is solving a stated problem rather than trying to guess which unstated one matters most.
What goes on the one page?
Eight short sections, each one a decision rather than a description. If any section takes more than a few lines, the decision behind it is probably not made yet, and that is useful to discover before money is spent on design.
The one-page brief, section by section
- Who it is for: the main reader and the second one
- The problem: what the current site or situation costs you
- The primary action: the one thing a buyer should do
- The pages: each with a one-line job
- The proof: real work, prices, people and process you can show
- What we will not build, and why
- The stack: platform, CMS and integrations
- How we will know: the signals checked after launch
A few notes on the sections people find hardest:
- Who it is for. Name a person, not a segment. "A parent in Hyderabad comparing CBSE schools within a short commute" is useful. "Families" is not.
- The pages. Each page gets a one-line job, the habit described in why every page should have a job. Pages that share a job get merged on paper, where it is cheap.
- What we will not build. A blog nobody will write for, a careers section with no vacancies, a chatbot with nothing to answer from. Writing these down is how a fixed scope stays fixed.
- The stack. One line, with the reason. Our guide to choosing a tech stack covers how we make that choice.
How do Diagnose and Decide produce the brief?
The brief is the output of two steps. Diagnose gathers evidence: your site, your search data, your competitors and how enquiries are handled today. Decide turns that evidence into choices on one page, which you sign. Nothing about the build starts until both are done.
How the brief gets written
- Discovery call: Goals, buyers and constraints
- Site and search audit: What exists and what it ranks for
- Competitor read: What buyers compare you against
- Enquiry review: Who answers, how fast, on which channel
- The one-page brief: Decisions written down and signed
Diagnose is where most of the useful surprises come from. The enquiry review in particular: we ask who actually answers a new enquiry, on which channel and how long it takes. In India and the UAE the honest answer is often "on someone's personal WhatsApp, when they see it", which changes what the website's contact page should do. The search audit shows which pages already earn visits, so they are protected rather than accidentally removed.
Decide is a working session, not a presentation. We draft the page, you challenge it, we cut. The final version names an owner for each open item. You can see how this fits our wider process on the studio page.
How does the brief change for India, the UAE and the UK?
The eight sections stay the same; what goes in them shifts by market. The channel buyers use, the languages they expect and the legal basics differ, and each of those is a decision that belongs on the brief rather than one discovered during the build.
- India, including Hyderabad, Mumbai and Pune. Decide early whether WhatsApp is the primary action, and whether any pages need Hindi, Telugu or Marathi. Note the obligations under the Digital Personal Data Protection Act, 2023 for any forms, and take legal advice on the detail.
- UAE and Dubai. Decide whether Arabic is a full version of the site or a set of key pages, because right-to-left layouts affect design from the first sketch. Note which trust signals you can show, such as trade licence details and a physical address. Personal data rules sit under Federal Decree-Law No. 45 of 2021, with separate regimes in DIFC and ADGM.
- UK and London. Put accessibility and privacy on the brief from the start: a target such as WCAG 2.2 AA, a cookie approach that matches what the site will actually load, and a privacy notice under UK GDPR and the Data Protection Act 2018.
What are the most common mistakes in a website brief?
The common mistakes are listing everything instead of choosing, describing the brand instead of the buyer, and leaving out what will not be built. Each one feels harmless on paper and turns expensive during the build, because the missing decision gets made later by whoever is in the review.
The patterns we see most often:
- Three primary actions. "Call us, WhatsApp us, download the brochure and book a visit" is four actions and no priority. Pick one per audience.
- Adjectives as goals. "Modern, premium, trustworthy" cannot be checked. "A parent can find the fee for Grade 6 in two clicks" can.
- No owner. An open question without a named owner stays open until launch week.
- Copy left for later. If nobody is named to write the words, design will be built around placeholder text that never fits the real thing.
What happens after the brief is signed?
The brief becomes the reference for every later decision. The sitemap and copy plan expand it, design interprets it, and each draft is reviewed against it through one review link. Change requests are judged by one question: does this help the page do its agreed job?
On our projects, requests and approvals live in a client portal rather than an inbox, so the trail from brief to launch is visible. The reasoning is covered in why every website request should be logged. After launch, the "how we will know" section becomes the monthly check: are the pages producing the signals we agreed?
A concrete example of a brief decision showing up in a finished site: on the Chanakya School of Modern Management site, fees are published in a table and the admissions process is set out step by step before the counselling form. That is what a "proof" line and a "primary action" line look like once they are built.
What to do next
Try writing your own brief before you talk to any agency, including us. Take one sheet of paper and fill in the eight sections. Where you get stuck is where the project's real risk is. Bring that sheet to a call; it will make the conversation shorter and the plan better. Our services all begin with this step, and you can book a call to start.
What to take away
- Diagnose before you decide: read the site, the search data, the competitors and the enquiries first.
- Fit the brief on one page. If it does not fit, the decisions are not made yet.
- Write down what you will not build. It is the line that protects budget and timeline.
- Sign the brief before design starts and judge every change request against it.
Built on Intent studio. A founder-led studio in India that plans and builds websites, search and AI visibility, and AI systems for businesses in India, the UAE and the UK. Reviewed by [Founder name], founder. We do not publish invented numbers; where a figure appears, its source is named in the sentence.
How the studio works
