GoDesign Technologies

Scoping · 8 min read

What almost every project brief leaves out

Everyone thinks a brief is about budget and deadline. Across 6,894 clarifying questions we had to ask, those two accounted for barely a quarter. The real gaps were brand assets and content — neither of which is developer work.

Updated 28 August 2026 · GoDesign build team

A printed project brief on a pale sage desk with three quarters of its fields left blank and a pencil resting across it

The short version

  • Brand assets and content are missing from 37% of briefs. Budget and timeline together are only 26%.
  • The gaps that stall a project are almost always the client's homework, not the developer's.
  • About 60% of briefs carry a marketplace default budget bracket rather than a considered number.
  • A brief that answers the fifteen questions below removes most of the back-and-forth before a quote can exist.

We keep a record of every clarifying question we have had to ask on an incoming project, because a brief that needs six rounds of questions before it can be quoted is expensive for everybody. At the time of writing that record holds 6,894 questions. Sorting them by what they were asking about produces a fairly uncomfortable ranking, because it is not the one most people expect.

What the brief did not sayQuestionsShare
Brand assets: logo, colours, fonts, style guide1,30518.9%
Content: copy, images, product descriptions1,24718.1%
Budget or rate93013.5%
Timeline or deadline86812.6%
Platform, CMS or stack choice79111.5%
Integrations, APIs, payment gateways69610.1%
Scope: how many pages or products3955.7%
Mobile or app expectations3675.3%
Hosting or domain2744.0%
Who edits the site after launch2293.3%
Language, multilingual, right-to-left1432.1%
Existing site or migration1432.1%
Target audience1412.0%
SEO expectations1211.8%
Maintenance and support791.1%

The two biggest gaps are not developer work

Brand assets and content account for 37% of everything we have had to ask about, more than budget and timeline combined. That is worth sitting with, because it inverts how most people prepare for a project. Budget and deadline are the two fields everyone fills in, and they are also the two things a good supplier can work around: a range is enough to start, and a deadline can be negotiated once scope is clear.

Brand assets and content cannot be worked around. If nobody knows what the logo file is, what the colours are, or whether there is a style guide, then the design phase either stops or proceeds on a guess that gets thrown away. If the copy does not exist, the build finishes and then sits at 90% for two months waiting on text that was never anybody's job to write. Both are the client's homework, and both are what actually causes the delay that later gets described as the developer being slow.

The budget number is usually a placeholder

There is a second finding sitting underneath this one. Looking at 18,000-odd budgeted briefs denominated in dollars, the distribution is not smooth at all. It clusters hard on a handful of values.

Budget bracketBriefsShare
$30 – $2507,50040.6%
$250 – $7503,59719.5%
$10 – $301,6358.8%
$15 – $251,1936.5%
$8 – $156463.5%
$750 – $1,5006063.3%
$1,500 – $3,0002981.6%

Those top brackets are presets. They are the default options a posting form offers, and roughly 60% of briefs simply take one. This is not people lowballing on purpose; it is people who have no basis for a number picking whatever the form suggested first. Which means that on both sides of the table, the budget line in a brief should be treated as a starting position rather than a constraint, until somebody has confirmed it out loud.

A folder of brand assets, colour swatches and printed copy laid out neatly next to a laptop showing a half-built page
The two things most briefs are missing are the two things that cannot be started without.

What a complete brief actually answers

Working backwards from the table, a brief that removes most of the back-and-forth answers these, in roughly this order of impact:

  1. Do brand assets exist? Name the files, or say plainly that branding is part of the job.
  2. Who is writing the copy, and is any of it written yet? If the answer is nobody, that is a line item, not an assumption.
  3. Is there a budget range, and is it a considered number or a starting point?
  4. Is the deadline driven by something real — an event, a campaign, a lease — or is it just soon?
  5. Is the platform already decided, and if so, why? A decision with a reason behind it is worth keeping; a decision inherited from a previous supplier usually is not.
  6. What has to connect to what? Payment, CRM, inventory, email — each integration is scope, and each one has an owner on the client side who has to hand over access.
  7. How many pages, or how many products, at launch. Not eventually.
  8. Does this need to work as an app, or does it need to work well on a phone? These are very different projects.
  9. Who owns the hosting and the domain, and does anyone have the login?
  10. Who edits the site after launch — someone in-house, or back to the supplier every time?
  11. One language or several, and does any of them read right to left?
  12. Is this a new build or a replacement, and if a replacement, what is being carried across?
  13. Who is this for? One sentence is enough, but the sentence has to be specific.
  14. Does this need to rank, or does it need to convert traffic you already have?
  15. What happens on the day after launch, and who is responsible for it?

Why this is worth the twenty minutes

A brief that answers those fifteen points can be quoted accurately the first time. One that answers five of them gets a quote with padding in it, because the supplier is pricing the risk of the ten unknowns, and that padding is real money that goes to nobody. The alternative to specificity is not a cheaper project; it is the same project with a contingency baked in and a longer timeline.

There is also a filtering effect worth mentioning. A detailed brief gets fewer responses, and better ones. Suppliers who work at volume tend to skip anything that requires reading carefully, which is exactly the selection you want.

Questions people ask

What is the single most common thing missing from a project brief?

Brand assets. Across 6,894 clarifying questions, 1,305 of them — 18.9% — were asking whether a logo, colour scheme, fonts or style guide existed. Content was a close second at 1,247 questions, or 18.1%.

Should I put a budget in my brief?

Yes, but put a range and say whether it is firm. About 60% of briefs carry a default bracket taken from a posting form rather than a considered figure, so suppliers already discount the number they see. A range with a sentence explaining it is treated very differently from a bracket.

Why does a vague brief lead to a higher price?

Because the supplier prices the unknowns. Every question the brief does not answer becomes a contingency in the quote, and that contingency is not negotiable down without answering the question it was covering. Specificity removes padding rather than adding cost.

Do I need the copy written before the project starts?

Not all of it, but you need to know who is writing it and when it lands. Content is the most common reason a build sits finished-but-unlaunched. If nobody in-house can write it, treat copywriting as a scoped line item rather than an assumption.

How long should a project brief be?

Long enough to answer the fifteen points above, which is usually one to two pages. Length is not the measure; a two-page brief that never says who owns the domain is worse than a half-page one that does.

Built by GoDesign FZE, who build WhatsApp and CRM automation for UAE businesses.

Get in touch

Want someone to just do this part?

The tool is free and stays free. If you would rather hand the work over, tell us what you are dealing with and you get a straight answer on scope, cost and timeline.

  • You own everythingRepository, hosting and domain credentials sit in your name from day one, not handed over at the end.
  • A written timelineMilestone dates are agreed in writing before work starts, so you always know what ships next.
  • One business dayEvery enquiry gets a reply from the person who would scope the work, not a sales sequence.
scale@godesign.ae+971 58 903 1983, WhatsApp enabled

Media City, Dubai, UAE · DHA Phase 2, Islamabad, Pakistan

One reply from the person who would do the work, within one business day. Your details stay with GoDesign FZE and are never sold or passed on.

Would rather type than fill in a form?

Message on WhatsApp