How to Brief a White Label Developer Without a Technical Lead

Grafitti of mice

You don’t need to know how a website is built to brief one well. What trips most agencies up isn’t a lack of technical knowledge — it’s not knowing which non-technical details actually matter to a developer, and which ones we’ll work out ourselves. Get those the wrong way round and you end up with a brief that’s either too thin to quote against, or padded with detail nobody needed.

Here’s what actually helps, in the order we’d want it.

Start with the client's goal, not the site's features

The single most useful sentence in any brief isn’t “we need a new homepage” — it’s “the client wants more people to enquire about X” or “the client is losing sales at checkout.” Features follow from goals; goals rarely follow from a feature list.

If you only have the client’s own brief to work from, that’s fine — pass it on as-is rather than translating it into what you think a developer wants to hear. We’d rather read the client’s actual words and ask our own follow-up questions than work from a summary that’s lost something in translation.

Tell us what's changing and what isn't

A surprising number of briefs describe the new site in full without mentioning what currently exists. That leaves us guessing at things that change the quote significantly:

  • Is there an existing site, and does any of it need to carry over — content, URLs, SEO rankings, email integrations?
  • Is the domain and hosting already sorted, or does that need setting up too?
  • Are there brand guidelines already, or is design direction still open?
  • Does anyone need to keep editing the site themselves once it’s live, or is it launch-and-done?

None of these need technical answers. They’re all things you’d know from the client relationship, not from knowing how WordPress works.

Bring examples, not specifications

“Make it modern and clean” tells us nothing. Three websites you like — even from completely different industries — tell us a lot, especially if you can say what you like about each one. One might be the layout, another the tone of the copy, another just the colour palette. We’ll separate out what’s actually replicable from what’s just a vibe, but we need the raw material first.

The same goes the other way: if there’s a site the client explicitly wants to avoid looking like (a competitor, usually), that’s worth flagging too.

Give us a real budget range, even a rough one

Agencies sometimes leave budget off a brief on the assumption that we’ll just quote whatever the project costs. In practice, an unbounded brief takes longer to scope, not less — we end up proposing a version of the project we’d need to then adjust once a number appears. A rough range, even “somewhere between £3k and £6k, flexible if you can make the case,” lets us scope something that’s actually going to get approved. We’ve published rough pricing by project type if that’s a useful starting point before you go back to the client.

Flag the deadline that actually matters

Most projects have one real fixed date — a product launch, an event, a campaign going live — and several softer ones that came from a general sense of “sooner is better.” Tell us which is which. A hard deadline changes how we plan the build; a soft one gives us room to flag if something in the brief will genuinely take longer than the client expects, before it becomes a problem two weeks before launch.

You don't need to write the technical spec

This is the part that puts agencies off briefing a build at all — the worry that they’re expected to specify platforms, plugins, hosting requirements or integrations correctly, and that getting it wrong will look bad. You don’t need to. Tell us what the site needs to do (take bookings, sell products, let five different people log in and edit content) and we’ll work out how. If we need a technical decision from you specifically, we’ll ask a specific question, not hand back a form to fill in.

A brief that would actually work

Put together, a genuinely useful brief is usually shorter than agencies expect:

  • What the client wants to achieve, in their own words if possible
  • What exists already, and what needs to survive the rebuild
  • Three reference sites, with a note on what you like about each
  • A rough budget range
  • The one date that can’t move
  • Anything the client has explicitly ruled out

That’s it. Everything else — platform, plugins, page-builder, hosting — is our end of the job.

If you're not sure what to include, just send what you have

Half-formed briefs are normal, not a problem. If you’re not sure whether something’s relevant, include it and we’ll tell you if we don’t need it — that’s a much faster conversation than you trying to second-guess what a developer wants before you’ve even briefed the project.

Send us a brief — however rough — and we’ll come back with questions where we actually need answers, not a form to fill in.

Red Ink Creative
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.