saascode
insurance & insurtech·run 050 · Apr 2026

Coilattice

A small-business certificate-of-insurance workspace that versions requirements and documents, routes discrepancies for review, and keeps extracted evidence separate from coverage conclusions.

Genesis score6.45/10
Make Coilattice real.0/500
500 more votes and Coilattice 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

Small businesses often depend on dozens of vendors but track insurance certificates through inboxes and spreadsheets. A document may be present while naming the wrong insured, showing limits below the current requirement, omitting a required endorsement or no longer reflecting active coverage. Expiration reminders solve only one part of that problem.

Coilattice gives each business a versioned requirements register and each vendor a permissioned upload path. It extracts candidate fields from certificates, cites their locations and compares them with the applicable requirement set. The result is a discrepancy queue for human review, not a compliance score. The original file, extraction confidence, reviewer finding and any broker or carrier verification remain distinct.

Requests, reminders and delivery events are recorded separately from vendor responses and replacement documents. A certificate can be reused for another customer only with explicit vendor permission, and reuse never means it satisfies that customer's different requirements. Waivers and exceptions require named approval.

The output is a practical evidence pack showing requirements, documents, review findings, requests, responses and corrections. It does not prove that a policy is genuine, in force, sufficient for a loss or applicable to a particular contract. Those conclusions remain with qualified risk, insurance and legal reviewers.

Who pays — and why

Operations, procurement, property or risk leader at a small business that depends on recurring vendors, with brokers as a possible distribution partner

What it unlocks
A tenant-separated requirements register linking each vendor relationship to the exact insurance rules and version that apply
A certificate-review queue separating source files, extracted field candidates, confidence, endorsements, discrepancies, reviewer findings and broker or carrier verification
A follow-up ledger separating requests, reminders, delivery events, vendor responses, replacement documents, waivers, approvals, corrections and exportable evidence
How Genesis scored it
6.45across seven criteria
tension 6temporal 7blindspot 5buyer 7leverage 7convergence 5why-not 7
7
Temporal window

The supplied research identifies current category activity and a reported small-business packaging gap.

7
Buyer persona

Operations, property, procurement and risk roles have a recognizable recurring vendor-document problem.

5
Convergence

The supplied record has two cross-references and two inbound connections.

Why it scored well

The supplied research confirms a fragmented category, a small-business pricing gap and document-extraction services that make focused workflow automation practical.

What's holding it back

A close small-business competitor exists, document extraction is not coverage verification, requirements vary by relationship and the proposed vendor network depends on explicit permission and sustained participation.

Signals detected3 sources crossed
SignalSupplied competitor and market research

SignalSupplied interface and product research

SignalSupplied competitor research

Direction briefcoilattice.md
coilattice.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.