Add native financial planning to Financial Services Cloud
Install Financial Planner as a managed package beside FSC household records — so advisors plan, review, and follow up in the same Salesforce org without exporting clients to a separate planning portal.
Managed package — own packaged objects, Lightning experiences, and FinPlan permission sets beside your FSC data model.
FSC without a native planning app
Household in FSC, plan somewhere else
Advisors navigate FSC relationships in Lightning, then export clients into an external planning portal — outside the sharing rules compliance already reviewed.
Integration tax on every refresh
Keeping CRM and planning aligned means custom mappings, batch jobs, and exception handling — while Salesforce already holds the household context.
Planning insights never become CRM intelligence
Funding gaps, retirement readiness, and review urgency live in a portal — so marketing, service, and leadership cannot segment or report on planning needs in Salesforce.
Another vendor in the security review
Each external planning database is another processor for balances, tax detail, and beneficiary-level data your compliance team must evaluate.
Why native planning belongs beside FSC
Financial Planner adds a planning layer without replacing FSC — same org, same permissions model, and planning data your firm can use for advisor workflow, reporting, and follow-up.
Install Financial Planner beside FSC — own packaged objects, Lightning experiences, and FinPlan permission sets without overwriting FSC data model objects.
Implementation connects FSC household pages to Financial Plan records so advisors open planning from the relationship they already navigated.
Household plans, projection runs, and explorer results stay on governed records — not a vendor planning database or exported PDF workflow.
Reduce custom sync jobs and middleware just to refresh retirement projections — advisors update and run calculations on the plan record in Lightning.
Permissions, sharing, field-level security, and audit history apply to Financial Planner records like the rest of your FSC org.
Funding gaps, plan health, and retirement readiness become Salesforce data leadership can report on — not portal-only views.
Sample household data for illustration only — not a client record.
What connects vs what you enter
Financial Planner uses its own packaged objects. Being in the same Salesforce org does not silently copy FSC balances into a plan — here is what connects automatically, what you map at implementation, and what advisors enter.
| Category | What happens |
|---|---|
| Automatic today | Existing Contacts can link as primary owner and spouse on the Financial Plan. Users, permission sets, sharing, and audit stay on the Salesforce model you already operate. |
| Mapped at implementation | FSC Accounts, Contacts, households, page layouts, related lists, and optional automation can connect to Financial Planner records so advisors navigate one relationship context. |
| Entered or imported on plan records | Accounts, assets, real estate, income, debts, expenses, money flows, and tax context — via the Financial Planner Lightning UI or plan CSV import/export. |
| Not automatic | FSC financial account balances and holdings are not silently copied into plan inputs unless your firm implements specific automation or import processes. |
How implementation mapping works
From package install to advisor workflow — planning beside FSC without replacing your CRM data model.
Install the managed package
Financial Planner adds its console app, packaged objects, Lightning pages, and FinPlan permission sets — without overwriting FSC objects.
Connect FSC household context
Your implementation team maps FSC household pages, related lists, and lookups so advisors open Financial Plan records from the same relationship view.
Build and calculate the plan
Advisors enter or import financial detail on Financial Planner records, then Run Calculation refreshes projections, plan health, and insight charts in Lightning.
Use results across Salesforce
Planning metrics on governed records support advisor reviews, tasks, segments, reports, and firm-wide workflows — subject to your org configuration.
Use planning data across the Salesforce platform
When planning lives beside FSC in the same org, wealth and advice teams use projection results for growth, service, and leadership workflows — not just advisor meetings.
Advisor dashboards for planning risk
Surface households with funding gaps, stale plans, retirement readiness issues, or unresolved goals in list views and dashboards advisors open daily.
Marketing and targeting from plan signals
Build outreach around retirement window, education funding needs, tax exposure, Roth opportunities, or plan health — using metrics on Salesforce records.
Tasks and flows on planning changes
Trigger Salesforce tasks or automation when Run Calculation surfaces a new funding gap, stale projection, or review opportunity.
Executive reporting across the book
Leadership dashboards show planning opportunities, review backlog, and retirement-risk concentration without exporting portal data.
Segmentation by household and planning need
Segment by household, advisor, assets, retirement date, cash-flow risk, tax context, or goals — from governed Financial Plan records.
Better handoffs across the firm
Advisors, associates, operations, marketing, and compliance reopen the same Financial Plan context — not disconnected portal exports.
Security, permissions, and governance
Planning data stays inside the Salesforce control plane your FSC team already operates — with honest limits on what connects automatically.
- Packaged FinPlan Admin and User permission sets govern who can view, edit, and run calculations on planning records.
- Sharing rules, field-level security, and audit history apply to Financial Planner data like FSC Accounts, Contacts, and household records.
- Financial Planner uses its own packaged objects — it does not overwrite FSC objects or silently copy holdings without firm-specific implementation.
- Planning outputs are estimates for advisor workflow — not trade recommendations, tax advice, or custodian instructions.
- Compliance reviews one data residency model instead of adding a separate planning vendor database to your control plane.
Common questions
Do we have to use Financial Services Cloud?
No. Financial Planner also supports Sales Cloud. FSC teams benefit most when households, relationships, and service workflows already live in Salesforce.
Will Financial Planner overwrite FSC objects?
No. Financial Planner uses its own packaged objects. FSC Accounts, Contacts, and household records relate to Financial Plan records through implementation — not object overwrite.
Does CRM data populate the plan automatically?
Not by default. Existing Contacts can link as plan owners. Accounts, income, balances, and financial detail are entered on Financial Planner records or imported — unless your firm implements custom automation.
Can we map FSC household pages to Financial Planner records?
Yes. Implementation teams connect FSC household page layouts, related lists, and optional automation so advisors open Financial Plan records from the same relationship context.
Can planning data be used in Salesforce reports and dashboards?
Yes. Financial Plan records and planning metrics can feed reports and dashboards — so leadership sees funding gaps, stale plans, and review opportunities across the book of business.
Can Marketing Cloud or campaigns use planning segments?
When planning results live on Salesforce records, your admin can expose segments for campaigns — retirement window, education funding, tax exposure, Roth opportunities, or plan health — subject to your org's integration design.
Does client data leave Salesforce?
No. Household planning records, projection results, and explorer outputs stay in your org. Financial Planner is a managed package — not an external planning portal.
How do permissions and sharing work?
Packaged FinPlan Admin and User permission sets, sharing rules, field-level security, and audit history apply to planning records the same way they apply to FSC and CRM data.
Is this a managed package?
Yes. Financial Planner installs as a Salesforce managed package with its own console app, objects, Lightning pages, and permission sets — AppExchange security reviewed.
Is this compatible with Sales Cloud too?
Yes. The same package supports Sales Cloud and Financial Services Cloud. FSC adds richer household context; Sales Cloud teams still get native in-org planning without a sidecar portal.
See Financial Planner in your Salesforce workflow
Request early access to evaluate household records, projections, insights, and explorers before the public AppExchange listing goes live.
- Public AppExchange listing coming soon — request early access to pilot in your org.
- Passed Salesforce AppExchange security review.
- Stratus Cloud Solutions has built Salesforce-native apps since 2009.
- Documentation is available for evaluator walkthroughs. Open docs