Project scoping is one of the places where agencies quietly lose money. Choco Media has learned this the hard way: a project scoped too loosely becomes a client relationship built on silent resentment. The team delivers more than was budgeted. The client expects even more than the team delivered. Nobody wins. This post is our honest account of the discovery call questions and scope document structure we use today — the system that helped us price accurately and avoid unpaid extras.
If you run a small agency or work as a freelance consultant, this is for you. It assumes you already know how to do the work. The problem this post solves is simpler and more painful: how do you scope it honestly, price it fairly, and still get the yes?
By the end of this, you will have a clear picture of our discovery call structure, the scope document format we use, the signals that tell us a project is under-scoped, and the language we use to explain scope creep before it happens. None of it is magic. Most of it took us a year of expensive lessons to assemble.
Why project scoping goes wrong
Most scoping problems start before the discovery call. A potential client arrives with a brief that describes what they want without describing what they actually need. These are rarely the same thing. The brief says “a website.” What it means is: a redesign, a migration, a content strategy, an SEO audit, stakeholder sign-off across three departments, and a photoshoot that nobody has budgeted for yet.
The instinct, especially early in an agency’s life, is to quote what the brief describes. That instinct is expensive.
We have found three consistent failure modes in scoping:
- Optimistic estimation. You scope for the clean version of the project. Projects are never clean. There is always a stakeholder who was not in the first call. There is always a brand guideline document that contradicts itself.
- Undefined deliverables. “A landing page” means different things to different people. One client means a designed mockup. Another means a fully coded, CRO-tested, integrated page with six rounds of copy revision.
- No conversation about what is excluded. Scope documents list what is included. The most valuable section is what is not included. Most scope documents skip this entirely.
Fixing these three things does not require a new tool or a 12-step methodology. It requires a discovery call that asks harder questions than most agencies ask, and a scope document that is explicit in a way that most agencies avoid.
The discovery call: what we actually ask
We run discovery calls as structured conversations, not pitches. The goal is not to sell. The goal is to understand enough to price accurately. If the project is a bad fit after the call, that is a good outcome — for both sides.
Opening with intent
We start every call the same way: “Before we talk about solutions, help us understand the problem you are trying to solve.” This sounds simple. It almost always surfaces a different problem than the one in the brief.
A client who says they want a new website often means their current site is embarrassing them in sales conversations. That is a confidence problem, not a technology problem. The solution might still be a new website — but the scope, the success metric, and the budget conversation all shift when you understand the real underlying need.
The questions we ask every time
Across all project types, these questions appear in every discovery call we run:
- What does success look like in six months? What number changes?
- Who else is involved in the project on your side — and who can block it?
- Have you tried to solve this before? What happened?
- What is the internal timeline driver? Is there a launch date, a board meeting, a campaign?
- What would make you regret hiring us?
- What is the budget range you are working within?
The last question is the one people most want to avoid. We ask it directly because a vague budget conversation always produces a vague scope. When a client says they do not have a number in mind, we offer two or three indicative ranges and watch the reaction. That reaction tells us as much as the number itself.
Project-type specific questions
On top of the standard questions, we layer specifics depending on the type of work. For a content retainer, we ask about approval chains and revision tolerance. For paid media, we ask about historical account access and whether there is a creative team or if we are expected to produce everything. For a website, we ask about the CMS, the existing analytics setup, and whether there is a copywriter or if that is in scope too.
The question that saves us the most time: “Is there anyone we have not spoken to who could change the direction of this project?” If the answer is yes, we do not scope until we have spoken to them.
What goes into the scope document
After the discovery call, we produce a scope document before we produce a proposal. The scope document is not the proposal. It is the input to the proposal. We share it with the client, ask for confirmation that we have understood the project correctly, and only then price it.
This adds a step. It is worth it every time. The scope confirmation step is where we catch misunderstandings before they become contract disputes.
The structure we use
Our scope documents follow a fixed structure regardless of project type:
- Project summary. One paragraph. What the project is, who it is for, and what it is trying to achieve. Written in plain language the client can show to their boss.
- Deliverables. A numbered list of everything we will produce. Each item is specific: not “social content” but “12 Instagram posts per month, in static format, sized 1080×1080, with captions up to 150 characters.”
- What is not included. This is the most important section. Explicitly call out the things that are adjacent to the project but not in it: photography, translation, media spend, third-party tool costs, SEO optimisation, post-launch support.
- Assumptions. The things we are taking as given. “We assume the client will provide brand assets within five business days of contract signature.” If the assumption proves false, the scope changes.
- Revision rounds. The number of included revision cycles per deliverable, and what happens outside that number.
- Dependencies and timeline. What we need from the client, by when, for the project to hit its dates.
Pricing from the scope, not from the brief
Once the scope is confirmed, pricing is mostly maths. We estimate time by deliverable, apply a multiplier for coordination and project management (we use 1.3x for most projects, 1.5x for anything involving multiple stakeholders on the client side), add third-party costs at cost, and arrive at a number.
The mistake we made early was pricing from the brief and then reverse-engineering a scope to justify the number. This produces scopes that are too tight and projects that are too stressful. Pricing from an honest scope is slower upfront and much less painful over the life of the project.
Where to add contingency honestly
We build contingency in at the deliverable level, not as a line item. If we know a particular type of deliverable tends to run long — say, a homepage that involves the founder’s personal preferences — we estimate higher for that item and note the assumption in the scope document. This is more honest than a 15% “contingency fee” that clients always question.
- For projects with undefined technical environments: add 20% to development estimates.
- For projects with more than two approval stakeholders: add one full revision round per deliverable type.
- For first projects with a new client: apply 1.2x on everything. You do not know their working style yet.
The language of scope creep
Even with a clear scope document, requests arrive mid-project that sit outside it. How you handle these conversations determines whether the client relationship survives them.
We use consistent language for out-of-scope requests. The goal is not to say no — it is to make the conversation explicit before it becomes an assumption. In our bespoke retainer work, we build a small flex budget into the relationship for exactly this kind of thing. But for project-based work, the conversation needs to happen cleanly.
The phrases we use
- “That is not in the current scope, but we can price it as an addition. Want us to send a quick estimate?”
- “We can absorb this if we remove [X] from the current deliverables. Would that trade work for you?”
- “This is a small one — we will include it this time. For anything like this going forward, we should talk about a monthly retainer that builds in that flex.”
The first option is for meaningful additions. The second is for project pivots where something else becomes less important. The third is for genuinely small things that would cost more to negotiate than to do — and it plants a useful seed about retainer structure.
For more on how we structure ongoing work, see our AI automation service, which we often scope as a phased project followed by a retainer to maintain and iterate.
The signals that a project is under-scoped
After enough projects, you start to recognise the patterns that signal a scope is too thin before you have started the work. We call these red flags internally, and we treat them as a requirement to go back to the scope document before signing anything.
- “We just need something simple.” Simple projects are often the most under-scoped. Simplicity is a design achievement, not a starting state.
- A compressed timeline with no explanation. Urgency without context usually means a previous agency relationship ended badly, or there is a deadline the client has not disclosed.
- “We will know it when we see it.” This is the most expensive sentence in the service industry. It means there are no defined success criteria, which means there is no endpoint.
- The decision-maker is not in the room. If you cannot get the actual decision-maker on the discovery call, every scope you write is provisional.
- The brief does not mention what has already been tried. A client who has not explained why the last attempt failed usually does not know why it failed. That uncertainty transfers to your scope.
When we see two or more of these signals in a single project conversation, we either slow the process down and ask more questions, or we decline. This is discussed in more detail in our post on why we say no to 7 out of 10 leads.
What to do when the scope breaks mid-project
Sometimes the scope breaks despite good process. A stakeholder enters the project late with strong opinions. The brief evolves. The original goal proves to be the wrong goal.
In these situations, the scope document becomes the reference point for a reset conversation, not a stick to beat the client with. We send a short email — we call it a scope reset note — that summarises what has changed, what the original scope assumed, and three options for how to proceed: continue with the original scope and deprioritise the new request, amend the scope and price, or pause and replan from scratch.
Presenting options is important. Clients who feel backed into a corner make difficult decisions. Clients who are choosing between three clear paths make faster, calmer decisions.
Making scoping a competitive advantage
Most agencies compete on portfolio, price, or personality. Clear, honest scoping is a rarer differentiator than any of those. When a client has been through a badly scoped project before — and most have — the experience of working through a structured discovery process and receiving a scope document that explicitly lists what is not included is genuinely reassuring. It signals that you know what you are doing and that you will tell them the truth even when the truth is inconvenient.
We have had clients choose us over cheaper options specifically because our scoping process felt more trustworthy. That is not something you can put in a pitch deck easily, but it is real and it compounds.
If you want to build this kind of trust from the first conversation, the starting point is always the same: ask better questions than the other agencies in the room, and be willing to write down what is not included.
If you are building out your agency operations or thinking about how to structure client relationships more sustainably, we are happy to talk. Get in touch and we can walk through how we approach scoping for the kind of work you do.