Remix Systems/Current system build

How it was built

Layer by layer, what is in the vault today, where every piece came from, and what is honestly still a draft. Nothing here is invented, and where a source was thin it says so.

Repo RemixSystems/remy-vault · head ca3c17f · 14 August 2026

At a glance

The numbers

Org entities

Eugene's 33 plus 49 new stubs from the conference list

Named leads

Of 55 rows with data, 4 are fragments

Missing email

45 of 51 have LinkedIn, so enrichable

Have a phone

No source carries one. Top blocker

Commits

Seed to reconciliation

Invites pending

Jake and Davor, sent 14 Aug

The layers

Six passes, in order

The seed

shared core, team mode

Forked from the Remix Systems vault seed, so fixes made anywhere merge forward
Team mode: company truth in a shared tracked file, each member's private config gitignored so nothing collides
A guard on the shared files that asks rather than blocks, and fails open
Folder convention identical to every other vault Remix Systems runs

Remy is the first team instance of the seed. Everything before this was single-operator.

Company truth

CLIENT.md, sacred

What Remy does, the market, and the ~2,000 FQHC universe
The no-PHI boundary, written once and repeated to the assistant at the start of every session
Team index pointing at each member's own file

This is the file that makes the assistant refuse the wrong thing without anyone having to remember to tell it.

The pipeline

two lists, one shape

Eugene's book, 33 accounts, imported with stage and history intact
The NACHC and Chemed list, 51 named leads, with the state column split into clean city and state
Every account is its own file carrying stage, last activity, and the verbatim note from whoever met them
Every person and company cross-linked, so "how do we know this account" is answerable

Counting caveat, recorded in the vault: the sheet has 1,001 rows, 55 hold data, 51 are real leads. A naive row count overstates it twentyfold.

The sales knowledge layer

draft pending Jake

A canonical pitch: one-liner, the problem, proof points, five qualifying questions, objection responses
A nine-dimension call rubric with literal 1 to 5 anchors, adapted for the FQHC motion
A four-gate qualification scorecard, scored 0 to 8, with action thresholds
An append-only lessons log that feeds revisions back into the pitch

Assembled from pipeline history, not from Remy selling. Every section is flagged draft inside the vault. This is the layer the Miami Beach call recordings fix.

The working surfaces

what the rep and the manager touch

Hit list, the prioritized queue, generated from the sources rather than hand-maintained
Six plays, each carrying its own counters so the system can rank what actually works
Activity log, one row per touch, which doubles as the hourly work record
Sales dashboard, Jake's weekly page
Onboarding ladder and a 30-60-90 for D'Andrew

Seven skills drive these: prioritize the list, enrich a lead, score a call, run a coaching review, write the weekly report, analyze which plays win, capture a lesson.

The correction pass

after reading the 7 August call

The build had assumed an email-first motion, because no source data carries a phone number
Jake had actually said calls first, email as the follow-up, and D'Andrew has never sold in writing
Motion reversed: a call play is now primary, the email plays follow it
Jake's instruction to triage Eugene's book first restored as its own tier
Missing phone numbers reclassified from a constraint to the top blocker

The original reasoning was sound on the evidence available. The evidence was incomplete, because the kickoff call never reached the transcription tool and sat unread for six days.

Honest status

What is live, what is draft, what is blocked

Component	State	Note
Vault structure and rules	live	Boots, enforces the boundary, guards the shared files
Pipeline data and people graph	live	84 orgs, cross-linked
Skills and coaching agent	live	Runs today for anyone with the repo
Call rubric	live	Ported from a working system, market notes are draft
Coaching setup and drill set	rewritten 8/19	The quiz mode D'Andrew asked for, running real objections from real calls
Canonical pitch and objections	rewritten 8/19	Now sourced from Remy's real calls: winners-only economics, the 340B answer, the pro-forma close. Jake still signs it off
Play copy	draft	Structure is right, the words need Jake and D'Andrew
Hit list ordering	stale	Generated before the phone-first correction. Reruns once Jake assigns the Eugene accounts
30-60-90 targets	draft	Structure real, every number a placeholder. Guessing them would make the reports lie
Rep's voice profile	blocked	Normally learned from sent mail. D'Andrew has never sold in writing, so it gets built by interview and from his own call transcripts
Call capture and scoring	blocked	Needs the Granola account and D'Andrew's number registered
Phone numbers	blocked	Zero across every source, and the motion is calls
Bot on the phone	designed, not built	Second container on Jake's existing server, own vault, one bot per person. Plan on the dependency board

Why so much said draft, and what changed

The alternative was to write a confident pitch, hand it to a new rep, and let him find out on a live call with a CEO that Remy does not actually say it that way. Labelling the draft was the cheaper failure.

On 19 August the biggest of those labels came off. Honey's 14 August delivery gave us Remy actually selling, so the pitch and the coaching setup are no longer reverse-engineered. What still says draft is what still genuinely is: the numbers, and the deal stages.

Provenance

Where the content came from

Source	Fed	Date
Eugene's pipeline PDF	33 org entities, stage history	6 Aug
NACHC and Chemed sheet from Honey	51 leads, referrers, revenue, patient volume	10 Aug
7 August kickoff call transcript	The motion, the lead order, D'Andrew's profile, the ask list	13 Aug
Miami Beach materials and five sales calls	Not yet processed. This is what makes the pitch real	14 Aug
Remy value prop docs	Still outstanding	—

The kickoff call is worth a note. It was recorded, but never reached the tool the vault reads from, so the build ran six days on an incomplete picture. That is exactly the failure mode this system exists to remove, which is why the recorder setup is a blocking item rather than a nice-to-have.