A consultant wants deal-risk scoring on the forecast page to factor in a custom 'contract complexity index' that the client calculates from clauses not captured anywhere in Dynamics 365 Sales. Which extension approach delivers this?

The correct approach is to build and publish an AI Builder model trained on the client's contract data, then surface its output through a custom field referenced in the deal-risk configuration. The client's contract complexity index is a bespoke calculation based on data that does not exist anywhere in Dynamics 365 Sales, so the extension has to both generate that score and make it consumable by the platform's deal-risk configuration; building an AI Builder model trained on the client's contract data, publishing it, and surfacing its output through a custom field that the deal-risk configuration references accomplishes both steps. Enabling Conversation Intelligence so call transcripts populate the complexity index automatically is incorrect because Conversation Intelligence analyzes call recordings and transcripts for talk patterns and keyword mentions, which has no relationship to contract clause complexity captured outside of calls. Configuring the Sales Qualification Agent to compute the complexity index during lead scoring is incorrect because the Sales Qualification Agent evaluates leads before they become opportunities; it is not designed to compute or attach a risk factor to opportunities already in the forecasting pipeline. Manually entering the complexity index into the forecast comments field each week is incorrect because typing the index into a comments field manually is not an extension of the AI-driven deal-risk scoring at all, and it will not be picked up by the automated forecast narrative the way a properly wired structured field would be, since that narrative reads structured fields, not free text.