Click to copy
I am comfortable copy-pasting and following instructions, but I am not a developer.
There is nothing to install for this one and no commands to type: it all happens inside Claude. If any instruction below implies a Terminal, translate it into the equivalent click path for me instead.
- Plain English. Define jargon the first time it appears.
- One step at a time, then wait for me to confirm before the next one.
- Tell me what success looks like at each step, and diagnose any error before moving on.
Follow the instructions below with those rules applied.
I want to INSTALL the real setup so Claude runs the monthly NAV close on my actual fund books, not just a chat demo. Walk me through it step by step, do not skip the install. Treat me like a fund controller or COO who has never built a Claude Project or installed an Office add-in, and define every term once.
This is NOT a Terminal or coding install. There is nothing to compile. It is two paths: a private Claude Project for the fund records (recommended) and an optional Excel add-in for the NAV strike, the reconciliations, and the fee math.
## Path 1 (RECOMMENDED), a private Claude Project for the close
This is where the trade blotter, prime broker and custodian statements, general ledger, and LP register live so every prompt reads from one governed place.
Walk me through ONE step at a time, waiting for me to confirm each:
1. **What I need.** A Claude account on a Team or Enterprise plan so the data stays in my tenant. Pin **Opus 5**. Nothing to install for this path.
2. **Create the close workspace.** In Claude, create a new **Project** named for the fund and the period. A Project is a private workspace with its own knowledge that other chats cannot see. Your blotter, statements, GL, and LP register stay in your own tenant.
3. **Load the records.** Drop the trade blotter, the prime broker and custodian statements, the GL or trial balance, the LP register, and your fee terms into the Project knowledge. If you run multiple funds, keep one Project per fund.
4. **Run the vault.** Run prompt 01, pick your fund type (hedge, PE/VC, fund of funds, family office), and data source (A) upload (or (D) connector if you pull from an administrator portal, prime broker feed, or fund-accounting system under governed access). Run 02 to 13 in order: strike the NAV, reconcile to the broker and custodian, book the fees, run the waterfall, reconcile the capital accounts, work the breaks, draft the letter, build the statements, re-derive the numbers a second way as a self-check, sign off, accrue expenses, and assemble the audit binder.
5. **Gate it.** Treat prompt 10 (the reconciliation self-check) and prompt 11 (the controller sign-off) as hard gates. Any red item or any self-check FAIL blocks publication. The person who strikes the NAV is not the only one who reviews it. A named human signs the NAV, a prompt cannot.
6. **Parallel run first.** Run the close alongside your administrator for one or two cycles and tie your NAV to theirs within tolerance before you trust it or change anyone's scope. See the 90 day rollout in the bundle.
## Path 2 (OPTIONAL), Claude for Excel add-in for the strike, recon, and fee math
If I want the NAV strike, the reconciliations, and the fee schedule to live in real formulas:
1. In Excel (Microsoft 365 desktop or web): **Home** or **Insert** tab, **Add-ins** / **Get Add-ins**, search **"Claude"**, **Add**. Tell me where the button is in my version.
2. Sign in to the docked Claude side panel.
3. In vault prompt 01 choose data source (C) Excel add-in. For prompt 02 (NAV), prompt 03 (reconciliation), and prompt 04 (fees) say "build this into my workbook as real formulas," so the NAV recomputes, the breaks list updates, and the high-water mark math runs on live cells.
4. Pin **Opus 5** for the strike, the fee and allocation math, and the sign-off.
## Rules for walking me through this
- One step at a time. Define every term once: Project, knowledge, NAV, trade blotter, prime broker, custodian, administrator, high-water mark, hurdle, waterfall, capital account, equalization, Level 3, SOC 1, `<review_gate>`, `{{TOKEN}}`.
- Do NOT tell me a step is "not possible." If the Excel add-in is missing, check Excel for Microsoft 365, try Excel on the web, or AppSource. For the Project path there is nothing to install.
- Never paste live investor PII or fund records into a public Claude window outside a Project. Use a Project with your tenant controls; respect your administrator's and data providers' terms.
- This moves the labor in-house. It does not replace independent NAV verification, SOC 1 controls, or the annual audit. Read the audit and compliance overlay before you reduce your administrator's scope. A named human signs every NAV. Not accounting or audit advice.
First message: ask me "Path 1 (Claude Project for the fund records, recommended) and do you also want Path 2 (Excel add-in for the NAV strike and fee math)? And is this a hedge fund with NAV per share, or a closed-end PE or VC vehicle with capital accounts?" Then start step 1.