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 Build Your Own Hire finance team so it runs inside Claude Tag in Slack, on my own books, not just as a chat demo. Walk me through it one step at a time, do not skip ahead. Treat me like a CFO or controller who has never installed a Claude skill or used Claude Tag, and define every term once.
This is NOT a coding install for the main path. There is nothing to compile. The seats run in Slack: I @mention Claude in a channel like a coworker and the seat does the work, 24/7, after I stop typing. There is also an optional install path for the one technical person on the team.
First, the one thing I need to know from you: ask me ONLY this in your first message, then wait.
"Has your workspace admin already turned on Claude Tag in Slack (the @Claude teammate, in beta for Team and Enterprise), or should we start in a private Claude Project for now and move to Slack once it is on?"
Then branch:
## Path A (RECOMMENDED) — Claude Tag in Slack, the 24/7 teammate
This is the always-on version. You @mention Claude in the channel and the seat works after you stop typing.
Walk me through ONE step at a time, waiting for me to confirm each:
1. **Confirm the plan.** Claude Tag is in beta for Claude Team and Enterprise, with full migration on 3 Aug 2026. If my admin has enabled the Slack integration, I will see Claude in my Slack. If not, tell me to ask my admin to turn it on, and we use Path B today.
2. **Make a channel per seat, or one finance channel.** For example a private channel named "month-close". A channel is just a Slack room. The seat reads what is posted or uploaded there.
3. **Drop in only what that seat reads.** Upload the trial balance for the Controller, the invoices for the AP Clerk, the bank file for the Staff Accountant. Read only. Your data stays in your own Claude tenant. Nothing is uploaded to consultance.ai, stored by us, or seen by us.
4. **Paste the seat card and tag it.** From the resource page below, copy a seat card (start with 01 Controller). Paste it into the thread and @mention Claude. The first time, ask it to run the preflight at the bottom of the card before anything else.
5. **Let it run while you sleep.** Tag the close at the end of the day. Claude Tag keeps working after you stop typing and posts the result back in the channel. No waiting on business hours.
6. **Turn on the gate.** Build 06 the Reviewer Gate. Before you act on any seat's output, tag the Reviewer Gate in the thread with the draft and the source. It re-derives every number and blocks anything it cannot tie back.
## Path B — a private Claude Project per seat (works today, no Slack needed)
Use this if Claude Tag is not on yet, or you want to test a seat first.
1. **Pin Opus 5** and create a private **Project** named for the seat. A Project is a private workspace with its own knowledge that other chats cannot see.
2. **Upload only what that seat reads**, read only, same as above. Data stays in your tenant.
3. **Paste the seat card** from the resource page as the Project instructions. Run the preflight first.
4. Move the same card into Slack later when Claude Tag is on. Same seat, same card.
## Path C (OPTIONAL, full team) — install the seats as skills
For the one technical person who wants the seats to run by name and on a schedule.
1. **Download the kit:** https://consultance.ai/library/downloads/claude-tag-finance-team-skills.zip . Unzip it. Inside are the seven seat folders, each a SKILL.md.
2. **Install them.** Web or desktop Claude: Settings then Capabilities then Skills then Upload, pick each seat folder, confirm it appears in the skills list. This is not a Terminal install, you will not touch code. Claude Code path: make ~/.claude/skills and copy the seven folders in, then type / to confirm they are listed.
3. **Run a seat by name**, for example /controller, on the data you point it at. Each seat self-grades and stops if it cannot pass its own rubric.
4. **Wire the gate.** Test reviewer-gate on a draft with one number deliberately wrong and one unsourced claim. It must catch both before you rely on it.
## First-session drill (do this once, it is the whole pitch)
1. Install or paste ONE seat first: 01 Controller. Give it last month's closed trial balance and this month's subledger exports.
2. Ask it to run the close. Good output: every subledger tied to the GL, or the gap named in dollars, every accrual citing its support, a clear done / open / blocked checklist.
3. Now turn on 06 the Reviewer Gate. Feed it the Controller's draft plus the source, but change one number in the draft by hand first. Watch the gate catch it and send it back. That single moment, it blocked the wrong number, is why this is safe to run while you sleep.
4. Only after that win, bring in the other seats: AP Clerk, Staff Accountant, FP and A, Reporting Controller.
## Rules for walking me through this
- One step at a time. Define every term once: Slack channel, Claude Tag, @mention, Project, knowledge, skill, SKILL.md, frontmatter, trial balance, subledger, accrual, ASSUMPTION, reviewer gate.
- Do NOT tell me a step is "not possible." If Claude Tag is not on yet, use Path B today. If a skill will not upload, check the folder has a SKILL.md with a name and a description.
- Never paste live financial data into a public Claude window outside a Project or a private Slack channel. Use your own tenant controls.
- A named human signs anything that posts to the GL or leaves the finance function. The seats draft, the reviewer gate checks, a person owns the call. This is not accounting, audit, or investment advice.
First message: ask me only the Claude Tag question above, then start step 1.