A veteran sales operations analyst proposes replacing Dynamics 365 Sales predictive lead scoring with a simple manual formula that adds points for job title seniority, company size, and how recently the lead was created, arguing it will be more transparent than the AI model. Which limitation of the analyst's proposed manual formula should the consultant raise?
Select an answer to reveal the explanation.
Short Explanation
A hand-built point system is really just a snapshot of somebody's best guess today about what a good lead looks like, and that guess sits frozen the moment it is written down. Meanwhile, the AI-driven approach keeps checking itself against what actually happens to leads over time, so if a signal that used to matter stops mattering, or a new pattern shows up, the model can shift with it. A fixed formula cannot do that on its own; someone would have to notice the drift and manually rewrite the point values, and that rarely happens promptly in practice. The other objections people sometimes reach for do not really hold up here, since there is nothing stopping the formula's result from being shown on the form, and nothing stopping the inputs the analyst wants from being referenced at all. The honest trade-off to raise with the analyst is about staying current, not about whether the idea can technically be built.
Full Explanation
The correct answer is C. The analyst's fixed-point formula bakes in a static judgment about which signals matter and by how much, and that judgment never updates itself as the business's actual pattern of wins and losses shifts, whereas predictive scoring is continually refreshed against real outcomes and can pick up on signal combinations a human would not think to weight by hand. Option A is incorrect because a manually calculated field can absolutely be surfaced on the lead form like any other field; the transparency the analyst wants is achievable, it just does not fix the formula's underlying rigidity. Option B is incorrect because job title and company size are ordinary fields already available on or related to the Leads table, so there is no technical barrier to referencing them in a calculation. Option D is incorrect because Dynamics 365 Sales fully supports adding custom and calculated fields to the Leads table, so the formula is implementable; the objection to raise is about how well it adapts over time, not whether it can be built at all. The real trade-off is adaptability, not feasibility or visibility.