saascode
insurance & insurtech·run 193 · Jun 2026

RateVault

A sandboxed workbook-to-service workflow that versions rating logic, compares deterministic outputs and requires actuarial and regulatory approval before use.

Genesis score6.72/10
Make RateVault real.0/500
500 more votes and RateVault is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The case

Carriers and managing general agents often maintain rating factors, commission rules and eligibility logic in spreadsheets. Exposing that logic through a governed service could reduce manual execution and preserve which model version produced an output. The supplied research confirms enterprise products that wrap spreadsheets or replace rating engines, leaving a possible mid-market layer.

Spreadsheet execution is not automatically deterministic or safe. Macros, external links, volatile functions, hidden sheets, iterative calculations and user-defined code may not translate. The supplied compiler candidate has an unresolved arbitrary-code-injection vulnerability, making untrusted workbook ingestion unsafe without strong isolation or a different engine. Even exact output parity does not authorize a rate: actuaries, underwriting, filings, contracts and regulators retain authority.

A workbook artifact, hash, source owner, formula graph, unsupported feature, compiled candidate, test fixture, parity result, actuarial finding, filing or regulatory approval, released version, quote request, calculated output, underwriting decision, policy issuance and claim outcome are separate. RateVault provides reproducibility, not actuarial or regulatory approval.

Who pays — and why

A carrier or managing general agent's rating, product or actuarial-operations leader maintaining business-critical workbook models but not replacing the full policy platform.

What it unlocks
An isolated workbook intake inventory covering formulas, links, macros, dependencies and unsupported behavior
Versioned compiled candidates with golden-case parity, property tests and actuarial sign-off
Role-gated calculation calls with exact model version, inputs, outputs, approval state and replay
How Genesis scored it
6.72across seven criteria
tension 8temporal 8blindspot 5buyer 6leverage 8convergence 5why-not 8
8
Productive tension

The product seeks to preserve workbook logic while any silent semantic difference can change a regulated price.

8
Temporal window

Insurance modernization and unbundled feature layers create a current opening.

5
Convergence

Several related concepts support spreadsheet governance, though no direct connection is recorded.

Why it scored well

The input identifies a costly insurance workflow, confirmed adjacent enterprise products and a plausible unbundled governance layer.

What's holding it back

The buyer quartet is incomplete, workbook semantics are complex, a proposed compiler is unsafe for untrusted input, regulatory approval remains external and heavier incumbents exist.

Signals detected4 sources crossed
SignalSupplied competitor research

SignalSupplied market research

SignalSupplied security research

SignalSupplied gap analysis

Direction briefratevault.md
ratevault.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.