Asked and answered.

The file of record for what a financial advisor knows about a household. The custodian holds the numbers; the CRM holds the records; Tenuit holds your judgment — dated, signed notes — and assembles briefs, stories, and answers that cite them, line by line. The name is Latin: he or she held.

No. Tenuit reads your CRM, your custodian, and your calendar — it does not replace them. It replaces the standalone meeting note-taker and the prep documents you assemble by hand. Keep the CRM you run; Tenuit fills the systems column from it so you stop re-typing what it already knows.

Collectors read the systems you already run: Charles Schwab for accounts and positions, Microsoft 365 for email and calendar, Salesforce and your CRM for households, Zocks for meeting transcripts. Fidelity, Redtail, Orion, Zoom, and Plaid are in pilot. Collectors are read-only by construction — they fill the first column and cannot write a note.

No line ships without a source. Assembly drafts — in your words, from your notes and the records it reads — and assembly is never a source. Quotes are verified deterministically, string-matched with stored character offsets, not model self-grading. When the file cannot answer, it says so: nobody has asked him — that question is yours.

Both promises hold at once — that is the honest split. The firm keeps the working file: every approved artifact with its review trail, every system record, the working join that keeps briefing whoever holds the relationship next. The advisor keeps her authored notes — attributed, exportable in documented JSON/CSV, contractually hers.

The file still briefs her successor — Eliana’s name included. She leaves with her authored notes, her name on every one. Clients leave when the person who knew them does; the split exists so that what mattered is already in the file when that day comes.

Never. Client transcripts, notes, and artifacts are not used to train shared or foundation models; per-firm voice tuning stays per-firm. It is one of the commitments we put in writing — the security page lists the rest.

A per-advisor monthly seat for the file, the console, and capture in every mode; a firm tier adds the compliance queue, disclosure controls, retention policy, and escrow. Priced like what it replaces — your note-taker and the hour before every review. The pricing page has the tiers; the pilot pack has the numbers.

Leave an address in the form below. We write back within a day — a person, not a sequence — with a 20-minute demo on households shaped like yours, the security review pack, and pilot pricing: five advisors, 90 days, full firm features, export working from day one.

Every artifact carries a disclosure block, an immutable version history, and a named approval; rejections require a written note, recorded forever. Retention follows the firm’s policy — a switch your CCO sets, not one we assume. RIAs answer to the SEC and the states, and the file’s native shape is the one an examiner asks for: dated, signed, traceable.

The export works on day one — that is the test of it. Advisor notes export at any time in documented JSON/CSV without vendor approval or fees, verifiable quarterly. Firm data is escrowed with an independent agent and releases on termination or vendor failure. If after ninety days the file has not earned its seat, the export takes everything you wrote with you.

SOC 2 Type II is in progress; the security review pack carries the current status. What we hold today is in writing on the security page — export, escrow, no-training, subprocessors, retention — and if a promise there is not in your contract, treat it as not made.