Scoping a Project Before the Client Has Finished Deciding What They Want¶
A client emails asking for a quote on "a new brand identity" or "a redesign of our packaging line" - no deliverables list, no format specifics, sometimes not even certainty about whether they want a refresh or a full rebuild. The instinct is to treat this as an incomplete brief that needs filling in before you can scope it. Often it isn't incomplete - the client genuinely hasn't decided yet, and won't be able to until they see some options. Scoping that kind of project as if the deliverables are already fixed is where most of the painful scope-creep conversations later actually start.
The Real Problem Is Timing, Not Vagueness¶
Most scoping friction isn't caused by a client being unclear - it's caused by asking for a fixed price at a stage of the project where the actual work hasn't been decided yet. A client who says "I'm not sure if we need a full rebrand or just a refresh" isn't withholding information; they don't have that information themselves until they've seen what each option would look like. Quoting a fixed deliverable list against that kind of brief means one of two things happens later: the quote turns out to cover the wrong work, or the client feels nickel-and-dimed when the "real" project turns out to be bigger than what was priced.
Scope the Decision Phase Separately From the Execution Phase¶
The fix is splitting the engagement into two scoped pieces instead of one: a short, fixed-price direction phase that produces two or three concept directions or a clear recommendation (refresh vs. rebuild, one direction vs. another), and a separate execution phase scoped only once that decision is made. This isn't slower for the client - it's usually faster, because they're not waiting for a single monolithic quote that has to account for every possible outcome. It also means the price for "figuring out what we actually need" is honest about being its own piece of work, instead of being absorbed invisibly into whatever the final deliverable turns out to be.
Define "Done" With Examples, Not Adjectives¶
Once the direction is set, scope the execution phase around concrete decision points rather than subjective outcomes. "Two rounds of revisions" is clearer than "revisions until you're happy," because it gives both sides a shared, countable definition of when the project is finished. Naming exact deliverable formats up front - file types, sizes, how many packaging SKUs, how many brand touchpoints - closes the most common gap between what a client assumed was included and what was actually quoted. None of this requires the client to have fully decided what they want before the contract is signed; it just requires the process for deciding to be scoped as clearly as the final output.
Build a Change-Order Path Into the Scope From the Start¶
Some amount of "actually, can we also..." is normal on any project with an undefined starting brief - it isn't a sign the scoping failed. What matters is whether there's already an agreed, low-friction way to handle it: a simple rate for additional concepts or rounds beyond what was scoped, agreed before the project starts rather than negotiated mid-project when both sides have more at stake. A change-order path that exists on paper before it's needed turns "this is now bigger than what we agreed" from a confrontation into a normal, expected step.
FAQ¶
Won't clients be put off by a two-phase proposal instead of one clean quote?
Most clients find it a relief once it's framed correctly - it tells them they're not committing to a large execution budget before they've seen any real options, which is usually a lower-risk proposition for them, not a higher one.
How do I price a direction phase that might not lead to a contract?
Price it as real, standalone work, because it is - the deliverable is a clear recommendation and a couple of concept directions, which has value on its own even if the client doesn't move forward with you for execution.
What if the client insists on a single fixed quote for the whole undefined project?
Quote conservatively for the largest reasonable interpretation of the brief, and say so explicitly - "this price assumes it becomes a full rebrand; if the direction phase points toward a lighter refresh, I'll requote down" sets the expectation honestly instead of leaving it to be discovered later.