What comes next

What was built

An engine that reads a commercial insurance program out of its own documents. It sorts each document, pulls the figures with a page and a printed quote behind every one, resolves the documents into policies and the policies into a tower, holds that tower against a set of requirements, and keeps a client’s file current as new documents arrive. Measured on the sample programs at the model vendor’s published rates, one full reading costs $0.26 to $1.84, and the largest of them, 413 pages, took 148 seconds. At that price a reading can run every time a document arrives, which is what the living file depends on.

Where the engine points next

The engine does not know who is using it. A persona is four choices made on top of it: whose documents fill the book, what one row stands for, which question the file leads with, and what paper comes out at the end.

Built: the broker. The book is a book of clients, a row is a client’s program, the file leads with what is in force today, and the paper is a proposal for the renewal.

Nearest: the vendor compliance manager. The book is a book of vendors, a row is one vendor’s insurance, the file leads with whether the requirement is met, and the paper is the record of that. It reads the policy instead of trusting the certificate, which is the same problem solved at the root.

After that: the risk manager inside the insured. The same engine pointed the other way, proving their own program against the requirements their counterparties impose on them.

What success means

A broker brings a second program. Nothing short of that is a sign of adoption.