Requirement analysis is supposed to be done by experts of the Dynamics 365 solution. This expert could be an external advisor/partner or an internal team member and should bring in their much-needed experience alongside solution guidance options.
Customers must push their advisors/partners/consultants to seek solution options, both in the form of workarounds and in the form of customizations or extensions when a requirement can't be met with out of the box capabilities. Even when requirements are envisioned to be met out of the box, their mapping must be documented and should be validated during the learning/prototyping phase in the CRP approach.
When a requirement can't be achieved with out-of-the-box capabilities in a Dynamics 365 solution, then the solution analysis stage starts. Poor analysis will add more time, effort, and cost to the project...
