Is It Out of Scope? — SEO & marketing
Is building a custom reporting dashboard out of scope for a SEO / marketing project?
It depends what's actually being asked for. Delivering the metrics and analysis themselves is core SEO reporting work, often already in scope — building a live, interactive dashboard tool is a separate application build outside the retainer.
SEO retainers routinely include some form of reporting — rankings, traffic, conversions — usually delivered as a document or spreadsheet on a set cadence. Clients sometimes ask for that same information as a "dashboard" instead, imagining something they can log into and check whenever they want. The metrics themselves are often already part of the retainer; the live, interactive tool to display them typically isn't.
Is it out of scope?
Depends what's meant by "dashboard." If it's really asking for the existing reporting content in a different format (a shared spreadsheet or an existing analytics tool's dashboard view), that's usually achievable within the retainer. If it's asking for a custom-built, live application with its own data pipeline and UI, that's development work outside the retainer, even though the underlying metrics are the same ones already being reported.
Clause typically implicated
Clause typically implicated
Exclusions clause→ — The retainer covers the reporting content itself — a custom application to display it live is a separate development deliverable outside that.
Example contract wording
Example contract wording (illustrative, not legal advice)
The metrics themselves are already part of what we report on — happy to talk through a format that feels more like a dashboard, like a shared view in [existing analytics tool]. A fully custom-built dashboard application is a separate development project outside our retainer; let me know if that's really what you're picturing and I can help scope it with a developer.
How MarginFlow flags it
MarginFlow keeps confidence lower on "dashboard" requests specifically, since the word covers both an in-scope reformatting of existing reporting and an out-of-scope custom build — the explanation flags the ambiguity and suggests clarifying which one the client means before responding.