Design-partner pilot
A narrow pilot with a clean exit.
The pilot exists to answer one question with evidence: does a controlled loss-run-to-reserve workflow reduce repeated cleanup and make review easier for your entities? Scope is deliberately small. Exit is deliberately easy.
Objective
Process a defined set of representative loss runs through ingestion, validation, reconciliation, development, and reporting — and measure whether the result is easier to produce, review, reproduce, and regenerate than the current process.
Who is eligible
- Captive managers responsible for recurring loss-run intake across one or more entities
- Consulting actuaries or actuarial teams performing captive reserve analyses
Included workflow
- Ingestion of agreed PDF, XLSX, and CSV loss-run formats
- Field mapping with preserved source values
- Validation, exception logging, and reconciliation of paid, case, and incurred totals
- Normalized claim history and development views
- Repeatable reserve calculations with recorded assumptions and selections
- Controlled PDF, Excel, and structured outputs with version and run identifiers
Required inputs and prohibited data
Representative loss-run files — synthetic or redacted by default. A short kickoff conversation about formats, entities, and the current review process.
Personal health information, claimant identifiers beyond what the workflow requires, and any production data not covered by the pilot agreement and data-sharing procedure.
Deliverables, meetings, and stages
1 · Clinic
One free 15–30 minute session on one difficult loss run: data-quality assessment, proposed mapping, exception list, walkthrough, pilot-fit assessment. Synthetic, redacted, or representative material only.
2 · Scoped run
An agreed set of files processed end to end. Deliverables: validation report, exception log, reconciliation, development exhibits, draft reserve package.
3 · Review & decision
Joint review against the success measures below, a written summary, and a decision to continue, adjust, or exit — with deletion confirmed on exit.
Success measures
Agreed at kickoff and measured, not asserted. Candidates include: percentage of source fields mapped, number and type of exceptions surfaced, reconciliation accuracy, analyst review time, time to regenerate a report, manual spreadsheet steps removed, traceability of assumptions and selections, reviewer satisfaction, fit with the existing approval process, and preferred deployment model.
No time-savings claims are made before they are measured.
Commercial terms
The Captive Loss-Run Clinic is free. It runs 15–30 minutes, uses synthetic, redacted, or representative material, and carries no obligation to continue. There is no charge and nothing to sign to book one.
Pilot participation beyond the clinic is on design-partner terms discussed during that session and set out in the pilot agreement, alongside confidentiality, responsibilities, data retention, and the exit process. Data ownership: uploaded data and generated work products are yours.
After the pilot
Continue on agreed terms, pause, or exit. On exit, data is deleted per the data-handling note and deletion is confirmed in writing. Design partners get a voice in what is built next; they are never quoted, named, or logo-ed without written permission.
Start with the clinic.
Synthetic or redacted data is welcome. Production claim data is not required.