By the Academy of Life Planning
For decades, the financial advice model has operated on a simple premise:
To help you, we must first hold your data.
Your financial life—income, assets, liabilities, goals, vulnerabilities—is gathered, transferred, stored, and processed across a chain of systems: adviser CRMs, platforms, providers, paraplanning tools, and increasingly, AI.
This model made sense in a world where:
- Information was scarce
- Technology was limited
- Centralisation enabled efficiency
But that world has changed.
Today, the question is no longer how much data can a firm hold securely?
It is:
Should your financial life be aggregated outside your control in the first place?
The invisible expansion of data risk
In the traditional advice model, data does not simply move—it multiplies.
A client’s information may exist:
- On their own device
- Within an adviser’s CRM
- Across investment platforms
- Inside provider systems
- In email chains and document stores
- And increasingly, inside AI tools used for analysis or drafting
Each transfer creates another copy.
Each copy creates another risk surface.
What appears to be a single relationship between client and adviser is, in reality, a distributed data ecosystem—often with limited visibility for the client and fragmented accountability across the system.
The regulatory framework attempts to manage this through governance, policies, and oversight.
But structurally, the model remains the same:
Collect, store, replicate, and protect.
A different starting point
Local-first financial planning begins from a different assumption:
Your financial data should remain with you by default.
Instead of continuous data transfer and storage across multiple systems, the model is designed around:
- Local data retention (e.g. stored within the client’s own device or environment)
- Selective, purpose-driven processing
- Explicit consent at the point of use
- Minimal or no persistent third-party storage
For example, in tools like Navigator™ developed by the Academy of Life Planning:
- Your financial plan is stored locally in your browser
- No plan data is held on Academy servers
- Analysis is triggered only when you choose to use it
- Data is transmitted to a named processor for that specific purpose
- You can delete your data instantly at any time
This is not simply a technical variation.
It is a reversal of the default data flow.
From aggregation to permission
The difference between the two models can be expressed simply:
| Traditional Advice Model | Local-First Model |
|---|---|
| Data is aggregated and stored | Data is retained and selectively exposed |
| Continuous custody by firms | Conditional, event-based processing |
| Multiple copies across systems | Single source of truth (client-held) |
| Control via policies and rights | Control via direct user action |
In the traditional model, clients are granted rights over their data.
In the local-first model, clients retain operational control over it.
That distinction matters.
What changes when data stays local
1. The data footprint shrinks
When data is not continuously transferred and stored across multiple systems, the number of potential breach points reduces significantly.
Instead of protecting a growing network of replicated data, the system minimises what exists outside the client’s control.
2. Exposure becomes explicit
In many firms today, AI tools are already in use—often informally.
Advisers may paste client information into tools such as ChatGPT or other platforms to assist with analysis or communication. This activity is rarely visible to the client and may sit outside formal governance frameworks.
In a local-first model:
- Data transfer to AI is declared, not assumed
- The processor is named
- The purpose is defined
- Consent is captured at the point of use
AI is not avoided—but it is bounded and transparent.
3. The role of the firm narrows
In an advice-led aggregation model, firms become the primary custodians of client data.
This carries significant responsibility under frameworks such as Consumer Duty, SM&CR, and UK GDPR.
In a local-first model:
- The firm does not automatically hold the full dataset
- Its role shifts from data custodian to decision support provider
- Liability becomes more closely tied to process quality and client enablement, rather than blanket data ownership
This is not the removal of responsibility.
It is a redefinition of it.
4. Control becomes immediate
Under current frameworks, clients have rights:
- Access
- Rectification
- Erasure
- Portability
But exercising those rights often involves:
- Requests
- Delays
- Fragmented systems
In a local-first model:
- Data can be deleted instantly
- Storage is visible and understandable
- Control is exercised directly, not requested
This shifts control from a legal entitlement to a practical reality.
The deeper issue: agency
At its core, this is not a debate about technology.
It is a question of agency.
In a delegated advice model:
- The client provides data
- The adviser interprets it
- Systems process it
- Decisions are guided externally
In a local-first model:
- The client retains the data
- The client controls when it is used
- The client initiates analysis
- The adviser (if involved) acts as a second brain, not a central processor
This aligns with a broader shift already underway:
From delegation to participation
From intermediation to control
From advice to decision support
A more capability-dependent future
There is, however, an important trade-off.
When control increases, so does responsibility.
A system that relies less on institutional protection must rely more on:
- Clarity of tools
- Transparency of processes
- Capability of the individual
This is where education, structure, and support become critical.
Without them, local control risks becoming another form of vulnerability.
With them, it becomes something else entirely:
A foundation for restored human agency
Rethinking “safety”
The traditional assumption has been:
More professional control equals more protection.
But in a world of:
- Distributed systems
- Increasing AI usage
- Expanding data flows
That assumption deserves scrutiny.
Local-first financial planning suggests an alternative:
Safety may come not from holding more data centrally,
but from holding less—and making every use of it visible, consensual, and controlled.
The direction of travel
The regulatory framework is unlikely to rewrite itself for AI.
Existing principles already apply.
What is changing is the environment in which those principles operate.
As financial planning evolves, the key question is not simply:
- How do we protect client data?
But:
Where should that data live in the first place—and who should control it?
The answer to that question will shape the next generation of financial planning.
And it may determine whether the system continues to rely on trust…
or begins to build something more robust:
protection by design, grounded in agency.
Academy of Life Planning 