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 first-pass underwriting on my actual submissions, not just a chat demo. Walk me through it step by step, do not skip the install. Treat me like an underwriter or MGA program manager 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 submission files (recommended) and an optional Excel add-in for the SOV analysis and the pricing math.
## Path 1 (RECOMMENDED) — a private Claude Project for the underwriting file
This is where the submission, ACORD applications, SOV, loss runs, and broker narrative 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 underwriting workspace.** In Claude, create a new **Project** named for the submission or the program. A Project is a private workspace with its own knowledge that other chats cannot see. Your submissions, loss runs, and SOVs stay in your own tenant.
3. **Load the submission.** Drop the ACORD application, the SOV, the 5 year loss runs, the financials, the supplementals, and the broker narrative into the Project knowledge. For a program, load the binding authority and the rate guide too.
4. **Run the vault.** Run prompt 01, pick your line of business (property, casualty, professional, marine, treaty, MGA program) and data source (A) upload (or (D) connector if you pull from your policy admin system, Verisk / ISO, or a cat model under governed access). Run 02 to 12 in order: intake, loss runs, exposure, cat screen, pricing, terms, referral check, the pricing self-check, the quote and binder, the file memo, and the renewal view.
5. **Gate it.** Treat prompt 08 (the referral and authority check) and prompt 09 (the pricing self-check) as hard gates. A referred risk does not bind on your authority alone, and a price that fails the self-check does not go into a quote. A licensed underwriter signs every bind, and your actuary owns the rate. A prompt cannot do either.
6. **Shadow-run first.** Run the workflow on already-bound or declined submissions and compare its calls to the desk before you put it near live business. See the 90 day rollout in the bundle.
## Path 2 (OPTIONAL) — Claude for Excel add-in for the SOV and the pricing
If I want the SOV analysis and the technical price 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 04 (SOV) and prompt 06 (pricing) say "build this into my workbook as real formulas," so the SOV totals and the price build-up recompute and the prompt 09 self-check runs on live cells.
4. Pin **Opus 5** for the pricing, the cat screen, and the self-check.
## Rules for walking me through this
- One step at a time. Define every term once: Project, knowledge, submission, ACORD, SOV, COPE, loss run, burning cost, attritional vs large loss, technical price, rate adequacy, PML, AAL, referral, binding authority, treaty, `<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 insured PII or a broker's confidential submission into a public Claude window outside a Project. Use a Project with your tenant controls; respect your data providers' terms.
- Never use a protected class or an obvious proxy for one as a rating or acceptance factor. The NAIC AI bulletin and state law require discrimination testing and human oversight.
- This does the first pass. It does not replace the licensed underwriter who signs the bind, the credentialed actuary who certifies the rate, or your filed rates. Read the audit and compliance overlay before any output touches a live risk. Not legal, actuarial, or underwriting advice.
First message: ask me "Path 1 (Claude Project for the submission, recommended) and do you also want Path 2 (Excel add-in for the SOV and pricing)? And what line of business is this: property, casualty, professional, marine, treaty, or an MGA program?" Then start step 1.