A client who genuinely can't fully define what they need yet still needs a number to move forward, and both directions of getting that number wrong cause a real problem, price too high and lose the deal, price too low and eat the gap yourself once the real scope emerges. Refusing to price it at all just delays a conversation that has to happen eventually.
Pricing an unclear scope isn't about guessing better. It's about being explicit that the number reflects what's known now, not a final commitment to everything that might come later.
Pricing an unclear scope wrong hurts you in either direction
A number that's too high loses the deal before it starts; a number that's too low locks you into absorbing whatever the real scope turns out to be. Both failure modes come from treating an inherently uncertain scope as if it were fully known.
Price the parts that are actually known, and name what isn't yet
Separate what's genuinely well-defined from what's still uncertain, and price the known parts with real confidence while explicitly flagging the rest as still to be scoped. This is more honest, and more defensible later, than one blended number covering everything.
In Stelaah, a project's scope can evolve from an initial estimate into confirmed deliverables as clarity develops, so pricing can track the real state of the work instead of a single upfront guess. See how estimates works.
Use a range with a not-to-exceed ceiling instead of a single number
A range gives the client a realistic sense of the likely cost while protecting you from being held to the low end once the real scope is clearer. Cap it with a not-to-exceed ceiling so the client also has a real bound on their exposure.
Build in an explicit checkpoint to re-scope once things clarify
Build a defined point into the engagement, after initial discovery, at a milestone, where the scope and price get formally revisited once more is known. This turns an uncertain start into a structured process rather than an open-ended guess nobody revisits.
Don't let a vague scope quietly become unpaid, unbounded scope
An unclear scope can quietly expand during execution simply because nothing was ever pinned down to compare against. Reference the checkpoint and the original range explicitly when the real scope starts to emerge, rather than absorbing the growth silently.
A simple checklist
If you do nothing else, do these five things:
- Price the known parts with confidence, flag the rest explicitly.
- Use a range with a not-to-exceed ceiling, not one single number.
- Build in a real checkpoint to re-scope once clarity develops.
- Reference the original scope explicitly as the real picture emerges.
- Don't let uncertainty quietly become unpaid, unbounded work.
Do that, and pricing an unclear scope becomes an honest, structured starting point, not a guess either side ends up regretting.
Run your client work in one place. Stelaah keeps projects, clients, contracts, and invoices together, with Aria for the busywork.
Start freeWe build Stelaah, the workspace for client work. We write about running teams, agencies, and venues without the busywork.
