Remix Systems

Remy Team Vault

This page is for Jake, Davor, Honey and D'Andrew. Enter the passphrase from Andy's email.

Not quite. Check the email.
Remix Systems/Remy Healthcare

The Remy team vault

A company brain for Remy's go-to-market side. Plain text files the team owns outright, an AI that works them, and one place where the pipeline, the people, and what was said actually live together.

The short version

Where it stands

Two things changed since 14 August. Honey's Miami Beach packet and the last five sales calls arrived and have been processed, so the pitch and the coaching setup are now written from how Remy actually sells rather than reverse-engineered from pipeline notes. That was the biggest gap on the board and it is closed.

The other thing did not change. The repo invites sent on 14 August are still unaccepted, so the vault is still a private folder only Andy can open, and every other item waits behind it.

This page is the handover. The dependency board is the one to read before the call: it puts every open item on a single page with an owner and what it unblocks.

84
Organizations
Eugene's book plus every conference lead, one file each
51
Named leads
NACHC and Chemed, 37 with a named referrer
7
Skills
Prioritize, enrich, score a call, coach, report
0
Invites accepted
Two sent 14 Aug, both still pending
What changed on 19 August

The sales content was marked draft pending Jake because it had been reverse-engineered from pipeline notes rather than from Remy selling. Honey's 14 August delivery fixed that. The pitch and the coaching setup are rewritten from the real calls, including the winners-only economics, the 340B answer and the pro-forma close, plus a drill set built from objections that were actually raised. Both are now marked sourced from calls.

Still genuinely draft: the 30-60-90 targets, and the deal stages. Still owed: the full transcript text of the five calls. The written summaries carried most of it, and the verbatim text is what makes the objection handling exact.

The thing that has not moved in five days

Jake and Davor were invited to the repo on 14 August as admins. Checked again on 19 August, neither invite has been accepted. It is one click in a GitHub email and it is the top of the dependency board, because nothing else can start behind it.

What it does

What it does

CapabilityWhat it means on a TuesdayState
Prioritized hit listD'Andrew opens one file and knows who to call, in what order, and why they are warmneeds rerun
Call prepAsk for any account and get its history, the referrer, and what they said they neededlive
Call scoring and coachingEvery recorded call comes back scored on nine dimensions with one thing to repeat and one to changeneeds Granola
DraftingFollow-up written in the rep's voice, referencing real specifics. It never sendslive
Weekly reportJake gets a one-page view of touches, replies, meetings and scores without asking anyonelive

Two things it will not do

It will not send anything. Drafts stay drafts until a person sends them. It will not hold patient data. The no-PHI boundary is written into the vault's company file and repeated to the assistant at the start of every session. Business contact records are fine. Anything about a patient is not.

Where to go

The rest of this portal

Action items

What each person owns

Ordered by what unblocks the most. Everything above the line stops D'Andrew from working at all.

Repo access, re-checked 19 August

Jake (ysacks1) and Davor (orbiusrs) have admin invites waiting in their GitHub email, sent 14 August. Neither has been accepted, five days on, so the vault still cannot be opened by anyone but Andy. Honey has not been invited and does not need to be. D'Andrew cannot be invited until he creates a GitHub account. Davor, if orbiusrs is not your account, say so and the invite gets cancelled rather than left sitting.

Blocking

#ItemOwnerWhy it blocks
1Accept the repo invite. Check your GitHub email, it is already sentJake + DavorUntil it is accepted the vault still cannot be opened
2D'Andrew's Remy email addressHoneyHe cannot send from a Remy domain, still outstanding since 7 August
3D'Andrew creates a GitHub account, free, then sends the usernameD'AndrewIt is how he gets the vault on his machine
4Phone numbers for the lead listHoney + AndyJake wants calls first and not one lead in any list has a phone number
5Granola business account, plus a seat for D'AndrewJake + HoneyNo captured calls means no coaching, which is half the value

To make the outreach specific

#ItemOwnerState
6Miami Beach materials and the last five sales callsHoneydelivered, processed 8/19
6bFull transcript text of those five calls, exported not linkedHoneypartial, links are login-gated
7Remy value prop material, the one-pagers that go to clientsDavoranswered by the 8/14 packet
8The recorded overview made to brief D'Andrew before the conferenceDavoroutstanding
9The partial CRM export from the conference leadsHoneyoutstanding
10One client journey start to finish, for the deal stagesDavoroutstanding
11Sign off the pitch, now rewritten from your real callsJakeready for you
12Assign the Eugene accounts. Which are D'Andrew's, which stay yoursJakewaiting
13Set the handoff line. Where D'Andrew stops and a Remy expert takes overJakewaiting
On the lead count

Jake described roughly 100 conference leads. The list that arrived holds 51 named ones. The difference is most likely still sitting in the partial CRM that never got exported, which is item 9. Nobody should resolve this by picking a number.

Next step

Grab thirty minutes

The fastest path is one working session. D'Andrew's machine set up, recording sorted, and Jake reading the rewritten pitch out loud to say what is off. Full picture on the dependency board.

Book time with Andy