Is It Out of Scope? — Web development
Is creating a lead-scoring model out of scope for a web development project?
Yes. Defining scoring logic and rules is a marketing-strategy task; a build might implement it, but doesn't design it.
This comes up when a build includes CRM integration work, and the client assumes that since the dev team is "already in the CRM," they can also work out what should make a lead worth more or less.
Is it out of scope?
Yes. Wiring data into a CRM is a technical task; deciding which behaviors and attributes should raise or lower a lead's score is a marketing-strategy decision, not a development one.
Clause typically implicated
Clause typically implicated
Exclusions clause→ — Defining lead-scoring criteria is excluded from a development scope as a marketing-strategy task distinct from the technical integration work.
Example contract wording
Example contract wording (illustrative, not legal advice)
We can build the integration that sends data into your CRM, but deciding the actual scoring criteria — what raises or lowers a lead's score — is a marketing-strategy call, outside this build.
How MarginFlow flags it
MarginFlow flags lead-scoring-model requests outside_scope on development contracts, keeping the distinction from CRM integration work a build might include.