One board. Every open thing, who owns it, and what it unblocks.
Nothing further down the chain works until the link above it clears. Everything else on this page is parallel work that can happen any time.
The invites are sitting in your GitHub email. Until they are accepted, Andy is the only person who can open the vault, so every demo is a screen share and nobody can correct anything themselves.
The GitHub account is free and takes two minutes. Send the username and the invite goes out the same day. The Remy email address is separate and matters for a different reason: he cannot send outreach from a Remy domain without it, so every follow-up he writes is stuck.
Jake's instruction on 7 August was calls first, then follow up by email. Not one lead in any list we hold carries a phone number, and the 14 August packet did not add any. The motion Jake asked for cannot start.
Call scoring and coaching are half of what this system is for, and both need the call to be captured. No recording means no transcript, no score, and no coaching loop. His number needs registering so outbound calls record too, not just meetings he is invited to.
These do not block each other. Each one makes the system more true than it is today.
| Ask | Owner | What it fixes | State |
|---|---|---|---|
| Verbatim transcripts of the sales calls | Honey | Three are in, pulled 20 Aug and now readable end to end. Four of the five calls in the July summary were recorded on a different tool and are still missing: Cascadia 29 Jun, Ziegler 23 Jun, Senderra 12 Jun, Clear Vision 11 Jun. Exported text for those four would finish the set | 3 in, 4 to go |
| Sign off the pitch, now rewritten from your real calls | Jake | It is no longer a guess. It is drawn from how Remy actually sold to Rabinowitz and MBCHC. One read and a yes turns it from our draft into Remy's pitch | waiting |
| Assign the Eugene accounts, first thirty | Jake | You said triage Eugene's book first. The hit list is built and waiting on your order to regenerate against it | waiting |
| Set the handoff line | Jake | Which questions D'Andrew answers and which become "let me bring in the person who owns that". Until it is set, the coach cannot tell confident from over-reaching, so it cannot score a call honestly | waiting |
| The partial CRM export from the conference | Honey | You described about a hundred leads. Fifty-one arrived. The gap is most likely still in the CRM. Nobody should settle this by picking a number | outstanding |
| One client journey, start to finish | Davor | The deal stages are six placeholders today. One real journey makes them real | outstanding |
| The recorded overview made to brief D'Andrew before the conference | Davor | Background the vault does not have in any form | outstanding |
| Scope and commercials | Jake + Andy | This has run past the original spike. Worth a short conversation before it runs further | open |
The three Miami Beach calls are now readable in full. On 20 August the discovery call, the follow-up and the pro forma meeting came into the vault verbatim, summarised and tagged, and the pitch was corrected against them. That is the biggest single gap on this board, closed. It also gave us a draft answer to decision 4 below.
The Miami Beach packet landed and has been processed. Honey's 14 August email carried the last-five-calls summary, the MBCHC partnership brief, the startup brief, facility requirements, the medication-by-disease sheet and the FAQ. That answers Davor's question about where the one-pagers are. It also let us rewrite the pitch and the coaching setup from real calls instead of from pipeline notes, which was the biggest single gap on this board.
| Item | State |
|---|---|
| Rewrite the pitch from the real calls | done 19 Aug |
| Rewrite the coaching setup, add a drill set built from real objections | done 19 Aug |
| File the 14 August materials into the vault as sources | done 19 Aug |
| Regenerate the hit list in Jake's order | ready, waiting on the Eugene assignment |
| Stand the team bot up on the Hostinger box | planned, see below |
| Scope the chart-review request properly | needs the boundary conversation first |
Jake already has a personal assistant running on his Hostinger server against his own vault, and it works. The question is how the team version joins it.
A second container on the same box, its own vault, its own messaging bot, its own credentials. Not a second job inside the existing one, and not a second server.
| Question | Answer | Why |
|---|---|---|
| Does the existing bot need rebuilding? | No | It already runs as a container. Nothing about Jake's setup changes, and it does not get restarted to add the team one |
| One container or two? | Two | Jake's personal vault and the Remy team vault are different privacy domains. One process with both mounted is one mistake away from mixing them. A team bot crash should also never take Jake's assistant down |
| Is the current server big enough? | Almost certainly yes | The heavy thinking happens off the box at the model provider, so each bot is a light process, not a large one. The plan to add is a second vault copy and a second sync watcher |
| Do we upgrade the plan now? | No, measure first | We stand the second one up, watch memory and disk for a week, and upgrade only if the numbers say so. Buying a bigger plan before there is evidence is money spent on a guess |
| One bot for the team, or one each? | One each | Each person gets their own memory and history, so D'Andrew's assistant knows it is his and never surfaces someone else's notes. They all read the same vault, which is the point. Start with D'Andrew alone, add seats once his loop works |
Exactly one process is allowed to sync a vault to GitHub, and it runs on the server rather than inside the bot. The bot only writes files. That single rule is what stops two processes fighting over the same files, and it is already how Jake's setup works, so the team one copies a pattern that is proven on this exact box.
Nothing below works today. It is here so the shape is clear before anyone approves the build, and so D'Andrew knows what he is being handed.
| # | Step | Who |
|---|---|---|
| 1 | Pick a messenger. Whatever D'Andrew already has open all day, rather than a new app to remember | D'Andrew |
| 2 | A bot is created on that messenger and its access token handed to Andy. Two minutes, no cost | Davor or Honey |
| 3 | D'Andrew sends one message to the bot so it learns his account, and Andy adds that ID to the allow-list. Nobody else can talk to it | D'Andrew + Andy |
| 4 | From then on it is a normal conversation. Ask it who to call today. Ask it about an account before dialling. Tell it what happened after | D'Andrew |
Two things it does on its own once connected: a morning message with the day's call list, and a note back in the vault every time you tell it something, so the same answer is there on your laptop.
It would be a worse version of the same thing. This page is a static document with a passphrase on it, so a chat window here would need its own login, its own connection back to the vault, and its own thing to maintain, and it would only work while the page is open. Your messenger already has the identity, the notifications and the history, and it is on your phone. The bot goes where you already are.
This is deliberately not first. A bot pointed at a vault nobody has corrected yet just makes wrong answers easier to reach. The right order is: team gets in, Jake corrects the content, then the phone. If the phone matters more than the order, say so on the call and we will flip it knowingly rather than by accident.
You do not need to understand how any of this was built. You need five things, in this order. Nothing here requires you to be technical.
Create a free GitHub account and send the username. Andy walks you through installing two apps and opening the vault. After this it is just an app on your machine with files in it.
Pick a health center from the list. Ask what we know about them, who referred them, and what they said they needed. Read what comes back and correct anything wrong. That correcting is the whole habit. The system gets better because you tell it when it is wrong.
The quiz you asked for is built. It runs objections from Remy's actual calls at you, you answer, it tells you what a strong answer sounds like. Do it wrong in private ten times, then do it right on the phone once.
One file tells you who to call today, in what order, and why they are warm. Before each call, ask for the prep. After each call, say what happened. That is the job.
Recorded calls come back scored, with one thing to repeat and one thing to change. It is a coach, not a report card for anyone else, and knowing that up front is deliberate.
It will not send anything for you. Drafts stay drafts until you press send. It writes candid notes about how your calls are going, because that is what makes coaching work, and you get full access to the vault, so you can read them. Nobody is hiding a file about you.
Accept the two invites. It has been the top of this board since 14 August and it costs one click.