Jeff Bernson · Meridian, Recombinant, Liora · from LPx October 14, 4:12 pm MT

Your programs, today and next

Your workflow as you walked me through it on Wednesday, step by step, then the same workflow with the dashboard in it. If a box is wrong, tell me and I fix it the same day.

Optional: copy this plan into Claude or ChatGPT

Press the button and this whole page, in plain words, goes to your clipboard. Paste it into your ChatGPT or Claude and the structure and the plan are in your own chat, to question or digest as you like. This is not the working product, just a way to read the plan.

You are helping Jeff Bernson understand a plan from Andrew Scimeca. Andrew is going to build a private dashboard for Jeff's three charitable donation programs: Meridian Wound Care, Recombinant Diagnostics and Liora Life Sciences. Read this whole text, then explain it to Jeff in plain English, one section at a time, and answer his questions from it. If the text does not say something, say so instead of guessing. Do not give legal or tax advice. Nothing described in sections 5, 6 and 7 exists yet; it is a plan, and Jeff decides whether it goes ahead.

## 1. What exists today

Andrew has read-only access to LPx (the onboarding platform), to Jeff's shared OneDrive folders, and to the Claude and Grok chat exports Jeff sent. ChatGPT's chat history could not be exported, but ChatGPT's own list of the files it made was. Andrew has read all three programs out of LPx and compared Meridian against Jeff's tracker and wire list. That is all that has been done so far. The dashboard has not been built. Nothing was changed in LPx, in Jeff's files, or in his Claude, ChatGPT and Grok accounts.

## 2. How the work runs today, start to finish

This is Jeff's own workflow as he walked Andrew through it on Wednesday, October 7, in eight phases. 40 steps in all.

A subscriber comes in. A referral comes in through Connor or through the group in Florida, who run the Recombinant and Liora onboarding and keep those contacts in HubSpot; Jeff's team handles Meridian. Connor adds the person to LPx and types in the referring organization. Jeff emails them the wire details himself. The subscriber fills in LPx (name, address, social security number; Plaid runs the identity and anti-money-laundering checks, called KYC and AML), uploads two years of W2s, a driver's licence or passport and a proof of address, and signs the subscription agreement and the W9 in LPx. LPx has no overview screen, so to see where anyone stands Jeff opens each record, one at a time.

The money. The subscriber wires to Encore Bank. Money never passes through LPx. Encore emails the day's wires. Whitney retypes the date, amount and sender into the Funds Received tab of the tracker, Jeff marks that member's "funds received" as Yes in LPx by hand, and Whitney sends a reminder that the subscriber is ready to be reviewed.

Approval. Jeff checks that every required item is in; the rows still waiting are yellow in the tracker, and the missing items are requested by email, one person at a time. Owen, who owns LPx and is a CPA, confirms accredited-investor status from the W2s or tax returns, or the subscriber's own CPA signs a separate letter that gets uploaded. Billy, the managing member, approves the subscription agreement in LPx and transfers the funds from escrow when told how much. Jeff sets the row to green in the tracker: a member.

State filings. The first subscriber from a new state means a notice to the securities lawyers, who file Blue Sky with that state within 15 days of the acceptance. Spotting the new state and emailing the lawyers is done by hand, with a Blue Sky tab in the tracker.

Daily tracking. Every night Jeff exports the member list from LPx as a CSV (a spreadsheet file) for each of the three programs and pastes it into ChatGPT, which rebuilds the whole tracker as a new version: committed, received, outstanding. The Meridian list went through versions 9, 10 and 11 in one day that way. Issues get an ID per subscriber in a tracker tab, by hand.

Emails. These are the emails to subscribers: asking for a missing W2, ID or proof of address, chasing an unsigned agreement, sending a form letter to a chosen list, answering a subscriber's question. The addresses were collected by hand into a Communications tab because there was no other way to get them. Each letter is drafted in a fresh Claude chat, sent and followed up one by one, and a reply is easy to miss in a full inbox.

Donation and tax. For Meridian, Convoy of Hope, the charity, picks up pallets of product from ABL, the manufacturer, every week or ten days, and signs a contemporaneous written acknowledgment (CWA) for each pickup: pallet number, units, value. Jeff keeps every CWA because they go with the 1065 tax return, writes the donation letters by delivery date in a tracker tab, and CBIZ builds the K-1 tax packages, with data due the first week of 2027. The tax documents then go out to each member; ShareFile for that is a later decision.

Alongside all of it, the documents. When Jeff changes a governing document (the PPM, the operating agreement, the subscription agreement), he opens a new chat in Claude and uploads the documents again, because the chat does not remember them, often with a carry-over brief listing the open matters. Claude drafts or redlines; Jeff runs it through ChatGPT and Grok for second and third reviews; ChatGPT rewrites the whole file as a new version; he finishes with Claude. Both AIs save into the same OneDrive folders, so versions accumulate and the question "which one is current" keeps coming back.

Who does what: Jeff runs administration and compliance. Whitney handles wires and spreadsheets. Billy accepts subscriptions, sees the bank and moves funds from escrow. LPx, owned by Owen, is the onboarding platform. Encore receives wires. Riveles Wahab does the state filings. Convoy of Hope is the Meridian charity, ABL the manufacturer. An appraiser does the qualified appraisal. CBIZ does the K-1s and the tax package.

## 3. The bottlenecks

- The daily CSV paste into ChatGPT rebuilds the tracker and breaks it.
- Every Encore wire is retyped, and funds received has to be marked as Yes in LPx by hand.
- LPx only emails when someone signs. Everything else is found by opening records one at a time.
- The acceptance date is copied out of LPx by hand, and the Blue Sky deadlines are counted by hand.
- The PPM, OA and SA are uploaded into every new chat.
- ChatGPT's document history is overwhelming: hundreds of generated files, versions on versions, and no way to tell which one matters.
- Nobody knows which version of a document is current.
- The accreditation result, Billy's acceptance and the countersign date live only inside LPx. They are not in the export and not in the tracker, so nobody can see them without opening LPx member by member.

## 4. What went wrong with the AIs, from Jeff's own chats

- February 12, Claude. A compliance alarm that was not one. The deck was called out of line with the PPM and SA because of a background memo nobody could find. Claude's own quotes showed all three agreed. A round of searching, then a retraction.
- May 5, Claude. One it got right. A one-unit illustration was carrying ten-unit amounts. Claude caught it and Jeff corrected it.
- June 28, July 1 and October 9, Claude and ChatGPT. Which version is current: recovering lost OA versions from OneDrive, reconciling v24 against v25, then asking again in October.
- August 18, Claude. 42 name replacements across the agreements when one definition covering both names was what Jeff wanted. Redone the smaller way.
- September 15, Claude. The tracker rebuilt instead of edited, after Jeff asked for colors, dropdowns and cross-sheet links to be kept.
- September 29, ChatGPT. The Meridian investor list went v9, v10, v11 in one day, each a full rebuild from the pasted CSV.
- October 11, Claude. Wire instructions pulled out of the subscription agreement on the strength of a stale carry-over note, then put back when Jeff objected.
- Every new chat, all three. The same documents uploaded again and the same context rebuilt by hand.

## 5. What gets built (planned, not built)

The pieces, in the words Andrew uses on the page:

- The cloud server: a rented computer at DigitalOcean, on Jeff's company's account. Everything below runs on it. Sign-in is by email code.
- The database: Postgres, on that server. The source of truth. Every record the dashboard shows is a row in it (subscribers, steps, wires, states, document versions), each with where it came from and when it was read. One copy; the web page and all three of Jeff's AIs read the same rows.
- The LPx reader: a program that signs into LPx with a view-only login, the way Jeff does, and copies the member lists for all three programs into the database every 15 minutes. That is what "every 15 minutes" means on the page. It never changes anything in LPx.
- The wire reader: a program that reads the Encore wire emails in the mailbox Jeff points it at, puts each wire into the database, and pairs it with the subscriber it matches. Whitney confirms the pair with one click.
- The web page: the dashboard. Jeff, Whitney and Billy open it in a browser. It shows what is in the database.
- The MCP server (Model Context Protocol): a program on the same server that Claude, ChatGPT and Grok can call. Jeff adds it once in each. From then on, whichever one he asks reads the same rows the dashboard shows and the current documents, and answers with the record it used. It can read, never write. No AI can change LPx or the dashboard.
- The version register: one row per governing document, which file is current and since when. The current files sit in one OneDrive folder, older ones in an archive folder. The MCP server reads the current ones, so nothing gets uploaded into a chat again.
- The outbox: the drafts the dashboard writes (the notice to the lawyers for a new state, the reminder for a missing item, the transfer note to Billy, the donation letter, the reply to a subscriber). They wait for Jeff. After he approves one, it is sent from his own mailbox.
- The change log: every row written to the database, with the time and the source. Nothing in it is erased.

The dashboard reads, compares and flags. It never writes to LPx, never moves money, and never decides who is accepted or accredited. Decisions stay with people: Owen on accreditation, Billy on acceptance and transfers, Jeff on every email that goes out.

## 6. The same workflow with the dashboard, phase by phase

39 steps instead of 40, and the dashboard does 16 of them. Jeff's own steps go from 16 to 4, Whitney's from 2 to 1.

A subscriber comes in. When a new person appears in LPx, the LPx reader sees them within 15 minutes and the dashboard sends them the wire details from Jeff's mailbox, using a template he approved once. Every person in all three programs sits on one subscriber screen: their stage in LPx, what is still missing, whether the wire is in, who referred them. The subscriber still fills in LPx, uploads and signs exactly as today.

The money. The wire reader takes each wire out of the Encore email, matches it to the subscriber and writes it, dated, into the source of truth. It shows on the dashboard, and every AI Jeff asks sees the same wire. Whitney confirms the match with one click; nothing is retyped. Jeff still marks funds received in LPx himself; the dashboard never touches LPx.

Approval. A review queue lists every subscriber whose wire is in, with the items still missing next to each name, and drafts the reminder email for each missing item for Jeff to approve. The transfer note to Billy is drafted with the amount, sent on Jeff's approval from his mailbox. The LPx reader picks up Billy's acceptance and its date, so the member date appears without anyone copying it, and the 15-day Blue Sky clock starts from that date. Owen and Billy do exactly what they do today.

State filings. A Blue Sky table by state: first subscriber, date, deadline, notice sent, filed. When a subscriber from a new state appears, the dashboard spots it, counts the deadline and drafts the notice to the lawyers; Jeff approves, it sends. The dashboard cannot see the state's system or the lawyers' office, so the filed date comes from the lawyers' reply in that email thread: the dashboard reads it, proposes the date, Whitney confirms. Until a filed date is in, that state stays open with the deadline counting down. The promise is that an unfiled state can never be forgotten, not that the filing happens by itself.

Daily tracking. Nothing to export. The LPx reader reads LPx every 15 minutes, and committed, received, outstanding and the issue IDs are live per program and per person. All three AIs read that same source of truth through the MCP server, so Claude, ChatGPT and Grok give the same answer from the same record. The tracker is left alone.

Emails. Jeff picks the names on the subscriber list: a whole program, everyone at one stage, everyone missing the same item, or a list he chooses. The dashboard fills the letter from each person's record (name, program, the item they owe) with the template he approved once. He reads it, changes it if he wants, approves, and it sends from his own mailbox. The dashboard keeps reading that mailbox: a reply is matched to the person and flagged, and for a question it drafts the answer from that person's records and shows which record it used. Every email and reply is kept in the communications history.

Donation and tax. Each CWA reaches the dashboard as an email Jeff forwards or a PDF he drops onto that delivery. The dashboard reads the pallet number, units, value and date off it, Whitney confirms the numbers, and the delivery gets one row in the source of truth with the PDF attached. The donation letter for that delivery is drafted from those numbers for Jeff's approval. At year end, every CWA, every letter and the totals per member go to CBIZ as one file in their layout. The pickups, CBIZ's work and the tax documents going out are unchanged.

Alongside all of it, the documents. Jeff opens the project in Claude, ChatGPT or Grok and the current documents are already there through the MCP server; nothing to upload, no carry-over brief. The AI reads the current file from the OneDrive folder and drafts or redlines it; a second or third AI reads the same file and comments; nothing is rebuilt as a new version. One current file per document, the register says which and since when.

The dashboard's screens: program overview (committed, wired, what is waiting); subscribers, every person and every step; review queue; wires with a confirm button; Blue Sky by state with deadlines; activity, every import and change; ask, with the record it used; a 7 am morning email; the outbox of drafts sent only after Jeff approves; donations and tax; the version register. The first screen is Meridian: one row per subscriber with step in LPx, KYC, wire, state, and what comes next.

## 7. What Jeff gets back, counted from the charts

These are counts of boxes on the two charts, nothing estimated.

- A subscriber comes in and funds: 8 hand steps today; 2 with the dashboard (Jeff marks funds received in LPx, Whitney confirms the wire).
- Per 100 subscribers: 800 hand steps today; 200 with the dashboard.
- Every night: 6 today (three exports, three rebuilt trackers); 0 with the dashboard.
- First subscriber from a new state: 2 hand steps today; 0, plus one approval, with the dashboard.
- A subscriber emails a question: 2 hand steps plus a fresh chat today; 1 with the dashboard.
- Convoy of Hope picks up a delivery: 2 hand steps today; 0 with the dashboard.
- Finding the current document version: asked an AI on June 28, July 1 and October 9; the register shows it.

The return is hours, and Andrew will not guess them. At the 30-day check-in Jeff and Andrew time one subscriber end to end, today's way and the dashboard's way, and write the hours down next to the fee.

## 8. Order of work, and what is needed

Meridian first, then Recombinant, then Liora, as the agreement says. The first thing Jeff will see is the Meridian subscriber screen: every subscriber, where they are stuck, what is missing, whether funds are in. Whitney checks it against LPx and the sheets before anyone relies on it. Wires, questions and the morning email come next, then follow-ups and notices (each one Jeff approves before it is turned on), then the other two programs, then the year-end donation and tax file for CBIZ.

Exact dates will be in a written plan Andrew sends for Jeff's approval. Nothing is built past the first screen until Jeff approves it. A short update every Friday. Same-day replies.

Andrew is ready to start the Meridian subscriber screen the day Jeff confirms the Today charts match how he works; he already has what that screen needs, the LPx login and the files. The later pieces need six things from Jeff:

1. A DigitalOcean account in the company's name, with Andrew as an admin, and the names of who should have logins.
2. Access to the inbox where Encore wire emails arrive, or a rule forwarding them to one address.
3. Confirmation that the company signer on the subscription agreement in LPx is Billy.
4. The lawyers' rule for new-state notices, in writing.
5. Read-only HubSpot access from the Florida group, for Recombinant and Liora.
6. Thirty minutes with Whitney to check the first screen.

## 9. Boundaries

The dashboard does not replace LPx. Tax returns, legal advice, a SOC 2 examination, a full archive of LPx documents and secure tax-document delivery are outside this work. The investor portal Jeff and Billy are deciding on in December is separate.

## Your job now

Explain sections 1 to 9 to Jeff in plain English, one at a time. Make clear which parts exist today (section 1) and which are planned (sections 5 to 7). Define any term he asks about using the words in section 5. Then ask him whether the Today workflow in section 2 matches how he works, which of the six items in section 8 he can send this week, and help him write his reply to Andrew.

The workflow, phase by phase

Your workflow as you walked me through it, from a referral to the tax packages: 40 steps today, 39 with the dashboard, which does 16 of them. Your own steps go from 16 to 4, Whitney's from 2 to 1.

Each phase is shown twice: as it runs today, then with the dashboard. Each box is one step, its lane says who does it, and the numbers run through all eight phases. "Every 15 minutes" means the dashboard opens LPx on its own and re-reads every member list; nobody exports anything. On the dashboard side your three AIs share one lane: through one MCP connection they read the same records and the same folder. LPx, the bank, Billy and Whitney stay where they are; the dashboard reads LPx and never changes anything in it.

By hand today, taken over by the dashboardThe dashboard does thisUnchanged from todayShaded lanes: you and Whitney

1. A subscriber comes in

Today: Jeff emails the wire details himself and opens each record in LPx, one at a time, to see where anyone stands.
With the dashboard: The wire instructions go out from the dashboard within 15 minutes of the person landing in LPx, and every person sits on one screen with their stage, what is missing, whether the wire is in and who referred them.

Today

With the dashboard

03 Wire details sent

When a new person appears in LPx, the LPx reader sees them within 15 minutes and the dashboard sends them the wire instructions from your mailbox, using the template you approved once. The send is written into the source of truth on your cloud server, so the dashboard shows who got it and when.

07 Subscriber screen

Every person in all three programs on one screen: their stage in LPx, what is still missing, whether the wire is in, who referred them. Read from LPx every 15 minutes into the source of truth on your cloud server. The dashboard shows it, and your AIs see the same rows through MCP (Model Context Protocol).

2. The money

Today: Whitney retypes every Encore wire into the sheet, Jeff marks funds received as Yes in LPx by hand, Whitney sends the reminder.
With the dashboard: Each wire is matched to its subscriber and written into the source of truth, so the screen and all three AIs show the same wire. Whitney confirms with one click. Jeff still marks funds received in LPx himself; the dashboard never touches LPx.

Today

With the dashboard

10 Wire matched

The wire reader takes each wire out of the Encore email, matches it to the subscriber, and writes it, dated, into the source of truth on your cloud server. The dashboard shows it next to the person. Any of your AIs you ask sees the same wire through MCP.

11 Confirms the match

Whitney looks at the pair the dashboard made and clicks confirm. Nothing is retyped. The confirmation, and who clicked it, go into the change log.

3. Approval

Today: Jeff checks every item, requests what is missing by email one person at a time, and sets the row to green by hand after Billy transfers.
With the dashboard: The review queue shows who is ready and what each one is still missing, with the reminders drafted. The transfer note to Billy is drafted with the amount. The member date is read out of LPx and the 15-day clock starts itself. Owen and Billy do exactly what they do today.

Today

With the dashboard

13 Review queue

Every subscriber whose wire is in, with the items still missing next to each name, oldest first. The dashboard drafts the reminder email for each missing item; you approve, it sends from your mailbox. The queue lives in the source of truth, so your AIs can answer who is waiting and why.

16 Note to Billy

When a subscriber is ready, the dashboard drafts the note to Billy with the amount to transfer from escrow. You approve, it goes from your mailbox, and the send is logged.

18 Member recorded

The LPx reader picks up Billy's acceptance and its date out of LPx, so the member date appears on the dashboard without anyone copying it, and the 15-day Blue Sky clock starts from that date.

4. State filings

Today: Someone notices the first subscriber from a new state and emails the lawyers, with a Blue Sky tab kept by hand.
With the dashboard: The dashboard spots the first subscriber from a new state, counts the deadline, and the notice to the lawyers goes out on your approval. The filed date comes from the lawyers' reply and Whitney confirms it; until it is in, the state stays open with the deadline counting down.

Today

With the dashboard

19 Blue Sky table

A table by state: first subscriber, date, deadline, notice sent, filed. When a subscriber from a new state appears, the dashboard spots it, counts the deadline and drafts the notice to the lawyers. You approve, it sends from your mailbox. The dashboard cannot see the state's system or the lawyers' system, so the filed date comes from the lawyers' reply in that email thread: the dashboard reads it, proposes the date, Whitney confirms with one click. Until a filed date is in, that state stays open on the table and in the review queue with the deadline counting down. The guarantee is that nothing drops silently, not that the filing happens by itself.

5. Daily tracking

Today: Three exports, three pastes into ChatGPT and a rebuilt tracker, every night, plus an issues tab by hand.
With the dashboard: Nothing to export. The dashboard reads LPx every 15 minutes into the source of truth on your cloud server, and committed, received, outstanding and the issue IDs are live per program and per person. All three of your AIs read that same source of truth through the MCP server (Model Context Protocol), so Claude, ChatGPT and Grok give the same answer from the same record. The tracker is left alone.

Today

With the dashboard

21 Reads LPx itself

The LPx reader signs into LPx with the view-only login every 15 minutes and copies the member lists for all three programs into the source of truth on your cloud server. Nobody exports a CSV, nothing is pasted into ChatGPT, the tracker is left alone.

22 Totals and issues

Committed, received and outstanding per program and per person, straight from the source of truth, plus the issue list with one ID per subscriber. What used to be rebuilt every night is simply there, and your AIs read the same numbers through MCP.

23 One source of truth

The MCP server (Model Context Protocol) runs on the same cloud server as the database. Claude, ChatGPT and Grok each connect to it once. From then on, whichever one you ask reads the same rows the dashboard shows: subscribers, wires, states, documents. One source of truth, three AIs, no pasting between them. It can read, never write.

6. Emails

Today: These are the emails to subscribers: asking for a missing W2, ID or proof of address, chasing an unsigned agreement, sending a form letter to a chosen list, answering an investor's question. Today the addresses are collected by hand into a tab, each letter is drafted in a fresh chat, sent and followed up one by one, and a reply is easy to miss in a full inbox.
With the dashboard: You pick the names on the subscriber list: a whole program, everyone at one stage, everyone missing the same item, or a list you choose. The dashboard fills the letter from each person's record (name, program, the item they owe) with the template you approved once. You read it, change it if you want, approve, and it sends from your own mailbox. The dashboard keeps reading that mailbox: a reply is matched to the person and flagged, and for a question it drafts the answer from that person's records and shows which record it used. Every email and reply is kept in the communications history, so the Communications tab is never filled in by hand again.

Today

With the dashboard

24 Select recipients

On the subscriber list you tick the people, or take a filter: one program, everyone at one stage, everyone missing the same item. The list comes from the source of truth, so the addresses are already there; nothing is looked up by hand.

25 Letter filled in

The dashboard takes the template you approved once and fills it from each person's record: their name, their program, the item they owe. One letter per person, ready to read. You can change any of them before you approve.

26 Sent, reply tracked

On your approval the emails go out from your own mailbox, so the subscriber sees your address. The dashboard keeps reading that mailbox: when a reply arrives it is matched to the person and flagged on the dashboard, so no reply sits unseen. The send and the reply are both written into the source of truth.

27 Approve the answer

When the reply is a question, the dashboard drafts the answer from that person's records and the current documents, and shows which record it used. You read it, change it if you want, approve, and it sends from your mailbox and stays on file. The Communications tab is never filled in by hand again.

7. Donation and tax

Today: Convoy of Hope collects pallets of product from ABL every week or ten days and signs a CWA for each pickup: pallet number, units, value. Jeff keeps every CWA because they go with the 1065 return, writes the donation letters by delivery date in a tracker tab, and CBIZ builds the K-1 tax packages from data due the first week of 2027. The tax documents then go out to each member.
With the dashboard: Each CWA reaches the dashboard as an email you forward or a PDF you drop onto that delivery. The dashboard reads the pallet number, units, value and date off it, Whitney confirms the numbers, and the delivery gets one row in the source of truth with the PDF attached. The donation letter for that delivery is drafted from those numbers for your approval. At year end, every CWA, every letter and the totals per member go to CBIZ as one file in their layout. The pickups, CBIZ's work and the tax documents going out to members are unchanged.

Today

With the dashboard

30 CWA filed

A CWA is the charity's signed acknowledgment of one pickup. It reaches the dashboard as an email you forward or a PDF you drop onto that delivery. The dashboard reads the pallet number, units, value and date off it, Whitney confirms the numbers, and the delivery gets one row in the source of truth with the PDF attached. Nothing is retyped into a tab, and every CWA is where the 1065 needs it.

31 Letter drafted

For each delivery the dashboard drafts the donation letter from that CWA's numbers and date. You read it, change it if you want, approve, and it sends from your mailbox. The letter is kept with its CWA.

32 CBIZ file

At year end the dashboard puts every CWA, every letter and the totals per member into one file for CBIZ, in the layout CBIZ asks for, instead of a tracker tab assembled by hand. Your workbook's target for that hand-over is the first week of 2027.

8. Alongside: the documents

Today: Every new chat starts with the PPM, OA and SA uploaded again and a carry-over brief, and ends with another version saved in OneDrive.
With the dashboard: One current file per document in one folder; the register says which file is current and since when; all three AIs read that same file through the MCP server. No uploading, no version hunting.

Today

With the dashboard

35 Opens the project

You open the project in Claude, ChatGPT or Grok. The current documents are already there through MCP. Nothing to upload, no carry-over brief.

36 Drafts and redlines

The AI reads the current file from your OneDrive folder through MCP (Model Context Protocol) and drafts or redlines it.

37 Other AI reviews

Ask a second or third AI. It reads the same current file, comments on it, and nothing is rebuilt as a new version.

38 One current version

One current file per document in one folder on your OneDrive. Older versions move to an archive folder.

39 Version register

A table in the source of truth: which file is current for each document and since when. The dashboard shows it. Your AIs read the current file through MCP, so nobody asks which version is current.

The dashboard, and how your AIs connect to it

One private web page on a server in your name. It reads LPx, your Encore wire emails and your OneDrive folders, and never writes back to any of them. You, Whitney and Billy open it in a browser. Claude, ChatGPT and Grok reach it through one MCP connector and answer with the record they used.

What you get back, counted

Counted from the two charts, nothing estimated. Hand steps are the boxes in your lane and Whitney's.

Each time	Today, by hand	With the dashboard
A subscriber comes in and funds	8 hand steps: 6 yours, 2 Whitney's	2: you mark funds received in LPx, Whitney confirms the wire
Per 100 subscribers	800 hand steps	200
Every night	6: three exports, three rebuilt trackers; about 180 a month	0; it re-reads LPx every 15 minutes on its own
First subscriber from a new state	2: spot it, email the attorneys	0; the email is drafted, you approve it
A subscriber emails a question	2, plus a fresh chat to draft	1: you approve the drafted reply
Convoy of Hope picks up a delivery	2: file the CWA, write the letter	0; both on file, the letter drafted
Finding the current document version	asked your AI on Jun 28, Jul 1 and Oct 9	the register shows it

The return is hours, and I will not guess them. At the 30-day check-in we time one subscriber end to end, today's way and the dashboard's way, and write the hours here next to the fee.

What gets built

The cloud server

A rented computer at DigitalOcean, on your company's account. Everything below runs on it.

The database

Postgres, on that server. The source of truth. Every record the dashboard shows is a row in it: subscribers, steps, wires, states, document versions, each with where it came from and when it was read. One copy; the web page and all three of your AIs read the same rows.

The LPx reader

A program that signs into LPx the way you do, with a view-only login, and copies the member lists for all three programs into the database on a timer. That is what every 15 minutes means. It never changes anything in LPx.

The wire reader

A program that reads the Encore wire emails in the mailbox you point it at and puts each wire into the database, paired with the subscriber it matches. Whitney confirms the pair with one click.

The web page

The dashboard. You, Whitney and Billy open it in a browser. It shows what is in the database.

The MCP server

A program on the same server that Claude, ChatGPT and Grok can call. You add it once in each. When you ask a question, the AI asks the MCP server, which reads the database and the current documents, and the AI answers with the record it used. It can read, not write.

The version register

One row per governing document: which file is current and since when. The current files sit in one OneDrive folder, older ones in an archive folder. The MCP server reads the current ones, so nothing gets uploaded into a chat again.

The outbox

The drafts the dashboard writes: the notice to the lawyers for a new state, the reminder for a missing item, the transfer note to Billy, the donation letter, the reply to an investor. They wait for you. After you approve one, it is sent from your own mailbox.

The change log

Every row written to the database, with the time and the source. Nothing in it is erased.

Review queue

Subscribers whose wire is in and whose items are complete, waiting for approval, with anything still missing listed next to the name.

Reads, never writes

The readers and the MCP server look at LPx, the Encore emails and your files. They change nothing in any of them.

CSV

The spreadsheet file LPx hands you when you press export. With the LPx reader in place there is nothing to export.

Red, green, grey

On the charts: red is work done by hand today, green is what the dashboard does, grey is what stays exactly as it is.

Three AIs at once: what went wrong

From your own chats and ChatGPT's file inventory. Dates only, no names. If a line is wrong, tell me which one.

Feb 12

Claude. A compliance alarm that was not one. The deck was called out of line with the PPM and SA because of a background memo nobody could find. Claude's own quotes showed all three agreed. A round of searching, then a retraction.

May 5

Claude. One it got right. A one-unit illustration was carrying ten-unit amounts. Caught, and you corrected it.

Jun 28, Jul 1, Oct 9

Claude and ChatGPT. Which version is current. Recovering lost OA versions from OneDrive, then reconciling v24 against v25, then asking again in October. Both write versions into the same folders and neither knows what the other did.

Aug 18

Claude. 42 name replacements across the agreements when one definition covering both names was what you wanted. Redone the smaller way.

Sep 15

Claude. The tracker rebuilt instead of edited. You asked for colors, dropdowns and cross-sheet links kept. It handed back a paste-in copy. Neither AI can edit your Excel in place; each one rebuilds the file.

Sep 29

ChatGPT. The Meridian investor list went v9, v10, v11 in one day, each a full rebuild from the pasted CSV.

Oct 11

Claude. Wire instructions pulled out of the SA on the strength of a stale carry-over note that called them a defect, then restored when you objected.

Every new chat

Claude, ChatGPT and Grok. The PPM, OA and SA uploaded again, plus a carry-over brief carrying up to nine open matters. The same context rebuilt by hand, three times over.

Bottlenecks today, and what removes them

Today	With the dashboard
You paste the LPx CSV into ChatGPT. It rebuilds the tracker and breaks the formatting.	The dashboard reads LPx itself, every 15 minutes. Your tracker is never touched.
Whitney retypes every Encore wire. Someone marks funds received as Yes in LPx by hand.	The dashboard reads the wire email, matches it to the subscriber and writes it into the source of truth; Whitney confirms it; every AI you ask sees the same wire. Funds received in LPx is still marked by your team, never by the dashboard.
LPx only emails you when someone signs. Everything else you have to go look for.	Every change shows up on one screen, with the time it happened.
Blue Sky deadlines are counted by hand.	Counted for you, per subscriber, per state.
You upload the PPM, OA and SA into every new chat.	One folder per program holds the current versions. Your AIs read from it.
ChatGPT's document history is overwhelming. Hundreds of generated files, versions on versions, no way to see which one matters.	One current version per document, per program. Everything else is archive. The dashboard shows the register.
Nobody knows which version is current.	The folder is the answer. Everything cites the version it used.
Accreditation, Billy's acceptance and the countersign date live only inside LPx. They are not in the export and not in the tracker.	The dashboard reads them out of LPx and shows them next to everything else, with the date.

Done so far

Oct 12

Read-only access to LPx, your OneDrive folders and your Claude and Grok exports.

Oct 14

Read all three programs straight from LPx.

Oct 14

Compared Meridian against your tracker and wire list, line by line.

Oct 14

Read the chat exports: what each AI does for you and where it went wrong.

Oct 14

Picked the hosting: a DigitalOcean VPS (virtual private server, a rented computer in the cloud) in your name, about $40 a month, with the database on it. Your data stays yours.

Oct 14

Designed the MCP connector (Model Context Protocol, the plug that lets Claude, ChatGPT and Grok read the same records and the same folders). One source of truth for all three.

A written plan with dates, sent to you for approval before anything is built past the first view.

Ready

Tell me the Today charts match how you work, and I start building the Meridian subscriber screen that day; I already have what it needs, the LPx login and your files. The later pieces need six things from you, listed in the brief at the top: a DigitalOcean account in your company's name, access to the Encore wire-email inbox, confirmation that Billy signs for the company in LPx, the lawyers' new-state rule in writing, read-only HubSpot access, and thirty minutes with Whitney.

Your programs, today and next

Optional: copy this plan into Claude or ChatGPT

The workflow, phase by phase

1. A subscriber comes in

2. The money

3. Approval

4. State filings

5. Daily tracking

6. Emails

7. Donation and tax

8. Alongside: the documents

The dashboard, and how your AIs connect to it

What you get back, counted

What gets built

Three AIs at once: what went wrong

Bottlenecks today, and what removes them

Done so far

Next