What is folder-native AI for advisors
Folder-native AI is an AI brain that lives inside an advisory firm's existing file storage — Microsoft 365, Google Drive, or iCloud — instead of inside a third-party SaaS portal. The firm's clients, voice, and workflows are markdown files in a shared folder, and the model reads them directly. Nothing leaves the firm's own stack.
Why it matters for an RIA
Most advisor AI products are SaaS portals. The firm uploads data into a vendor's cloud, the vendor's model reasons over it, and the firm rents access. Folder-native flips that — the data never leaves the firm. The model comes to the data.
What's in the folder
- Clients. One markdown file per household — goals, last touch, planning state, account map.
- Voice. Every letter, blog, and email the firm has ever published, indexed for the model.
- Playbooks. Plain-text prompts for meeting prep, content drafting, lead scoring, IPS reviews.
- Compliance. What the brain must always say, must never say, and who reviews what.
How it differs from SaaS AI
| SaaS AI tool | Folder-native install | |
|---|---|---|
| Where data lives | Vendor's cloud | Firm's existing storage |
| Where the brain lives | Vendor's portal | Markdown files in the folder |
| Who owns the prompts | Vendor | Firm — they're plain files |
| What you keep if you leave | Exported PDFs, maybe | Everything — the brain stays on the firm's drive |
| Compliance posture | New vendor in the data flow | No new data location — stack is unchanged |
Why "folder-native" is the term
The folder is the brain. There's no separate platform to log into. A team member opens the same shared folder they already use for client documents, and Claude reads it. The architecture is intentionally boring because boring is what compliance accepts.
What you need to run it
A Microsoft 365, Google Workspace, or iCloud account the firm already pays for. A Claude Team subscription on the firm's account. That's the stack. No new vendor, no new data center, no new compliance review.
What the day-to-day actually looks like inside the firm
The team opens the same file structure they already use for client work. Inside the folder there is a /clients directory with one markdown file per household, a /voice directory with the firm's published writing, a /playbooks directory with the prompts that drive each workflow, and a /compliance directory with the must-say and must-not-say rules. When an advisor wants meeting prep for the Hendersons, they open Claude inside the folder and say "prep for Henderson review Thursday" — Claude reads the Henderson client file, the planning state, the last meeting notes, and the firm's voice, and produces a prep brief in the firm's tone. Nothing was uploaded. Nothing left the firm's storage. The interaction is no different in compliance posture than an associate opening the same files in a Word document.
The same pattern runs unattended for scheduled work. The Touch Point Engine reads which households are due for a check-in, drafts the outreach in voice, and queues it for principal approval — all using the same folder. No vendor portal sits between the work and the firm.
Where folder-native AI is a poor fit
It is the wrong fit for firms that don't actually use a shared cloud drive — a few small RIAs still keep client files on a local server with no cloud sync, and folder-native assumes M365, Google, or iCloud is already in place. It is also the wrong fit for firms that want a turn-key SaaS interface their team can use without any folder convention at all; folder-native rewards firms whose team is comfortable opening a shared folder and reading what's in it. For everyone else — which is most modern RIAs already living in M365 or Google — the folder is the most defensible place to put the brain.
Sources
The folder is the brain. Free AI visibility audit →