Planning should begin with architectural assessment rather than immediate feature activation. Salesforce instructs implementation teams to review out-of-the-box Agentforce Financial Services capabilities and compare them with current business needs. This establishes what the platform already provides and identifies where configuration or additional solution work is genuinely required.

Integration planning is equally fundamental. The implementation team should identify required connections to transactional systems, external data sources, custodians, and other platforms during implementation design. Financial institutions typically depend on core banking, portfolio, lending, policy, payment, or external-data systems, so these integration requirements can materially affect the data model and solution architecture.

The team should also evaluate whether requirements extend beyond preconfigured capabilities and require advanced customization. The preferred approach is to minimize unnecessary customization and assess available standard features before deciding how much additional development is appropriate.

Option A represents implementation execution rather than planning. Enabling Person Accounts and assigning licenses occurs after the appropriate architecture, data model, and user-access strategy have been defined. Option B is a valid design consideration, but detailed field and layout modifications follow the higher-level assessment of platform fit.

The planning priority is therefore to assess standard capability fit, integration dependencies, and the genuine need for advanced customization.