is a competitor analysis out of scope?
Yes — a competitor analysis or market audit added partway through is a distinct research deliverable outside your original scope. The exception is an agreement whose discovery phase explicitly included competitive research.
Why this answer
Research is a deliverable in its own right, even though it rarely looks like one. When a client asks you mid-project to study their competitors, audit a market, or benchmark rivals, they're requesting a body of investigative work — gathering, evaluating, and synthesizing information into something usable — that produces value independent of whatever you were originally hired to make. The reason it slips past people is that research feels like 'just understanding the problem,' as if it were background you'd naturally do anyway. But a structured competitive analysis is hours of focused effort with its own output, and it's the kind of thing consultancies sell as a standalone engagement. Unless your agreement's discovery phase named competitive research as an included input, this is new work bolted onto the project. The deliverable you were contracted for hasn't changed; the client has added a second, earlier deliverable in front of it. That addition deserves its own scope, timeline, and fee rather than being absorbed as a courtesy.
When the answer flips
The verdict shifts toward In Scope when your agreement's discovery or research phase explicitly covered competitive or market analysis — then producing it is exactly what you were paid for. It softens when the 'analysis' the client wants is genuinely lightweight: a quick glance at two rival sites to inform a decision you were already making is often just diligence, not a deliverable. It turns ambiguous when your proposal promised a 'strategic' or 'research-led' approach without defining how much research, since the client may have pictured competitor work as part of that. The sharp flip toward Out of Scope is anything that becomes a deliverable in its own right — a written audit, a benchmarking report, a documented findings deck — because those have value the client could extract and use entirely apart from your original engagement.
What to do next
Name what's actually being asked for, because 'can you look at our competitors' can mean five minutes or five days. Ask what the analysis is for and what form the output should take — a quick verbal read, or a documented report. If it's the lightweight version and it genuinely sharpens work you're already doing, a brief look may be reasonable to fold in. If it's a real deliverable, scope it as one: define what you'll examine, what you'll produce, the timeline, and a fixed fee for the research as a distinct line item. Offer it as an add-on the client can accept or decline, and make clear that the main project continues on its own schedule. Send a short change order, and only start the research once it's agreed.
Frequently asked questions
Isn't understanding competitors just part of doing good work?
A general awareness of the landscape is part of being good at your craft, and nobody bills for the context they carry in their head. A structured analysis is different: it's deliberate, time-consuming, and produces a usable artifact. The line is between the diligence that informs your judgment and a research output the client could hand to someone else as a standalone document. The first is baked into your fee; the second is its own deliverable.
How do I price a competitor analysis as an add-on?
Scope it by output, not hours, so the price doesn't balloon as you dig. Decide what the client gets — say, a short audit of a fixed number of competitors against named criteria — and quote a flat fee for that defined deliverable. A bounded scope protects you from an open-ended research spiral and gives the client a clear number to approve. If they want more depth, that's a larger, separately priced version, not an overrun on the first.
The client says the research is needed to finish my actual work. Is it still extra?
Necessity to the project doesn't make it free; it makes it a prerequisite the client is choosing to add. Plenty of useful inputs sit outside scope — the question is whether your agreement promised this particular input. If it didn't, you can do the research as a paid add-on or proceed with the information you already have and flag the gap. What you shouldn't do is silently absorb a full audit because it would improve the outcome.
What if I already did some competitor research informally?
Informal glancing and a formal analysis are different products, and doing the first doesn't obligate you to deliver the second for free. If you've absorbed light competitive context to inform your decisions, that's just good practice. If the client now wants that knowledge written up, benchmarked, and packaged into a report, they're asking you to turn private diligence into a deliverable — which is real additional work that deserves its own scope and fee.
Can I include a small amount of research in my base scope to avoid this?
You can, and naming it precisely is what protects you. Vague promises of a 'research-led' or 'strategic' approach invite exactly this expansion, because the client fills the gap with their own assumptions. Instead, state what research is included — for example, a brief review of competitors during discovery — and what counts as a separately scoped audit beyond that. A defined boundary lets you offer some research without it becoming unlimited research.
How do I keep the main project moving while we sort out the research?
Decouple them explicitly. Tell the client the original deliverables continue on their existing timeline while the proposed analysis is scoped and approved separately, so the project doesn't stall on a side request. If the research genuinely needs to come first because later work depends on it, say so and adjust the schedule openly. The point is to keep the two threads from tangling, so adding research doesn't quietly delay everything you already committed to.
Related reading
- The full guide
The scope creep guide for freelancers
How to spot scope creep, why clients do it, what it costs you, and how to respond professionally.
- Scenario
Is a second round of stakeholder review in scope?
Ambiguous — a new stakeholder reviewing already-approved work usually introduces new feedback that exceeds the original scope, but the revi…
- Scenario
Is a rush deadline out of scope?
Yes — a mid-project deadline acceleration is out of scope unless your contract explicitly accommodated shifting timelines. The work itself…
- Clause guide
What a deliverables clause should include in freelance contracts
A strong deliverables clause names each artifact with a format, a quantity, and — critically — an exclusion list. If it's not named, it's n…
- Profession guide
Scope creep for web developers: where projects actually break
Web development scope creep usually hides in the gap between 'build this feature' and 'make it work in production.' Clients think the featu…
- Scenario
are extra meetings out of scope?
Yes — meeting time past the checkpoints your contract scoped is billable work, even though it doesn't produce a deliverable. The exception…
Answer scope creep from your actual contract — not a template.
Settled reads your contract and the client's request, gives you a verdict (In Scope / Out of Scope / Ambiguous), and drafts the email grounded in your specific clause.