How to Create a Website Project Brief (With a Structure You Can Copy)

Without a brief, every quotation you receive answers a slightly different question. One vendor prices five pages, another prices twelve, a third includes content writing and the fourth assumes you will supply everything. You then compare four numbers that are not comparable and, reasonably enough, pick the lowest.
A brief takes a working day to write and changes that dynamic entirely. It also forces you to make decisions early, while they are still free.
What a brief is for, and what it is not
A brief is a commercial document written before you engage anyone. It sits between your internal intention and a vendor's proposal.
A brief is:
- A statement of business context and objectives.
- A list of what the site must contain and do.
- A declaration of what you will supply, what you expect the vendor to supply, and by when.
- A budget band and a deadline.
A brief is not:
- A design specification. Do not dictate colours, layouts or the exact position of a button. You are buying professional judgement.
- A technical specification. Unless you have a genuine constraint, let the vendor propose the platform and justify it.
- A contract. The brief informs the proposal; the proposal and contract carry the legally binding scope.
Keep those boundaries and your brief will attract good vendors. Blur them and you will either receive inflated quotations or discourage the firms whose judgement you were trying to buy.
The ten sections every website brief needs
| Section | What it answers | Typical length |
|---|---|---|
| 1. About the business | Who you are, what you sell, where you operate | One paragraph |
| 2. The problem | Why you are doing this now | One paragraph |
| 3. Objectives | What the site must achieve, with measures | Three to five bullets |
| 4. Audiences | Who will use it and what they want | Two to four short profiles |
| 5. Scope of pages | The sitemap you expect | A list or simple table |
| 6. Features and functionality | What the site must do beyond displaying content | Bulleted list, marked must or nice |
| 7. Content and assets | What you will supply and what you need help with | A table with owners and dates |
| 8. Technical and integration needs | Payments, bookings, CRM, analytics, hosting constraints | Bulleted list |
| 9. Budget and timeline | Your band and your deadline, with the reason for the deadline | Two lines |
| 10. Evaluation and next steps | How you will decide, and by when | Three bullets |
Two optional sections earn their place often enough to mention: references, listing three sites you find effective and one sentence on why, and out of scope, listing what you are explicitly not asking for. The out-of-scope list prevents more disputes than any other paragraph in the document.
How much detail to give, and where to stop
The useful rule: be precise about outcomes and content, and loose about execution.
Be precise about:
- The number and names of pages you expect.
- Every feature that involves money, data capture or a third-party system.
- Who supplies text, photographs, logos and product data.
- The deadline and what depends on it.
- Languages, locations and any legal or regulatory content you must display.
Stay loose about:
- Visual design direction beyond your brand guidelines.
- Platform choice, unless you have a real constraint such as an existing system or an in-house team.
- The exact structure of a page. Say "the service page must let a visitor request a quotation without leaving the page", not "put a form in the right sidebar".
A brief that is too detailed in the wrong places signals a difficult client and raises your quotations. A brief that is too vague produces proposals you cannot compare.
Writing the goals section so it is measurable
Most briefs say "we want a modern, professional website". No vendor can price or design against that. Convert intention into measurable outcomes.
Weak: "We want more customers."
Better: "We want qualified enquiries to arrive through a form with enough detail that our sales team can respond with a price, reducing the back-and-forth that currently happens over three WhatsApp messages."
Weak: "We want to look credible."
Better: "Corporate procurement officers who receive our profile by email should be able to confirm our registration details, sector experience and past work within a minute of landing on the site."
Three to five goals of that kind will shape the entire project, including the pages you need, the content you must write and the features that matter. Add a measure for each where possible: enquiry volume, enquiry quality, time to answer a common question, orders processed without a phone call.
Defining pages and features without designing the site
List the pages you believe you need, and mark which are essential. Vendors will suggest additions and removals, which is a good sign.
| Page | Purpose | Must have |
|---|---|---|
| Home | Position the business, route visitors to services | Yes |
| About | Registration details, team, credibility | Yes |
| Service pages, one per service | Explain the offer, answer objections, capture enquiries | Yes, four pages |
| Work or portfolio | Proof | Yes |
| Pricing or how we work | Reduce unqualified enquiries | Preferred |
| Contact | Address with landmark, map, WhatsApp, form | Yes |
| Insights or blog | Search visibility over time | Nice to have |
| Policy pages | Privacy notice and terms | Yes |
Then list functionality separately and mark each item must-have, should-have or nice-to-have:
- Enquiry form with email and WhatsApp notification. Must.
- Click-to-chat WhatsApp button on every page. Must.
- Online payment for consultation deposits. Should.
- Appointment booking with calendar sync. Should.
- Newsletter sign-up. Nice.
- Multi-language support. Nice.
- Admin area where staff can update content without a developer. Must.
That three-level marking is the single most useful thing in a brief. It lets a vendor quote a base scope and options, which is exactly what you need when budget is tight.
Saying what you will supply and when
Website projects in Nigeria stall on content more than on code. Settle this in the brief.
| Item | Supplied by | Ready by |
|---|---|---|
| Logo and brand files | Client | Before kickoff |
| Page text | To be quoted by vendor | Week 2 |
| Team photographs | Client, professional shoot needed | Week 3 |
| Product images and descriptions | Client | Week 2 |
| Company registration details | Client | Week 1 |
| Domain and hosting access | Client, currently with former developer | Week 1 |
| Privacy notice and terms | Vendor drafts, client's adviser reviews | Week 4 |
| Payment gateway account | Client to open with provider | Week 3 |
If you are not sure you can write the content, say so and ask vendors to price it as an option. Copywriting is a real line item, commonly the difference between a site that launches in six weeks and one that sits unfinished for six months.
Budget and timeline: why you should state a band
Many business owners withhold their budget, believing they will be quoted whatever they reveal. In practice, withholding it produces proposals aimed at the wrong scope and wastes everyone's time.
State a band, not a number. For example: "Our budget for the build is in the ₦800,000 to ₦1,500,000 range, with a separate annual allowance for hosting and maintenance."
Indicative 2026 ranges for Nigerian websites; actual quotes vary with scope, vendor and exchange rate:
| Type of site | Indicative build cost |
|---|---|
| Single landing page | ₦80,000–₦400,000 |
| Basic business website, five to eight pages | ₦150,000–₦500,000 |
| Professional custom-designed business website | ₦500,000–₦2,500,000 |
| E-commerce website | ₦400,000–₦3,500,000+ |
| Custom web application | ₦1,500,000–₦10,000,000+ |
| Annual hosting | ₦20,000–₦120,000 shared; ₦150,000–₦800,000+ for applications |
| Maintenance | ₦20,000–₦150,000 per month |
For the timeline, give the date and the reason. "Live by 15 March because our trade exhibition opens on 20 March" tells a vendor far more than "as soon as possible", and lets them tell you honestly whether it is achievable.
Example (hypothetical): brief extract for a Lagos law firm
Example (hypothetical). A six-partner commercial law firm in Victoria Island needs to replace a site built in 2018.
Problem: Corporate clients research the firm before responding to a proposal. The current site does not list practice areas properly, is slow on mobile, and cannot be updated without contacting a developer who no longer responds.
Objectives:
- A prospective corporate client can identify the relevant practice area and the partner leading it within 30 seconds.
- Recruitment candidates can find and apply for openings without emailing the office manager.
- The firm's own staff can publish an article without developer involvement.
- The site loads quickly on a mid-range phone over mobile data.
Scope: Home, firm profile, seven practice-area pages, partner profiles, insights section, careers with an application form, contact.
Must-have features: Content management access for two staff; enquiry form routed to a shared inbox; searchable insights; downloadable firm profile in PDF.
Out of scope: Client portal, document management, online payment.
Supplied by the firm: Partner biographies, practice-area descriptions, photographs. Needed from the vendor: editing and structuring of text, plus a privacy notice draft for the firm's own review.
Budget band: ₦1,200,000–₦2,000,000 for the build, separate annual maintenance.
Deadline: Live before the firm's annual client seminar in October.
Notice that no colour, font or layout is mentioned, and every feature is testable.
What changes for Nigerian businesses
Domain and hosting ownership. State clearly in the brief who currently controls the domain, hosting and email. A large share of Nigerian website projects are delayed because access sits with a former developer or a personal Gmail account. Ask vendors to include transfer and handover explicitly.
Mobile and data weight. Most of your visitors will arrive on Android phones over mobile data. Put a performance expectation in the brief, such as "pages must remain usable on a 3G connection", and ask how the vendor will achieve it.
WhatsApp as the conversion channel. Specify how the site should hand a visitor to WhatsApp, and whether the message should be pre-filled with context. This is a real requirement in Nigeria, not an afterthought.
Payments. If you will take money, name the providers you intend to use, such as Paystack or Flutterwave, and say whether you already hold an account. Gateway onboarding takes time and needs your CAC and bank details.
Local search. Ask for a sitemap structure that supports the locations and services people actually search for, and for the site's business details to match your Google Business Profile exactly.
Data protection. If the site collects personal data, say so in the brief and ask the vendor how consent, storage and retention will be handled. Confirm your obligations under the Nigeria Data Protection Act 2023 with the Nigeria Data Protection Commission or a qualified adviser.
Content in your own voice. Nigerian buyers respond to specifics: locations served, delivery times, registration details, real photographs of your premises. Say in the brief that generic stock imagery is not acceptable.
How to send the brief and compare responses
- Shortlist three to five vendors whose published work resembles the kind of site you need.
- Send the identical brief to all of them on the same day, with a response deadline of seven to ten working days.
- Ask for the same structure back: understanding of the brief, proposed scope, what is excluded, timeline with milestones, price broken into build, content, and first-year running costs, plus payment schedule.
- Hold one clarification call each. Answer every question, and circulate any material answer to all vendors so the playing field stays level.
- Compare on a single sheet: scope covered, exclusions, timeline, total first-year cost, ownership and handover terms, maintenance offer.
- Interrogate the outliers. A quotation far below the others usually excludes content, revisions or post-launch support. Ask which.
- Check references and live sites. Ask for two sites the vendor built that are still running, and look at them on your own phone.
Mistakes to avoid
- Writing the brief after you have chosen a vendor. The brief's main value is comparability, which is lost once you have decided.
- Hiding the budget. It produces proposals for the wrong scope and wastes weeks.
- Specifying design instead of outcomes. You will get exactly what you described and still be unhappy.
- Leaving content unassigned. Unowned content is the leading cause of stalled website projects.
- Omitting the out-of-scope list. Everything not excluded will be assumed by somebody.
- No named decision-maker. If four people must approve every page, say so and expect a longer timeline.
- Forgetting running costs. Ask every vendor for first-year hosting, maintenance and support costs in the same format.
- Sending different briefs to different vendors. Then the comparison means nothing.
Website brief checklist
- Business context written in one paragraph
- Three to five measurable objectives
- Audiences described with what each needs
- Expected sitemap listed
- Features marked must, should or nice
- Content and asset responsibilities assigned with dates
- Integrations and third-party accounts named
- Domain, hosting and email access situation stated
- Budget band and timeline with reason
- Out-of-scope list written
- Ownership, source files and handover expectations stated
- Decision-maker and approval process named
- Evaluation criteria and response deadline included
Conclusion
A website project brief is the cheapest risk control available to a Nigerian business commissioning a site. It takes a day to write, it forces the decisions that would otherwise surface expensively in week six, and it converts four incomparable quotations into a genuine choice.
Be precise about objectives, pages, features and who supplies content. Be generous about design and technical judgement. State a budget band, state your deadline and say what is out of scope. Then send the same document to every vendor on the same day, and compare like with like.
If you would like a second opinion on a draft brief, or a realistic view of what your scope should cost and how long it should take, Linestech is happy to review it before you invite quotations.
Frequently asked questions
How long should a website brief be?
Two to six pages for most Nigerian SME projects. A landing page may need one page; a complex e-commerce or membership site may justify eight to ten. Length is not the measure of quality. Clarity about objectives, scope, content ownership and budget band matters far more than volume.
Should I write the brief myself or ask an agency to write it?
Write the first version yourself, because only your business knows the objectives, content position and internal constraints. It is reasonable to ask a vendor to help structure it, but a brief written entirely by the firm that will quote on it tends to describe the work that firm prefers to do.
What if I do not know what features I need?
Describe the outcomes instead. "Customers should be able to book and pay a deposit for a consultation" is a requirement; the vendor decides whether that means a booking plugin, a custom module or a third-party service. Mark it should-have so you can see the price of the option before committing.
Is a brief necessary for a small five-page website?
Yes, though it can be short. Even a one-page brief that names the pages, the enquiry mechanism, who writes the content and the budget band will improve the quotations you receive and prevent the most common disputes about revisions and scope.
How do I stop vendors from quoting on different scopes?
Give every vendor the identical document, ask for responses in a fixed structure, list exclusions explicitly, and require a line for first-year running costs. Then build a single comparison sheet. If one proposal is missing a section, ask for it before comparing rather than filling the gap with assumptions.
Should the brief include my existing website's problems?
Include them briefly, framed as business problems rather than complaints. "The current site cannot be updated by staff" and "product pages do not appear in search" are useful. Long lists of grievances about a previous developer consume space that would be better spent on objectives.
What do I do if all the quotations exceed my budget?
Use your must, should and nice markings to cut deliberately. Reduce scope rather than quality: fewer pages built properly beats twenty pages built carelessly. Ask vendors to phase the work, delivering the essential pages first and adding the rest once the site is earning its keep.
Does the brief become part of the contract?
Not automatically, and it should not be relied on as a contract. The vendor's proposal, refined into a scope of work, is what should be attached to the agreement. Make sure anything from the brief that matters to you appears in that scope, including ownership, handover and post-launch support terms.
Sources and further reading
Figures, platform rules and regulations change. These are the primary references behind this article and the places to check before you act on it.


