EMINENCE VSP Talk to the architect

The Salesforce partner built for banking — lending journeys live this quarter, not eighteen-month programmes.

LinkedInEmail
Industries
Company
RETAIL · ONBOARDING· 5 min read · by Srinivasa, Founder & Architect · published Oct 2025, updated Jun 2026

Householding in Financial Services Cloud: one customer, whole household

Most retail banks onboard accounts. Financial Services Cloud onboards relationships — and the difference shows up in conversion, service time and share of wallet.

Accounts versus relationships

Most retail banks onboard accounts. The customer gets a current account, then — as far as the systems are concerned — a stranger with the same surname gets a savings account, and an unrelated person at the same address gets a mortgage. Every product priced alone, every risk seen alone, every opportunity invisible. FSC onboards relationships, and the difference shows up everywhere from conversion to credit.

What householding in FSC actually changes

One person, one record. Person Accounts make the customer a single entity across products and channels — the precondition for everything else.
The household is data. The Actionable Relationship Center maps the family — partners, dependants, joint products — as records and relationships, not as a note in a call log.
Consent is designed in. What may be seen across the household is governed at person level — the adviser sees what consent permits, automatically, rather than what curiosity finds.
Intelligence gets context. Einstein next-best-action grounded in the household stops suggesting a first-time-buyer mortgage to someone whose partner already holds one with you.

The mortgage that nearly went elsewhere

Without itA customer asks about mortgage rates. The banker sees one current account, quotes the standard rate, and the customer says they'll think about it. The partner's maturing fixed-term deposit — at your bank — never enters the conversation.
With itThe same conversation, but the record shows the household: the partner's deposit maturing in six weeks, the joint savings history, the child's account opened last year. The banker offers the rate the relationship justifies — and a reason to bring the deposit into it.
A bank that can't see the household is pricing risk and opportunity one account at a time.

The honest caveat

Householding is a consent design problem before it is a data model. Seeing the family must be permissible, not merely possible — which means the consent architecture is designed with the household model, not bolted on after the first complaint. We treat the two as one workstream, because they are.

Three questions for your retail platform

Can a banker see a customer's household today — in one screen? Not in three systems and a guess.
Is the joint product joint in the data? Or duplicated against two unconnected people?
Would your consent records survive the question "why could you see that?" The household view must come with its permission slip.

How Eminence VSP helps

Retail onboarding and householding on Salesforce FSC is week-one work in our retail engagements: Person Accounts, ARC relationship maps and household rollups your pricing and credit teams can query. Start at Retail Banking or talk to the architect.

S.
Srinivasa
Founder & Architect, Eminence VSP — the person who scopes and delivers these builds.
Share on LinkedIn →
Keep reading

More straight answers.

AI · AGENTS

Agentforce for banking in 2026: what’s actually ready, and what to deploy first

Read the article →
AI · DATA

What is Data 360 for banks? The intelligence layer under your agents, explained

Read the article →
AI · GOVERNANCE

AI agent auditability in banking: answering “how did the agent decide?”

Read the article →

Let’s talk.

One conversation with the architect — and a clear view of what your bank could ship next quarter.

Talk to the architect