Is It Out of Scope? — SEO & marketing
Is building a custom CRM integration out of scope for a SEO / marketing project?
Yes. CRM integration is backend engineering work with no organic search component, outside an SEO retainer regardless of how the lead data might eventually be used for SEO reporting.
This sometimes comes up because the SEO team is already looking at conversion data and lead sources as part of reporting, which can make a CRM connection feel adjacent to their work. But wiring form submissions into a CRM is a backend integration task with no organic search component — the SEO team consuming lead data for reporting is a different thing than building the pipe that delivers it.
Is it out of scope?
Yes. This is development work with no SEO-specific expertise required, and it's outside the retainer even though the resulting data might eventually feed into SEO or marketing reporting.
Clause typically implicated
Clause typically implicated
Exclusions clause→ — Development and integration work is excluded from the retainer regardless of how the resulting data connects to reporting the retainer does cover.
Example contract wording
Example contract wording (illustrative, not legal advice)
Connecting the forms to your CRM is development/integration work outside our retainer — not something I'd want to take on without the right technical background. Once it's set up, I'm glad to help make sure the data we need for SEO reporting is flowing through correctly.
How MarginFlow flags it
MarginFlow flags CRM integration requests outside_scope on SEO contracts by default, with the explanation offering the narrower, genuinely relevant follow-up (verifying reporting data once the integration exists) so the account manager can decline the build while staying useful on the reporting side.