Existing Salesforce environment review for opportunities and constraints
Key Takeaway
Review the existing org for opportunities and constraints before you design. Salesforce recommends standard UI components, such as Actionable Relationship Center, over the Aura-based managed package components whenever possible. Before you enable a new feature from Salesforce Go, manually review its impact on existing customizations.
A consultant reviews the customer's current Salesforce org before recommending Agentforce Financial Services capabilities. The review shows how the org is used today, what can be reused or improved, and what will limit the design. You compare the current state to the desired future state. Then you check customizations, data model choices, licenses, integrations, and known product limitations.
Why review the existing org
Analyzing the customer's Salesforce environment for opportunities and constraints is a core discovery task. Part of the task is learning how the customer uses and benefits from its Salesforce products, which establishes the current state.
Start with project history, also called project orientation. Project history is background on the existing systems, design, requirements, and business processes. Knowing the project history keeps you from repeating work already done or reopening decisions already made.