What enterprise buyers are actually deciding
The situation is familiar. A division has a corporate CRM available to it and does not use it properly, because saving a record takes eleven fields and four of them require information nobody has at the point of the conversation. The real pipeline therefore lives in a spreadsheet, and the official system is updated shortly before each reporting deadline by someone who was not on the calls.
The decision is not simple versus sophisticated. It is governed versus ungoverned. If the team's working pipeline is already outside the corporate system, the choice on the table is whether that reality gets access control, an audit trail and an owner, or whether it stays in a spreadsheet attached to an email thread.
Mandatory fields are where enterprise CRM adoption dies
Each required field is defensible on its own and was added to answer a genuine question. Collectively they push data entry out of the moment of the conversation and into a retrospective exercise, at which point the detail is invented rather than recorded. Less data, entered truthfully, is usually worth more than more data entered afterwards.
Scope is the whole risk
A bounded departmental deployment with a written data boundary and a named owner is a manageable arrangement. The same tool adopted informally by four teams with no boundary is the thing your governance function was right to worry about. The difference is entirely in the paperwork, and the paperwork is short.