Skip to content
← Blog

White Label Fundamentals · 5 min read

How to brief a white label web build (a template)

What to send a white label studio before a WordPress or Shopify build starts, so the quote is accurate and the first draft is close to right.

November 4, 2026

How to brief a white label web build (a template)

Key takeaways

  • Most late, over-budget web projects were under-briefed; an hour of writing saves days.
  • A good brief covers a single contact, the business, design direction, content, features, access, dates, confidentiality and exclusions.
  • Late content is the most common cause of late launches, so put its delivery date in the brief.
  • Flag unknowns rather than guessing; unknown is fine, hidden is the problem.

Most late, over-budget web projects were under-briefed. The studio guessed, the agency assumed, and the gap showed up in revision three. A good brief takes an hour to write and saves days. This is the one we would like to receive.

1. One point of contact

Name the person at your agency who answers questions and decides. Feedback from five people with five opinions is the quickest way to stall a build. Say who has final say.

2. The business and the audience

Two or three sentences: what the client sells, to whom, and what a successful website does for them. A phone call, a booking, an online sale. Skip adjectives like “modern”; describe the decision the visitor is making.

Woman using a laptop at a table during an online meeting
A discovery call with the client is the best source for the first two sections of the brief.

3. Design direction

Send the design, or the closest thing you have: layouts, brand kit, fonts, colours, logo files, and two or three sites the client likes with a note on what they like about each. If there is no design yet, say so; that changes the scope.

4. Content

  • Who is writing the copy, and when will it arrive?
  • Are images supplied, stock, or to be sourced?
  • Is there existing content to carry over?

Late content is the most common cause of late launches. Put the delivery date in the brief.

5. Structure and features

List the pages and what each must do. Then list the functions: forms, bookings, a blog, a store, memberships, integrations. For Shopify, add catalogue size, variants and the apps you expect; our scoping guide goes through it. For WordPress, say whether Elementor Pro features are needed; see Elementor Pro vs free.

Tip: If you only have time to write one thing well, make it the list of what each page must do. “Contact page” is vague; “contact page that routes quote requests to sales@ and shows opening hours” is a brief.

6. Access and ownership

Where will the site live, and who owns the hosting, domain and licences? Provide logins or tell the studio who will. If this is a takeover rather than a new build, start with the audit in how to take over an Elementor site.

7. Dates and constraints

The real launch date, and what it is tied to. A fixed event date is information; a vague “ASAP” is not. Mention review windows too: if your client takes two weeks to approve, the schedule must allow for it.

8. Confidentiality and communication

Say whether the client knows a partner is involved, what the studio may and may not say, and whether you need an NDA first. Agree how you will talk: one channel, with answers expected within a stated time.

9. What is out of scope

State what you are not asking for: copywriting, ongoing changes, SEO, hosting. Revision rounds should be agreed up front; see how to handle client revisions with a white label partner.

Watch out: Avoid sending the brief as a chain of forwarded emails. Studios miss details in threads; put the final version in one document and say it supersedes earlier messages.

A brief you can copy

Section What to write
Contact Name, role, preferred channel, response time
Business What the client does, who for, the goal of the site
Design Files, links, brand assets, references
Content Who writes it, when it arrives, what is carried over
Features Pages, functions, integrations, apps
Access Hosting, domain, licences, logins
Dates Launch date and what it depends on, review windows
Confidentiality White label terms, NDA
Out of scope Anything you are not asking for
Cup of coffee and a notebook on a table
A brief does not need to be long; it needs to be complete enough that nobody has to guess.

Why this works

A brief gives the studio what it needs to quote accurately and build without constant questions. It also protects your client relationship: fewer surprises means fewer awkward calls. Our process is built around a clear brief and a fixed quote before any work starts.

Send us one

We build WordPress sites with Elementor and custom-coded Shopify stores under your brand. Send your brief, even a rough one, via contact. If you are still choosing a partner, read how to choose a white label Elementor agency and our partner program; the services are described on white label Elementor development and white label Shopify development.

Frequently asked questions

How detailed does the brief need to be?
Detailed enough to quote from. Rough is fine; missing is the problem. Flag unknowns rather than guessing.
What if the client has not decided on the design?
Say so. Design decisions affect scope, so it may be a separate step before the build.
Should the brief come from the client or the agency?
From the agency, in one document, so the studio gets one consistent version.
Can a studio help write the brief?
Often yes. A short call to fill gaps is quicker than guessing, and it is better to do it before the quote than after the build starts.

Sources and further reading

  1. Google: creating helpful, people-first content — useful when briefing content.
  2. Google: title links — what to specify for page titles.
  3. Google: snippets and descriptions — what descriptions do.
  4. WordPress: documentation — the platform for most builds.
  5. Shopify: themes — what a Shopify build involves.
  6. Elementor Help Center — reference for Elementor features.

Ready to talk?

Looking for a white label web partner you can actually rely on?