WYEA / Specialty insurance / Investment

Specialty insurance

Investing in workflow automation

Builds start at $30,000, and the monthly investment starts at $7,500, covering hosting, support and all model usage. It starts with a prototype on your own wordings, at a fixed investment agreed before work starts, and the exact build investment is agreed in writing after it.

The steps, and the investment at each

  1. Consultation or demo. The first call is at no charge. The thirty minutes cover what your team spends the day reading, and whether a build is worth doing.
  2. NDA. It is signed before you send us a single document. We prefer your form.
  3. Prototype. It has a fixed investment, agreed before work starts. It produces a working prototype on your own documents, and someone on your team uses it on live work. If it does not earn the build, the engagement ends there, and your documents are returned or destroyed on your instruction.
  4. The build. It is a fixed investment, starting at $30,000, agreed in writing with deliverables and dates before work starts. Your team reviews each release as it lands.
  5. Running it. One monthly investment, starting at $7,500, applies from the day the system goes live.

A prototype puts questions like this one to your own library.

Invented example The insureds, clauses and dates in this example are invented. No client material appears anywhere on this site.

What makes one build a larger investment than another

The build investment reflects the work needed for the engine to read and draft your documents correctly. Four things account for most of it.

  • Document types and forms. A program on two policy forms and a dozen endorsements is a smaller build than a book of manuscript wordings, slips, binding authority agreements and reinsurance treaties. Each type has its own structure, and the engine has to know what attaches to what: which endorsement amends which policy, and which slip belongs to which deal.
  • Entities and markets. If you write through more than one carrier entity or market, the same deal has to be drafted on each one's forms. Each set of forms is set up and checked on its own.
  • The size of the library. The work grows with the number of documents and the years they span. Scans with no readable text go to a person unanswered, so a library with many of them needs a plan for who reads them.
  • The rules to encode. These include your house wording rules, which endorsements go with which program, and where a draft stops for a reviewer. Where your forms and rules cover a point, the draft follows them. Writing each rule down so the engine can follow it is part of the build.

The build is scoped for the system you ask for. Adding underwriters or wordings staff does not change it.

What the monthly investment covers

  • Hosting. Your system is yours alone, with its own database, network and sign-in, and we run it on our infrastructure.
  • Support. The engineers who built the system run it, and they are the people you call when something breaks.
  • Model usage. The engine calls language models from outside providers, and those providers charge for each use. Every one of those charges is inside the monthly investment. None is passed through to you as a separate bill.

Why spend on these projects is hard to predict

In July 2024 Gartner predicted that at least 30% of generative projects would be abandoned after proof of concept by the end of 2025, with escalating costs and unclear business value among the reasons. Its analyst Rita Sallam said such costs “aren’t as predictable as other technologies” (Gartner, July 29, 2024).

That prediction is about the market as a whole. It is also why our engagement runs in this order. The prototype is a fixed investment agreed before work starts and runs on your own wordings, so you see what the engine does with your documents before any build is quoted. The build then has its own fixed investment with deliverables written down, and model provider charges stay inside the monthly investment.

What to ask any provider about the investment

Whichever route you take, these points decide what you pay over the life of the system.

  • Whether model provider charges are included in the monthly investment or billed on top as usage.
  • Whether the build is a fixed investment, and which deliverables and dates are written into the agreement.
  • What changes the investment later: a new program, a new carrier entity, more users or a larger library.
  • Who owns the rules, records and configuration built from your documents, and the terms for taking them with you.
  • Who connects the system to your document store, and who pays when that store changes.

With us, what the system learns from your documents belongs to you, and the terms for taking it with you are written into the agreement before the build starts.

When a shared product is the better fit

If your documents are mostly standard forms, a shared product will usually serve you better, and we say so on the first call. A shared product spreads its engineering across many customers, so it usually needs a smaller investment to start.

See it on your own documents

Book thirty minutes as a consultation on whether a build is worth paying for, or as a demo on your own documents. If it is worth going further, we sign the NDA and agree the prototype as a fixed investment before work starts. Book a demo.

Start a conversation

Tell us which documents take your team the longest.

Thirty minutes. Book it as a consultation on whether any of this is worth doing, or as a demo on your own documents. Say which when you book, or decide on the call.

Prefer to write? We reply within one business day.