Plain text files on the team's own machines. Claude works them, Obsidian browses them, GitHub backs them up. No app to log into, no vendor holding the pipeline.
Thirty accounts he had worked for a year. A hundred conference conversations spread across three or four events and half-finished in a CRM nobody owns. A new rep starting cold, with no email address, no tools, and no way to know what was already said to anyone.
That is not a CRM problem. A CRM stores fields. What was missing is the context: who referred whom, what they actually said they needed, what Remy sounds like when it sells well, and what happened on the last call. This holds all of it in one place, in files the team owns, and lets an AI work them.
There is no interface to learn. D'Andrew opens the folder and types in plain English.
| He says | It does |
|---|---|
| "What should I work today?" | Reads the hit list and the last three days of activity, names five accounts and the next physical step on each |
| "Prep me for Golden Valley" | Pulls the account history, the referrer, the verbatim need from the conference, and what changed since |
| "Just got off with Mercy Medical" | Logs the call, updates the stage, drafts the follow-up in his voice, and never sends it |
| "Score that call" | Nine dimensions, one thing to repeat, one thing to change, both quoted from what he actually said |
| "Quiz me on objections" | Plays an FQHC CEO, throws the hard questions, scores the answers |
Jake gets the same surface, pointed at the week rather than the day. One page: touches, replies, meetings, call scores, and what is aging.
Plus a sales knowledge layer (the pitch being tested, a nine-dimension call rubric, a four-gate qualification scorecard, an append-only lessons log), a coaching agent, an onboarding ladder for D'Andrew, and a dashboard for Jake.
| Rule | Why it exists |
|---|---|
| No patient data, ever | HIPAA. The boundary is written into the company file and repeated at the start of every session. Business contact records are fine; anything about a patient is not |
| It never sends | Drafts are drafts. A person sends |
| Never blend two accounts | Before drafting for anyone it reads that one account's file and nothing else. Remy's pipeline carries signed agreements and legal structuring; one account's terms must never surface in another's email |
| It says "I don't know" | Every claim points at a file, a connected tool, or a link. Blanks stay blank rather than getting filled with a plausible guess. A confident wrong answer costs more than a missing one |
Right now this is the layer underneath. It holds truth and answers questions; it does not draw pipelines or replace Salesforce. If the team later wants a visual board on top, one can sit on this data without the data moving.
The deal stages in it today are six sensible placeholders. Making them real needs one complete client journey, first contact to onboarded, which is Davor's point and the right one.
The structure and the data are real. The sales content is a strong first draft assembled from pipeline notes rather than from Remy actually selling, and it is labelled that way inside the vault so nobody mistakes it for approved.
Three things convert it: Jake reviewing the pitch, the recordings of Remy's best calls (arrived 14 August), and phone numbers so the rep can make the calls the whole motion assumes.