How to Brief a Web Designer: The Complete 2026 Guide for Sri Lankan Businesses

A web design project lives or dies in the first week. Not because of the designer's skill, the budget, or the platform — but because of how clearly the brief was written.

We've seen Sri Lankan businesses spend LKR 300,000+ on a website and end up with a beautiful product that solves the wrong problem, because nobody ever wrote down what the problem was. We've also seen LKR 80,000 projects deliver above expectations because the founder spent two hours on a tight, honest brief before sending it to three agencies.

This guide gives you exactly what to put in a web design brief in 2026, what to leave out, and a fill-in template you can use today. It works for any Sri Lankan agency, freelancer, or international team.

Why most briefs fail

Three patterns we see weekly:

1. The wishlist brief. Five pages listing every feature the founder has ever seen on a competitor's site. No prioritisation, no goal, no audience. The agency quotes high to cover its risk. The project bloats.
2. The "you're the expert" brief. A two-line WhatsApp message: "Need a website. How much?" The agency has nothing to scope from, so the quote is either a cookie-cutter package or a fishing-expedition meeting.
3. The aesthetic-only brief. Three Pinterest mood boards and zero business context. The designer makes something pretty that doesn't convert.

A good brief sits between all three. It's strategic enough to anchor business decisions, prescriptive enough to bound scope, and humble enough to let the designer do their job.

The 9 sections every web design brief needs

1. The business in one paragraph

What you do, who you sell to, and what makes you different. Not a marketing pitch — a description a journalist could use. If you can't write this in five sentences, the website project isn't the first problem to solve.

Example: "Wasana Drivers is a Colombo-based transport service offering long-distance airport transfers and full-day chauffeur hire. We serve business travellers and Sri Lankan diaspora visiting from Australia and the UK. Our differentiation is fixed-fare pricing in USD/AUD/GBP, English-speaking drivers, and same-day WhatsApp booking confirmation."

2. The single most important goal of the website

Not three goals. Not seven. One. Every design decision will be measured against this.

Common goals for Sri Lankan SMEs:

• Generate qualified enquiries (most service businesses)
• Sell products (ecommerce)
• Reduce support load (FAQs, self-serve booking)
• Win trust before a sales call (B2B, healthcare)
• Recruit (talent-heavy industries)

If the website needs to do more than one of these, rank them and pick a clear primary. The secondary goals get fewer pixels.

3. The audience — specific, not generic

"Small businesses in Sri Lanka" is not an audience. "Mid-tier hotels in Galle and Mirissa with 20–80 rooms, booking direct rather than through OTAs" is.

Include:

• Industry, scale, location
• Decision-maker (owner, CMO, IT manager, parent)
• Their context when they land on your site (Googling at 11pm? Comparing three quotes? Forwarded a link?)
• What would make them leave in 5 seconds

This single section determines tone, copy, layout, and the entire information hierarchy.

4. The pages you need (best guess is fine)

A rough page list lets the agency scope. You won't have the final structure — that comes after discovery — but list what you think today:

• Home
• About
• Services (one page or one per service?)
• Portfolio / case studies
• Blog / insights
• Contact
• Anything industry-specific (booking flow, member login, calculator)

If you're not sure, say "12–15 pages, structure to be agreed in discovery." Agencies prefer honesty to false precision.

5. Content — who's writing it, and is it ready?

This is the single biggest cause of delayed Sri Lankan web projects. The design ships, the agency waits four months for the founder to write the About page, and the launch slips into next quarter.

State plainly:

• Will the agency write the copy? (Most charge LKR 8,000–25,000 per page.)
• Do you have existing copy that needs editing?
• Are you supplying photography, or sourcing stock?
• Will you provide brand assets (logo, colours, fonts)?

If the answer to most of these is "we'll figure it out," budget for the agency to handle it. That's not a luxury — it's what keeps the project on schedule.

6. Design preferences (lightly)

Three to five websites you like, one or two you don't. One-line note on each. That's enough.

Like: figma.com — clean, no clutter, type-led

Like: linear.app — calm, confident, dark mode done well

Dislike: [competitor.lk] — feels generic, every page looks the same

Don't dictate colours, fonts, or layout. You hired the designer for that. Give them the destination; let them choose the road.

7. Technical requirements

The boring stuff that determines half the quote:

• Platform preference? WordPress, Next.js, Webflow, Shopify, custom? If you don't know, write "agency to recommend."
• Integrations? WhatsApp business, payment gateway (PayHere, Stripe, Onepay), booking system (Calendly, custom), CRM (HubSpot, Zoho), analytics (GA4, Plausible).
• Multilingual? English-only, English + Sinhala, English + Tamil + Sinhala?
• Existing site? Migration of content, redirects, SEO history to preserve?
• Hosting? Own preference, or include in the quote?

8. Budget and timeline — both ranges

The two questions every agency dreads asking and every founder dreads answering. Skip both and you'll get either a wildly inflated quote or a lowball that bleeds in scope creep.

Budget: Give a range. "LKR 250,000–400,000" tells the agency how to scope. "We'll see what you quote" tells them to test the ceiling.

Timeline: State the launch goal and what's driving it. "Live by 1 October — board presentation 5 October" is useful. "ASAP" is not.

For typical Sri Lankan projects in 2026:

• LKR 80,000–150,000: 4–6 weeks, template-led, content-ready
• LKR 200,000–400,000: 8–12 weeks, custom design, light content support
• LKR 500,000+: 12–20 weeks, custom design + dev, content production, integrations

For more detail on what each tier includes, see our website cost Sri Lanka 2026 guide.

9. Success metrics (post-launch)

How will you know it worked? Three months after launch, what number tells you the website is doing its job?

• "20+ qualified enquiries per month via the contact form" (most service businesses)
• "5% conversion on the pricing page" (SaaS or productised service)
• "Reduce inbound 'what do you charge' calls by 50%" (transparent-pricing play)

Agencies that take this seriously will architect for that number from day one. Agencies that brush it off are selling design as decoration.

The 1-page brief template (copy this)

PROJECT BRIEF — [COMPANY NAME]
Date: [DD MMM YYYY]

1. THE BUSINESS
[5 sentences max. What you do, who for, why you're different.]

2. PRIMARY GOAL OF THE WEBSITE
[One sentence. Pick one outcome.]

3. AUDIENCE
[Industry, scale, location, decision-maker, context.]

4. PAGES (BEST GUESS)
[Bullet list — 5–15 pages.]

5. CONTENT
- Copy: [who writes it]
- Images: [supplied / stock / shoot needed]
- Brand assets: [available / to design]

6. DESIGN REFERENCES
Like: [site] — [why]
Like: [site] — [why]
Like: [site] — [why]
Avoid: [site] — [why]

7. TECHNICAL
- Platform: [WordPress / Next.js / open]
- Integrations: [list]
- Languages: [English / Sinhala / Tamil]
- Existing site: [yes/no, migration needed?]

8. BUDGET + TIMELINE
- Budget range: LKR [X – Y]
- Launch goal: [date]
- What's driving the date: [reason]

9. SUCCESS METRIC
[The one number that tells you it worked.]

Three quarters of an A4 page. Two hours of your time. The most leveraged work you'll do on the whole project.

What to leave out of the brief

Just as important as what goes in:

• Specific design choices. No "use teal and Montserrat." That's the designer's call after they've read your business and audience sections.
• The full feature list. "Like Airbnb but for catering" hides 200 features. Pick the five that matter for launch; everything else is phase 2.
• A 40-page strategy deck. If you wrote one, summarise it on page 1 of the brief. The agency will read the brief; they won't read the deck.
• Your company history. Unless you've been around long enough that it matters for trust, skip it.
• Internal politics. "The CEO wants this, but the marketing director thinks…" — sort this out before you brief.

When to brief multiple agencies

If you're comparing three quotes, send all three the same brief on the same day. Vary nothing. Then compare:

• Did they actually read it? (Look for specific references in the proposal.)
• Did they push back on anything? (A good agency will challenge weak parts of the brief.)
• Did they scope what you asked for, or sell you their package?

Agencies that answer questions you didn't ask are selling a process. Agencies that scope precisely to your brief are partners. For more on how to evaluate the response, see our guide on questions to ask a web development agency.

After you send the brief

Expect three things from a good agency within 5–7 days:

1. A 30–45 minute discovery call to fill the gaps your brief left open. (Every brief leaves gaps. That's fine.)
2. A written proposal with itemised scope, milestones, payment terms, and assumptions. Anything verbal-only is a red flag.
3. A clear next step. If a contract is needed, when. If a deposit is required, how much. If references are available, who.

If the response to your brief is a generic PDF and a payment link, send it back. The brief deserves better — and so does your project.

The honest truth about briefs

A perfect brief doesn't exist. The goal isn't to anticipate every decision the designer will need to make over the next 12 weeks. The goal is to give them enough to start, in the right direction, without burning a week on assumptions.

Two hours on this document saves four weeks of revisions later. It's the single highest-leverage piece of work you'll do on the entire project — and it doesn't require a designer to help you write it.

Once you have the brief, the rest of the project becomes a conversation between two people who already agree on the destination. That's the version that ships on time, on budget, and with the result you actually wanted.