WYEA / Specialty insurance
Specialty insurance
Paper more deals with the team you have.
WYEA builds document engines for specialty insurers and MGAs. The engine knows every policy and endorsement you have issued, and every decision your team has made on them, so each new deal starts from all of it. Each line it gives you opens the document it came from.
Under NDA before we see a document · Your documents never train a model
may cancel this Policy by giving thirty (30) days' written notice to the InsuredCondition 7, Cancellation · incepted 1 Apr 2026
the period of notice in Condition 11 is amended to forty-five (45) daysEndorsement 3, amending Condition 11 · effective 14 Jun 2025
cancellation by either party upon thirty days' notice in writingClause 19, Cancellation · incepted 1 Jan 2026
The cancellation clause is in a scanned endorsement that could not be read. Nobody guessed at it. It is on your list.
The insureds, clauses and dates in this example are invented. No client material appears anywhere on this site.
Two engineers build it, run it, and answer the phone when it breaks.
Newport Beach, California. Meet the principals
What we build
What the engine does
It is set up from your forms, clause library, executed deals and house rules.
Answers across everything you have issued
Search forms, wordings, endorsements, slips and executed deals together. You get the passage and the document it sits in.
Read with its endorsements
A policy is read with the endorsements that amend it, so the answer reflects the wording in force.
Quoted from the source
Every passage in an answer is found in one of your documents. Anything that cannot be found is flagged.
Scans go to your team
If a page has no readable text, it comes back to you unanswered.
It remembers, and learns from your team
What it learns is kept as rules and records in your own system. None of it trains a model.
Documents tied to their deals
Which endorsement amends which policy, which deal each document belongs to, and who the parties are. Worked out once and kept.
Decisions carry forward
When a reviewer approves or corrects a clause, the next draft follows that choice. Your team makes each call once.
Current as the library grows
New and revised documents are picked up as they are saved to your document system.
Drafts from your own precedents
Give it the deal inputs and the precedent to start from.
Your rules first
Where your forms and rules cover a point, the draft follows them. Suggested language is labeled until your team adopts it.
One deal, each entity's forms
The same deal can be drafted on the forms of each carrier entity or market you write through.
Your reviewer signs off
Drafts stay drafts until a reviewer approves them. The engine does not issue, bind or send anything.
A record that holds up later
Wordings get questioned years after they were issued, often after the form has changed.
Answers keep their version
An answer points at the document as it read that day. Later edits to the form do not change it.
A name on every answer
Who asked, who approved it, and when.
Copies kept past your file history
Some storage plans keep thirty days of file history. The page you relied on is kept anyway.
What slows insurers down
Three barriers insurers name
In AM Best's April 2026 survey of more than 150 insurers and MGAs, the largest impediments to deploying AI were data readiness, security and privacy, and integration with legacy systems.
Data readiness
It starts from the library you have and reads documents where they already live. Anything it cannot read, such as a scanned endorsement, goes to your team.
How an answer gets checkedSecurity and privacy
One system per insurer, with its own database, network and sign-in. Your documents never train a model. We sign your NDA before we see a document.
What we can claim today, and what we cannotIntegration
Your document system stays the system of record, read with the permissions you grant. Dropbox is the first connector; SharePoint, OneDrive, Google Drive, iManage and NetDocuments are what the connecting work was written for.
Connected sourcesThe terms
What an engagement holds to
Commitments written into the engagement agreement.
Questions
What insurers ask first
Which lines of business is this for?
Any line where the paper is written for the deal: specialty and financial lines, manuscript wordings, program business, binding authorities and reinsurance treaties. If your documents are mostly standard forms, a shared product will usually serve you better, and we will say so on the first call.
Does the engine make underwriting or claims decisions?
No. It locates, drafts and flags. Underwriting, pricing, claims and the decision to issue anything stay with your people.
What will our vendor review ask that you cannot answer yet?
A SOC 2 report or ISO certificate, a third-party penetration test, hosting inside your own cloud account, and keys you hold yourself. We have none of those today. The security page keeps that list current.
Who owns what gets built?
What the system learns from your documents belongs to you. The terms for taking it with you are written into the agreement before the build starts.
What does it cost?
A fixed price for the build, quoted before work starts, then one monthly fee that covers hosting, support and every model provider cost. Nothing is passed through. The engagement model.
Can we see it on our own documents?
Yes. Book a demo, sign the NDA, and within the first week there is a working prototype running on your own wordings.
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.
Thanks. Your message is on its way. We'll reply within one business day.