Run retirement planning conversations inside Salesforce
Model income, withdrawals, taxes, projected net worth, first deficit year, and funding gaps on the household Financial Plan record. Advisors can review retirement readiness where client data, tasks, meetings, and service workflows already live.
Lifetime cash flow, plan health, and funding gaps on the Financial Plan record — ready for a review meeting.
Sample household data for illustration only — not a client record.
Why retirement plans go stale
Assumptions live outside CRM
Retirement age, withdrawal order, and spending rules get updated in an external planning portal or a spreadsheet — then sit stale in Salesforce while account values and tasks keep moving.
Cash flow gets reduced to a stale PDF
Clients review last quarter's illustration while Salesforce already holds new balances, income changes, and the meeting notes your team logged yesterday.
Funding gaps surface too late
First deficit year and total funding gap stay hidden until someone re-runs the external planner — often days after the review conversation.
What advisors can answer in a client meeting
Each question maps to a projection-backed view on the Financial Plan record — not a one-off spreadsheet.
Can this household retire earlier?
In Salesforce What-If Simulator and plan health show whether an earlier retirement age still funds spending goals.
What is the first deficit year?
In Salesforce Plan health surfaces the first year expenses exceed income — before the client hears it from a stale PDF.
How large is the projected funding gap?
In Salesforce Total funding gap and surplus-gap charts quantify shortfalls across the plan horizon.
Will income cover planned retirement spending?
In Salesforce Lifetime cash flow and retirement insight cards compare average income and expenses after retirement.
Should we adjust savings, withdrawals, or spending?
In Salesforce What-If controls model trade-offs in session — results stay on the plan record.
Should we review Social Security, CPP/OAS, Roth conversion, or tax exposure?
In Salesforce Dedicated explorers plus tax rate and IRMAA on the metric watchlist connect strategy to projected balances.
Retire at 65 vs 63 on a sample household
Sample household data for illustration only — not a client record.
After a baseline Run Calculation on the sample Chen household, the advisor opens What-If to test retiring two years earlier. All values below are illustrative — not a client record.
Retire at 65
- Retirement age
- 65
- First deficit year
- 2044
- Funding gap
- $418,000
- Income coverage
- Income covers spending through 2043
Baseline plan funds retirement spending with a modest gap late in the horizon.
Retire at 63
- Retirement age
- 63
- First deficit year
- 2041
- Funding gap
- $612,000
- Income coverage
- Income falls below spending three years earlier
Sample result: retiring at 63 moves the first deficit year earlier and increases the projected funding gap.
Sample result: Retiring at 63 moves the first deficit year from 2044 to 2041 and increases the projected funding gap from $418,000 to $612,000 on the illustrative Chen household.
Note: What-if overlays are analytical until applied to baseline inputs and confirmed with Run Calculation.
Why retirement planning data belongs in Salesforce
Retirement readiness becomes governed Salesforce data — so advisors plan, review, and act without a second system.
Readiness metrics, first deficit year, funding gaps, income, expenses, assets, debt, tax context, and withdrawal assumptions stay on Financial Planner objects — not a vendor planning database.
Open plans from the same system where relationships, tasks, meetings, reviews, and service workflows already live.
Leadership can filter households by funding gaps, retirement risk, rollover opportunities, Roth opportunities, education funding needs, debt pressure, or review urgency.
Salesforce admins and compliance teams retain permissions, sharing, auditability, and data residency controls you already operate.
No external planning database, duplicate entry, middleware sync, or copied sensitive client data.
Sample household data for illustration only — not a client record.
How retirement planning runs in the Financial Plan workspace
Advisors build the household plan once, run projections, and review retirement outcomes without exporting data to another vendor database.
Guided plan setup
Create New Financial Plan walks through basics, owners and ages, withdrawal rules, and tax context before you trust retirement projections.
Run Calculation on the plan record
Projection runs refresh retirement insights, cash flow charts, and plan health — results are saved to the Financial Plan record with run history attached.
Retirement insights and explorers
Projected net worth, average income and expenses, surplus-gap analysis, tax and IRMAA watchlist metrics, Monte Carlo, and what-if explorers sit in the same plan navigation.
Ages, accounts, income, and expenses on the Financial Plan
Run Calculation refreshes plan health and cash flow
Income, expenses, funding gap, and net worth charts
What-if, Monte Carlo, or plan updates in Salesforce
Sample household data for illustration only — not a client record.
How the retirement workflow runs in Salesforce
From household records to advisor next steps — without a copied spreadsheet or external planning database.
Capture household records
Link Contacts as owners, then enter ages, accounts, income, expenses, and money flows on Financial Planner records — or import from a plan CSV.
Set planning assumptions
Configure return, inflation, tax, and withdrawal assumptions during plan setup and Plan Preferences.
Run Calculation
Projection runs refresh retirement insights, cash flow, net worth, and plan health. Results are saved to the Financial Plan record with run history attached.
Review and explore
Advisors walk through insight cards, lifetime cash flow, and plan health — then open Monte Carlo or What-If for follow-up questions in the same meeting.
Limitations
Planning-oriented analysis — not tax filing, trade execution, or custodian instructions. Complex cross-border situations need qualified advice.
Planning data protected by Salesforce Trust
Financial Planner is a managed Salesforce package. Sensitive household data inherits the platform controls your IT and compliance teams already govern.
Household records, projections, and explorer results never leave Salesforce.
Packaged FinPlan permission sets sit on profiles, sharing, and field-level security you already run.
Advisors sign in with the SSO and MFA your org requires — no separate planning login.
Financial Planner has passed Salesforce's required AppExchange security review.
Common questions
Does client planning data leave Salesforce?
No. Household records, projection results, and explorer outputs stay in your Salesforce org. Financial Planner is a managed package — not an external planning portal and not a copy of client data in another cloud.
Can advisors compare retirement scenarios during a meeting?
Yes. What-If Simulator, Monte Carlo, and related explorers run on the same Financial Plan record so advisors can test retirement age, spending, and savings without rebuilding the household elsewhere.
Does it support household plans with spouses or partners?
Yes. Joint plans link primary and spouse Contacts as owners. Ages, accounts, income, and retirement assumptions stay on one Financial Plan record.
Can admins control access with Salesforce permissions?
Yes. Packaged FinPlan Admin and FinPlan User permission sets sit on profiles, sharing, and field-level security you already run — no separate planning login.
Can leadership report on households with funding gaps?
Plan health, first deficit year, and funding gap fields live on Salesforce records — so teams can filter, report, and prioritize reviews from the same platform they use for pipeline and service.
How is this different from an external planning portal?
External portals store household data in a vendor database and sync (or rekey) back to CRM. Financial Planner keeps planning inputs and results on governed Salesforce records — no duplicate entry, middleware sync, or copied sensitive client data.
Does it support Social Security, CPP/OAS, Roth, and tax-aware planning?
Yes. Tax context is captured during plan setup, insights include tax rate and IRMAA, and dedicated Social Security, Roth, and CPP/OAS explorers sit in the plan navigation alongside retirement cash flow.
Does it model taxes in retirement?
Yes. Tax context is part of plan setup, and insights include tax and IRMAA views fed by packaged reference data for US and Canada households.
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