Turn a vague client brief into a clear scope with AI (a hidden-dependency check, prompt included)

"We need a simple website." "Just a few blog posts." "Something like what [competitor] has."

Briefs like these are normal. Clients describe what they want in their own terms, and "simple" is about how it should feel, not how much work it is. The trouble starts when you quote from the vague version. Every unasked question becomes a later conversation about what was "obviously included".

This article walks through one AI prompt you can use before you quote. You give it the brief and some context about your business. It lists the assumptions, missing information, hidden dependencies and likely scope-creep points, and drafts the questions to send back to the client. There's a worked example, and a section on where the method breaks down.

Why one-line prompts give you generic scopes

If you paste a brief into a chat assistant and ask "write a scope of work for this", you'll get something that looks professional and could apply to almost any project. The AI fills the gaps with typical assumptions, because you haven't told it anything else.

This is a common complaint about generic prompt collections. Reviewers point out that many packs are padded with generic variations (dev.to), and that the value is in your own business context, not clever wording (Lilach Bullock).

There's a second problem: asking for a scope invites the AI to answer the gaps instead of flagging them. You want the opposite. The aim of this step is not a finished document. It's a list of what you don't know yet.

So the prompt below asks the AI to look for hidden dependencies and open questions before anything goes into a quote or contract.

Before you paste anything: a privacy check

Client briefs can contain confidential information. Before you paste one into any AI tool:

The prompt

Copy this, then fill in the two bracketed blocks.

You are helping me, a freelancer, check a client brief BEFORE I quote.
Do not write a scope of work. Your job is to find what is unclear,
missing or assumed.

ABOUT MY BUSINESS:
[3-6 lines: what you do, your typical deliverables, what you don't do,
your usual number of revision rounds, the tools/platforms you work in]

THE CLIENT BRIEF (de-identified):
[paste the brief, plus any notes from your first call]

Rules:
- Only use what is in the brief and my business notes.
- Do not invent facts, numbers, prices or client preferences.
- If something is not stated, write "UNKNOWN - ask client".
- Quote the exact words from the brief that each finding is based on,
  or write "not mentioned".

Give me four sections:

1. ASSUMPTIONS I'd be making if I quoted from this brief as-is.
   Table: assumption | based on (quote or "not mentioned") | risk if wrong (H/M/L)

2. HIDDEN DEPENDENCIES: things the project needs that I don't control.
   Check these categories: content and assets, access and logins,
   decision-makers and approvals, third parties, paid tools or fees,
   existing data or material, technical integrations, checks the client
   owns (legal, compliance, accessibility), timing and feedback speed,
   undefined quantities or "done" definitions.
   Table: finding | category | evidence | likely owner (me/client/third party)

3. LIKELY SCOPE-CREEP POINTS: where this project is most likely to grow
   after I've quoted, and why.

4. QUESTIONS FOR THE CLIENT: at most 10, most important first.
   Write them in plain, friendly language a non-expert would understand.
   One question per line.

Why each part is there

Worked example

Fictional example. The business, the brief and the freelancer are invented.

About my business (as pasted):

Solo web designer. I design and build small-business sites on [website platform]. Typical project: 4-6 pages, my design, client supplies copy and photos. I don't write copy or take photos. Two revision rounds per page. I don't do ongoing maintenance unless agreed separately.

The brief (as pasted, de-identified):

Hi! We're [CLIENT], a dog-grooming salon. We need a simple website, nothing fancy, with online booking so people stop phoning us. Maybe 4 or 5 pages. We'd like it to look a bit like [competitor]'s site. Our old site is on some builder my nephew set up. We'd love it live before the spring rush.

Example output (illustrative: we wrote this to show the format; it is not a recorded AI run, and your output will differ):

Finding Category Evidence Likely owner
Which booking system, and who pays for it, isn't stated Paid tools / third parties "online booking" Client to choose and pay; UNKNOWN - ask client
Whether booking needs deposits, card payments or reminders is unclear Undefined "done" "so people stop phoning us" UNKNOWN - ask client
Logins for the old site and domain are with a relative Access "some builder my nephew set up" Client
Who writes the page copy isn't stated Content not mentioned Client (per my business notes)
"4 or 5 pages" isn't a fixed number Undefined quantity "Maybe 4 or 5 pages" UNKNOWN - ask client
"Look a bit like [competitor]" doesn't say which parts Undefined "done" "a bit like [competitor]'s site" UNKNOWN - ask client
No specific launch date Timing "before the spring rush" UNKNOWN - ask client
Who approves the design isn't stated Approvals not mentioned UNKNOWN - ask client

Likely scope-creep points (abridged): the booking set-up growing into payments, reminders and staff calendars, and "a bit like [competitor]" turning into copying specific features.

What we kept and what we threw away. Reviewing an output like this is part of the job. In the example:

Turning the output into questions and exclusions

The output is raw material for two things you'll actually use.

1. A short email of questions. Pick the five to eight that change the price or timeline, and send them before you quote:

Hi [Name], thanks for the brief. Before I put a quote together, a few quick questions so it's accurate:

  1. Do you already have a booking system in mind, or would you like a recommendation? (Many charge their own monthly fee, which you'd pay directly.)
  2. Should clients pay a deposit when they book, or just reserve a time?
  3. Will you be writing the page text, or would you like a recommendation for a copywriter?
  4. Could you get the login details for your current site and domain from whoever set them up?
  5. Which parts of [competitor]'s site do you like: the look, the layout or particular features?
  6. Is there a date you'd like the site live by?
  7. Who will give feedback on the design, and who has the final say?

2. An "assumptions and not included" list for your proposal or scope summary, written in a friendly way:

That "not included" list is what makes a later "that's extra" conversation easy. The guide to out-of-scope replies covers that conversation. The client onboarding checklist shows where this check fits between the first call and kickoff.

The limits (read this part)

Used this way, the AI acts like a careful second reader. It's good at noticing what's missing. You still decide what matters.

Want the full workflow?

This prompt is one step. The Scope Guard & Client Onboarding Kit puts it inside a full intake-to-kickoff workflow:

It works with any chat AI assistant, plus Google Docs or Word, and Google Sheets or Notion. It isn't a contract and it isn't legal advice.

The kit isn't on sale yet. See what's in the kit


Sources

← All posts