Overview
The Advisory & Insurance Product Architecture Blueprint is a Salesforce configuration pattern for firms that sell and service multiple financial product lines. It defines record types, sales processes, support processes, page layouts, custom fields, and field dependencies for products including advisory services, disability insurance, financial planning, insurance, and variable annuities.
Business Problem
Financial services organizations often start with a generic Opportunity setup, then quickly run into problems as different product lines require different data, stages, service processes, and reporting. A variable annuity does not follow the same lifecycle as disability insurance or financial planning. Teams need to capture product-specific information such as premium, death benefit, riders, registration type, split allocations, and commission options without cluttering every sales record with irrelevant fields.
How It Works
The accelerator provides a pre-configured Salesforce architecture that separates distinct financial product paths. Record types and sales processes align to the type of product being sold. Support processes and page layouts can be tailored to the documents, approvals, status tracking, and servicing requirements of each product. Field dependencies guide users to the correct data capture points, reducing the need for duplicated objects or ad hoc fields.
Where This Fits
This accelerator fits wealth management, insurance, advisory, and financial planning firms that need product-specific CRM architecture. It gives implementation teams a reusable starting point for firms with multiple financial lines, reducing setup effort while allowing each organization to adjust stages, fields, page layouts, and service processes to match its own product operations. For reuse, the implementation should start by confirming the object model, required fields, record types, status values, ownership rules, and security model in the target Salesforce org. The existing pattern can then be adjusted for naming, page layout placement, validation rules, reporting needs, and integration points. Sample records should be used to test the automation path, exception handling, and user-facing screens before rollout. This keeps the accelerator grounded in the original delivered pattern while allowing the details to fit the new organization and its operating process fully.