What a document engine costs

A document engine from WYEA costs a fixed price for the build, quoted in writing before work starts, and then one monthly fee that covers hosting, support and every model provider cost. The build price depends on your documents, so we quote it after a fixed-price one-week prototype on your own wordings and publish no price list.

The steps, and which ones are priced

1. Consultation or demo. There is 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. One-week prototype. It has a fixed price, quoted before it starts, and produces a working prototype on your own documents. Someone on your team uses it on live work that week. If it does not earn the build, the engagement ends there at the quoted price, and your documents are returned or destroyed on your instruction.
4. The build. It has a fixed price, quoted in writing with deliverables and dates before work starts. Your team reviews each release as it lands.
5. Running it. One monthly fee applies from the day the system goes live.

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

Which cyber policies bound this year change the business interruption waiting period? 118 read · 2 changed · 1 for you

Found

Northwind Logistics, Cyber Policy the Waiting Period applicable to Business Interruption Loss is amended to twelve (12) hours Endorsement 4, amending Section II · effective 1 Apr 2026

Found

Calloway Holdings, Cyber Policy the Waiting Period shown in Item 5 of the Declarations is deleted and replaced with eight (8) hours Endorsement 2, amending Item 5 · effective 1 Feb 2026

For you

Harlow Foods, Cyber Policy

The endorsement schedule is a scanned page with no readable text. It comes to you unanswered.

Each line opens the endorsement it came from. The build is quoted after your team has used this on your own library.

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

What makes one build cost more than another

The build price 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 priced for the system you ask for. Adding underwriters or wordings staff does not change it.

What the monthly fee covers

• Hosting. Your system is yours alone, with its own database, network and sign-in, and we run it on our infrastructure. It does not run inside your own cloud account or on your hardware today. Our security page lists that with the other things we do not have yet.
• Support. The two engineers who built the system run it, and they are the people you call when something breaks.
• Model provider costs. The engine calls language models from outside providers, and those providers charge for each use. Every one of those charges is inside the fee. None is passed through to you as a separate bill.

Why costs in this market are hard to predict

That prediction is about the market as a whole. It is also why our engagement runs in this order. The prototype has a fixed price 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 price with deliverables written down, and model provider charges stay inside the monthly fee.

What to ask any provider about cost

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

• Whether model provider charges are included in the fee or billed on top as usage.
• Whether the build is a fixed price, and which deliverables and dates are written into the agreement.
• What changes the price 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 what it costs to take 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 costs less to start. Many also hold certifications a carrier's vendor review may ask for. We have no SOC 2 report today (see our security page).

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 quote the one-week prototype before it starts. Book a consultation or demo.