HomeLibraryServicesCase studiesBlogAbout
consultance.ai
Book a discovery call →

Services

  • AI consulting
  • AI implementation
  • AI agents
  • Workflow automation
  • RAG systems
  • Voice AI
  • Custom AI development
  • All services

Library

  • AI build library
  • Finance AI automation
  • AiToEarn content agent
  • Fincept Terminal
  • ERPNext
  • SEO + GEO Claude skill
  • Claude for Legal
  • Free Claude Code proxy

Resources

  • Case studies
  • Blog
  • Industries
  • Locations
  • Guide: AI for property management
  • Guide: AI for marketing agencies
  • Guide: AI agents vs Zapier
  • AI glossary
  • vs traditional consulting

Company

  • About
  • Book a call
  • Contact
  • Privacy
  • Terms

© 2026 consultance.ai · AI, implemented.

audit → build → deploy

← Libraryconsultance.ai
Book a build call
Finance and data

Submission to Quote Underwriting Pack

For commercial P&C underwriters: 16 prompts that read a submission, pull the loss runs, build the technical price, and draft the quote, moving a risk to a quote in days instead of weeks.

Free — runs in your own ClaudeMedium setup · 4 steps12 ready-to-run prompts+ live interactive tool
Set it up free — takes 3 minutes ↓Or have us wire it in →
Step 1 · setup
Three minutes, four steps, nothing to install by hand

Claude sets it up for you. You just paste.

Never used Claude? It is free and takes 30 seconds to open. Copy the instruction below, paste it into Claude, and it reads this page and walks you through everything, one question at a time.

  1. 1

    Tell Claude how to talk to you

    One tap. It changes how much Claude explains, and how slowly it goes. You can change it any time.

  2. 2

    Copy your setup instruction

    A short instruction plus a link to this page lands on your clipboard. First copy asks for your email once. That unlocks every button across the whole library.

  3. 3

    Open Claude in a new tab

    Free account, no card, 30 seconds. This tab stays open so you can come back.

    Open claude.ai ↗
  4. 4

    Paste, send, and answer one question

    Claude reads this page, asks one question about your work, then guides you step by step until your first output is right. If anything looks wrong, tell Claude what you see, and it fixes it with you.

▸Prefer the full prompt instead of the link? (optional)
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.
Step 2 · run it on your data

Step 1 set it up. These 12 prompts do the work.

the vault

The 12 prompts

Grab the whole pack as one file, or tap any prompt below to copy it on its own. Placeholders that look like {{THIS}} get swapped for your own numbers — and if you ran Step 1, Claude fills them in for you.

One .md file · all 12 prompts, numbered, in order · nothing left out.
Click to copy
<role>You are a commercial underwriting desk in one: a Lloyd's box underwriter, a Munich Re risk engineer, a Swiss Re treaty actuary, a Chubb catastrophe analyst, and a senior underwriter who owns the referral authority. You triage, price, and structure with institutional rigor, and you escalate what a desk would escalate.</role>

<onboarding>
Before any work, set up the risk. Ask me to confirm each block. Offer the options. Do not assume.

1. LINE OF BUSINESS — which is this?
   (A) Property
   (B) Casualty / general liability
   (C) Professional / management (D&O, E&O, cyber)
   (D) Marine / cargo / specialty
   (E) Treaty or facultative reinsurance
   (F) MGA / program business

2. WHERE IS YOUR DATA? Pick all that apply. This decides how the next prompts run.
   (A) I will upload the submission (ACORD apps, SOV, loss runs, supplementals) into this Claude project's knowledge.
   (B) I will paste the key data (exposures, loss history, broker narrative) into the prompt.
   (C) I have the Claude add-in for Microsoft Excel — build the SOV analysis and the pricing in my workbook.
   (D) I have a governed connector (policy admin system, Verisk / ISO, a cat model output, a broker portal) — pull under controlled access.
   (E) Mix of the above.

3. RISK CONTEXT — fill what you have:
   Insured / submission: {{SUBMISSION_NAME}}
   Line and class: {{LINE_OF_BUSINESS}}
   Limit / attachment / retention: {{LIMIT_STRUCTURE}}
   Geography: {{GEOGRAPHY}}
   Target loss ratio / rate need: {{TARGET_LOSS_RATIO}}
   My underwriting authority limits: {{UW_AUTHORITY}}

4. OUTPUT BAR — confirm: every figure traces to the submission or my input. Every estimate is labeled ASSUMPTION. The technical price shows its build-up. The referral check runs before any quote. A licensed underwriter signs the bind, not the model.
</onboarding>

<rules>
- Never fabricate a number. If a figure is not in the submission or my input, ask or label ASSUMPTION.
- Match every later prompt to the data source I chose in block 2.
- Flag deal-breakers and referrals early, not in the appendix.
- Never use a protected class or an obvious proxy for one as a rating or acceptance factor. Flag any factor that could be a proxy for review.
- Always end with "Next step:" and the next prompt to run.
</rules>

Confirm my four blocks back to me, then wait for prompt 02.
Click to copy
<role>Underwriter running first-pass triage on a new submission.</role>

<task>
Using the data source I selected in prompt 01, triage the submission.
1. Index what is present versus the standard underwriting file for this line: ACORD application, SOV, 5 year loss runs, financials, supplementals, broker narrative.
2. List the missing items that block a quote, ranked by how much they matter.
3. Summarize the risk in a half page: who, what, where, the operation, and the ask.
4. Make a quick accept / decline-to-quote / refer call with the reason.
Output a one-page submission summary with a red / amber / green completeness call.
</task>

<constraints>Work only from what I provided. Do not fill a gap with an assumption you do not label. If the submission is incomplete, say what is missing before triaging further.</constraints>

<review_gate>State the completeness call and the missing items that block a quote. A submission missing loss runs or the SOV is not quote-ready.</review_gate>

Then "Next step:".
Click to copy
<role>Risk engineer reading the loss history the way a Munich Re engineer reads it.</role>

<task>
Analyze the loss runs in my data source.
1. Build the loss summary: count, paid, reserved, and incurred by year, for at least 5 years.
2. Frequency and severity trend. Separate attritional losses from large or shock losses.
3. Loss development: are recent years still developing. Flag any open reserves that could deteriorate.
4. Pattern detection: a recurring cause, a single large driver, a deteriorating trend, a class of loss the operation keeps producing.
5. Burning cost: the historical loss cost per unit of exposure, trended to the policy period.
Output a loss analysis with the burning cost and the three patterns that matter for pricing.
</task>

<constraints>Use only the loss runs provided. Separate attritional from large losses, do not blend them. Flag years that are still developing rather than treating them as final.</constraints>

<review_gate>State the trended burning cost and whether the recent years are fully developed. Flag any single loss or pattern that should drive the price or a decline.</review_gate>

Then "Next step:".
Click to copy
<role>Property or casualty analyst sizing the exposure.</role>

<task>
Analyze the exposure base in my data source.
1. For property: build the SOV view, total insured value, by location, occupancy, construction, protection, and exposure (COPE). Flag the top locations by TIV.
2. For casualty: size the exposure base (revenue, payroll, units, fleet) and the hazard grade of the operation.
3. Concentration: where is the exposure clustered, geographically and by type.
4. Data quality: flag missing COPE fields, unvalued locations, or stale values.
Output the exposure profile with the concentrations and the data-quality gaps.
</task>

<constraints>Work from the SOV or exposure schedule I provided. Flag unvalued or missing locations explicitly, do not infer a value into the total. Note where the data quality limits the analysis.</constraints>

<review_gate>State total insured value or the exposure base, the top concentrations, and the data-quality gaps that affect pricing or cat modeling.</review_gate>

Then "Next step:".
Click to copy
<role>Catastrophe analyst screening the natural-peril exposure.</role>

<task>
Screen the catastrophe exposure for this risk.
1. Identify the relevant perils by geography: wind / hurricane, earthquake, flood, wildfire, severe convective storm.
2. For each peril, flag the exposed TIV and the concentration, using the SOV from prompt 04.
3. Frame the catastrophe load: what a model would treat as the average annual loss and the tail (PML), conceptually, and what inputs a full model run would need.
4. Aggregation: how this risk adds to a portfolio that already has exposure in the same zone.
Output a cat screen with the exposed perils, the concentrations, and what a formal model run still needs.
</task>

<constraints>This is a screen, not a licensed catastrophe model run. State clearly that the AAL and PML framing is indicative and that a quote on cat-exposed property needs a real model run (RMS, Verisk / AIR, or your licensed model) reviewed by a qualified analyst per ASOP 38 and 39.</constraints>

<review_gate>State the exposed perils and the concentrations. Confirm that cat-exposed business requires a licensed model run and a qualified review before binding.</review_gate>

Then "Next step:".
Click to copy
<role>Pricing actuary building the technical price from the ground up.</role>

<task>
Build the technical price for this risk.
1. Start from the trended burning cost (prompt 03) as the expected loss cost.
2. Load for ALAE and ULAE, reinsurance cost, expenses, and a profit and contingency load. Show every component.
3. Add the catastrophe load from prompt 05 where applicable.
4. Produce the technical premium and the technical rate (per unit of exposure).
5. Compare to the rate on offer or the expiring rate: rate adequacy, the implied loss ratio, and the rate change needed to hit {{TARGET_LOSS_RATIO}}.
Output the price build-up, the technical rate, and the rate adequacy call.
</task>

<constraints>Show every load as a separate line, do not collapse them. Use only the loss cost and exposures from the prior prompts. This is a technical indication for internal adequacy, it is not a filed rate and not an actuarial rate certification.</constraints>

<review_gate>State the technical premium, the implied loss ratio, and the rate change needed. Label this an internal indication that a credentialed actuary owns and that the carrier can only charge within its filed rates.</review_gate>

Then "Next step:".
Click to copy
<role>Underwriter structuring the terms.</role>

<task>
Structure the terms for the risk.
1. Limit, attachment, retention, and any sublimits the exposure calls for.
2. Deductibles, including per-peril deductibles for cat exposure.
3. Coverage form, key endorsements, and the exclusions this risk needs.
4. Subjectivities required before binding (inspections, missing data, loss control).
5. Where the structure differs from a standard offering and why.
Output the proposed structure with the subjectivities listed.
</task>

<constraints>Base the structure on the exposure and loss analysis, not a template. Name the exclusions and subjectivities explicitly. Flag any coverage the loss history says you should not grant.</constraints>

<review_gate>State the proposed structure and the subjectivities. Flag any term that exceeds appetite or that the loss history argues against.</review_gate>

Then "Next step:".
Click to copy
<role>Senior underwriter checking the risk against authority and appetite.</role>

<task>
Check this risk against my underwriting authority and guidelines.
1. Compare limit, line size, hazard, cat exposure, and price against {{UW_AUTHORITY}} and the appetite I gave you.
2. List every item that breaches authority or appetite and must be referred to a senior underwriter, the CUO, or treaty.
3. Flag any acceptance or rating factor that could be a proxy for a protected class, for compliance review.
4. State what additional sign-off each referral needs.
Output a referral schedule with each item, the trigger, and who must approve.
</task>

<constraints>Do not waive a referral to be helpful. If the risk breaches authority, it refers, full stop. The discrimination-proxy flag is mandatory, not optional.</constraints>

<review_gate>State whether the risk is within authority or must be referred, and list every referral with its approver. A referred risk does not bind on this desk's authority alone.</review_gate>

Then "Next step:".
Click to copy
<role>Independent reviewer recomputing the price from scratch to catch an error before it reaches the quote. You did not see the earlier build. You re-derive, then compare.</role>

<task>
Re-derive the key numbers a SECOND, independent way. Do not copy the earlier prompt outputs. Recompute from the source data, then compare.
1. Loss cost: rebuild the trended burning cost a different way (frequency times severity, against exposure) and compare to prompt 03.
2. Technical premium: rebuild it from loss cost and the loads, independently of prompt 06, and compare.
3. Rate adequacy: recompute the implied loss ratio from the offered premium and your loss cost, and compare to prompt 06.
4. Sanity checks: does the price clear the largest historical loss over a reasonable period, is the cat load present where prompt 05 flagged a peril.
For every comparison, show both numbers and the delta. Anything outside {{TOLERANCE}} (default 5 percent of the technical premium) is a FAIL.
</task>

<constraints>Recompute, do not restate. If you reuse an earlier output instead of re-deriving it, this check is worthless. Claude does the math in chat, so this self-check is your guard. Report deltas honestly, do not round a mismatch to zero.</constraints>

<review_gate>State PASS or FAIL for each re-derivation with both numbers and the delta. Any FAIL blocks the quote until the difference is found. Do not draft the quote on a FAIL.</review_gate>

Then "Next step:".
Click to copy
<role>Underwriter drafting the quote from the priced, checked, and authorized risk.</role>

<task>
Draft the quote using only the numbers and terms produced in this file.
1. The quote letter: insured, line, limit and structure (prompt 07), premium (prompt 06, self-check passed in prompt 09), and the subjectivities.
2. The binder language, contingent on the subjectivities being met.
3. The conditions and the quote validity period.
4. A clean, professional tone. No coverage the structure did not grant. No number the pricing did not produce.
Output the quote letter and the binder draft, ready to format on your paper.
</task>

<constraints>Every figure and term must trace to a prior prompt. Do not quote a price that failed the prompt 09 self-check or a risk that prompt 08 referred without the referral cleared. Mark anything needing input as [INPUT NEEDED]. The quote is subject to a licensed underwriter's sign-off and the carrier's filed rates.</constraints>

<review_gate>Confirm the quote uses the self-checked price and that all referrals are cleared. List the subjectivities. A licensed underwriter signs before this binds.</review_gate>

Then "Next step:".
Click to copy
<role>Underwriter writing the decision memo for the file.</role>

<task>
Write the underwriting file memo that documents the decision.
1. The risk summary and the appetite fit.
2. The loss analysis, the exposure, and the cat screen, in brief, with the numbers.
3. The technical price, the rate adequacy, and the price actually offered, with the reason for any deviation.
4. The referrals raised and how they were resolved.
5. The decision and the rationale, written so an auditor, a reinsurer, or a regulator can follow it.
Output the file memo, dated, with every key figure sourced to a prior prompt.
</task>

<constraints>Document, do not embellish. Every figure traces to the file. Record the human decisions and who made them. This memo is the audit trail, write it as one.</constraints>

<review_gate>Confirm the memo records the price, the deviations, the referrals, and the named human decision. The memo supports the file, it does not replace the underwriter's judgment.</review_gate>

Then "Next step:".
Click to copy
<role>Underwriter managing the book, not just the single risk.</role>

<task>
Set the renewal and portfolio view.
1. Renewal strategy: rate change needed, terms to tighten, and whether to renew, re-rate, or non-renew, based on the loss experience.
2. How this risk adds to portfolio aggregation: cat zone accumulation, class concentration, and large-line exposure.
3. The renewal diary: when to re-underwrite, what to request, and the early-warning signs to watch.
4. The portfolio impact of writing this risk at the proposed terms.
Output the renewal call and the portfolio aggregation note.
</task>

<constraints>Base the renewal call on the actual loss experience and the portfolio, not a default renewal. Flag where this risk pushes a cat zone or class concentration past a comfortable level.</constraints>

<review_gate>State the renewal call and the portfolio aggregation impact. Flag any accumulation that needs a senior or treaty review before writing.</review_gate>

Then "Next step:".

Got the prompts. Want them wired into your actual stack? We map that on a free AI audit.

Book the free audit
🔥 optional · live interactive tool

Open the Underwriting Desk Cost Calculator

Browser-based. No signup. Drop in your numbers and see the trade in real time. Opens in a new tab so the prompts stay where you left them.

Launch the live tool ↗

Rent it forever, or own it once.

For commercial P&C underwriters: 16 prompts that read a submission, pull the loss runs, build the technical price, and draft the quote, moving a risk to a quote in days instead of weeks.

Path A · free

You just did it

The setup rail and every prompt above are free and stay free. The cost is your time, and the risk of wiring it wrong on live data.

Back to the prompts ↑
Path B · done with you

We wire it into your business

We would deliver a deployed underwriting workspace: the prompts loaded into your Claude tenant, governed connectors to your policy admin system, Verisk, and your cat model, the pricing wired to your loss-cost methodology and filed rates, an underwriting authority and referral gate, NAIC AI governance and discrimination-testing documentation, and an audit-ready file binder. Done with you, then handed over so you own it.

Book a build call →
data safety

Before you use live numbers

  • • Run last quarter's numbers first. Live data is not a test bed.
  • • Nothing here uploads to us. It runs in your own Claude account, on your own machine.
  • • A named human reviews and signs every output before it reaches a board, lender, or client.
  • • Mask account numbers and names to the minimum the task needs.
the fine print

Straight answers on ownership

Prompt set authored by consultance.ai. Lloyd's, Munich Re, Swiss Re, Chubb, and AIG are referenced as the underwriting standard the pack matches, no affiliation implied. Your submission and insured data stays in your own Claude tenant; we never see it. 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; the NAIC AI bulletin discrimination testing and human oversight apply. Not legal, actuarial, underwriting, or investment advice.

Want this running in your business, not just your laptop? We build it and hand you the keys.

Book a build callBack to the library

Want this wired into your stack instead of running it yourself? That is our AI deal desk and finance automation service.

the newsletter

AI news worth opening.

The AI tools, launches, and shifts that actually matter, in plain English. New library drops the moment they land.

100% freeNo paywall, everUnsubscribe anytime

More like this

Other builds worth a weekend

All repos →
Finance and data

Free Portfolio Quant Research Desk

For family offices and serious individual investors: run a portfolio backtest, tax loss harvesting, and model risk checks on your own holdings, locally, in your own Claude. Replaces the $250k quant seat you would otherwise hire.

Setup guide →
Finance and data

Private Equity Deal Sourcing Playbook

For lower and mid market private equity origination teams: turn one mandate into a ranked, owner verified proprietary deal flow pipeline. Six Claude agents with Exa and Scrapling replace a rented deal sourcing subscription.

Setup guide →
Finance and data

Free Jira Alternative for Deal Teams

For PE deal teams and IC members still tracking a live process on a sprint board: a self hosted deal tracker your Claude can write to, plus 10 prompts that move a workstream only when the document actually lands.

Setup guide →
Get the free kitBook a call

Forward this to whoever owns the workflow.

The person drowning in this every week is the one who'll actually want it.

Forward by email
in one line

What is Submission to Quote Underwriting Pack?

Submission to Quote Underwriting Pack is a finance and data build in the consultance.ai AI Build Library. For commercial P&C underwriters: 16 prompts that read a submission, pull the loss runs, build the technical price, and draft the quote, moving a risk to a quote in days instead of weeks. It fits commercial P&C underwriters, carriers, MGAs and program managers, and reinsurance desks running submissions through a desk of underwriters and pricing actuaries over 6 to 10 weeks. Setup difficulty is Medium, with 4 plain-English steps.

What does Submission to Quote Underwriting Pack do?

For commercial P&C underwriters: 16 prompts that read a submission, pull the loss runs, build the technical price, and draft the quote, moving a risk to a quote in days instead of weeks.

Who is Submission to Quote Underwriting Pack for?

It fits commercial P&C underwriters, carriers, MGAs and program managers, and reinsurance desks running submissions through a desk of underwriters and pricing actuaries over 6 to 10 weeks.

How hard is Submission to Quote Underwriting Pack to set up?

Medium to set up — one guided setup instruction covering 4 plain-English steps, plus 12 ready-to-run prompts on the resource page.

How would consultance.ai build this out?

We would deliver a deployed underwriting workspace: the prompts loaded into your Claude tenant, governed connectors to your policy admin system, Verisk, and your cat model, the pricing wired to your loss-cost methodology and filed rates, an underwriting authority and referral gate, NAIC AI governance and discrimination-testing documentation, and an audit-ready file binder. Done with you, then handed over so you own it.

What are the licensing terms?

Prompt set authored by consultance.ai. Lloyd's, Munich Re, Swiss Re, Chubb, and AIG are referenced as the underwriting standard the pack matches, no affiliation implied. Your submission and insured data stays in your own Claude tenant; we never see it. 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; the NAIC AI bulletin discrimination testing and human oversight apply. Not legal, actuarial, underwriting, or investment advice.

Want this built into your workflow?

Submission to Quote Underwriting Pack is the starting point. On a free AI audit we map where it fits your stack and what consultance.ai would build around it.

This build comes from our AI consulting and AI implementation practice — see the full AI in finance guide and how we work with CFO teams.

Book your free AI audit