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 set up the Family Office Investment Team so Claude runs real investment-office work on my own books, not just a chat demo. Walk me through it one step at a time, do not skip ahead. Treat me like a family office principal or CFO who has never built a Claude Project or used Claude Code, and define every term once.
This is NOT a coding install for the first path. There is nothing to compile. There are two tiers. Tier 1 is paste only and runs in a browser, one Project per seat. Tier 2 is the full team for the one technical person, running overnight on a schedule. Start me on Tier 1.
## Tier 1 (START HERE, no install) — one Claude Project per seat, paste the card
Each seat is a finance hire. You make a Project, upload only what that seat reads, and paste its card. The agent shows up. Your books stay in your own tenant.
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 my data stays in my own tenant. Select **Claude Opus 5.5** in the model picker. Nothing to install for this tier.
2. **Pick the first seat.** Start with 01. Portfolio Analyst (the consolidated position) or 07. Reviewing Manager (the one that checks the others). On the resource page below, each card is one seat.
3. **Make the Project.** In Claude, create a new **Project** and name it for the seat, for example "Portfolio Analyst". A Project is a private workspace with its own knowledge that other chats cannot see.
4. **Upload only what that seat reads.** Drop just that seat's files into the Project knowledge, read-only: custodian exports for the Portfolio Analyst, manager letters for the Manager Monitor, the commitment schedule for the Liquidity Analyst, and so on. The seat only ever reads these.
5. **Paste the card.** Copy that seat's card from the vault below and paste it into the Project instructions. The first time, ask it to run the preflight at the bottom of the card before anything else.
6. **Build the gate.** Stand up 07. Reviewing Manager and run every other seat's output through it before you act. Feed it a draft with one number deliberately wrong; it must catch it. If it does not, do not trust it yet.
7. A named human owns every decision and signs every number. The seats do the analyst work.
## Tier 2 (OPTIONAL, full team) — drop the seats into Claude Code, run overnight
For the one technical person who wants the seven seats to run by name and on a schedule, on a machine you control.
1. **Download the kit.** Get the agent files here: https://consultance.ai/library/downloads/family-office-agents.zip . Unzip it. Inside are the seven seat folders, each a SKILL.md.
2. **Install them.** With Claude Code (`claude` on the command line) signed into your own account, make the skills folder and copy the seven seats in: `mkdir -p ~/.claude/skills` then copy `portfolio-analyst`, `manager-monitor`, `liquidity-analyst`, `co-invest-associate`, `reporting-controller`, `family-meeting-prep`, and `reviewing-manager` into it. Open Claude Code, type `/`, you should see them.
3. **Mount the books read-only**, then run a seat by its slash name, for example `/portfolio-analyst`. Each seat self-grades and stops if it cannot pass its own rubric.
4. **Wire the gate.** Test `reviewing-manager` on a draft with one number deliberately wrong and one unsourced claim. It must catch both before you rely on it.
5. **Schedule the daily seats** (portfolio consolidation, manager drift, the liquidity calendar) on a cron, and run the gate over their output before anyone acts.
## Rules for walking me through this
- One step at a time. Define every term once: Project, knowledge, seat, card, gate, SKILL.md, `~/.claude/skills`, custodian export, capital call, mandate drift, preflight.
- Do NOT tell me a step is "not possible." If I am on Tier 1 there is nothing to install, it is paste only. If Claude Code is missing for Tier 2, walk me through installing it first.
- Never paste live account or custodian data into a public Claude window outside a Project. Use a Project with your tenant controls.
- A named human owns every decision and signs every number. The reviewing manager checks the work; it does not replace the person who acts on it. This is not investment advice.
First message: ask me "Tier 1, paste a seat card into a Claude Project to start, or Tier 2, install the seats in Claude Code? And which seat do you want first, the Portfolio Analyst or the Reviewing Manager?" Then start step 1.