Our Richmond company has several divisions. Should each get its own Salesforce org?
Usually not. One org with shared accounts and unit-specific record types, layouts and sharing gives leadership a single customer view and avoids paying to sync separate systems. A multi-org strategy is justified by genuine differences, for example divisions with no shared customers, regulatory walls between them or incompatible release calendars. We assess that in discovery by mapping where customers, products and processes overlap.
How should a Richmond insurer implement Salesforce alongside its policy administration system?
Treat the policy system as the record for quotes, policies, endorsements and claims, and use Salesforce for producers, insureds, submissions in progress and service interactions. An integration brings policy status, premium and renewal dates onto the account so service staff and producers see the whole picture. Financial Services Cloud's insurance data model covers much of this without custom objects, which keeps future upgrades simpler.
What should our internal IT team own after go-live?
Settle ownership while the org is being designed, not at handover. Richmond companies with a corporate IT group usually keep user administration, security reviews and integration monitoring in-house, and bring in outside help for larger enhancements. We document the data model, automation and integrations as we build, pair your admins with our consultants during configuration, and leave a runbook for routine tasks. The people supporting the org then understand the reasons behind it, not just the settings.