.svg)
.svg)
How Eydent took a $30M runoff book in-house in about 45 days
Faced with a $500K+ upgrade to run off a book it was exiting, Eydent built a new claims system with OneShield on AI Hub instead
Explore AI HubUpgrade or Get Off
Eydent had a $30M book of business in runoff. The book was being exited, not grown, but claims were still coming in and still had to be handled.
Its incumbent vendor’s terms were simple: upgrade or get off. The upgrade quote started at $500K, all to keep running a book Eydent was leaving.
Upgrade the Incumbent Platform
A $500K+ quote to run off a book on its way out.
Run It Off Manually
Too big. Never an option at this claim volume.
Take It In-House
No migration path existed, because no one had ever planned for one.
What Eydent Had to Work With
Eydent had 3 things in hand and was missing 3 others. The 3 in hand turned out to be enough.
In Hand
Their Data, in Full
Eydent owned its data and had all of it.
The Reports
Every report the business actually ran on.
Domain Knowledge
Someone who knew the data.
Not Available
Documentation
The platform was never designed to be taken in-house, so none of it had been written down.
Vendor Support
Once the decision was made, the incumbent vendor was out of the picture.
Source Code or Configuration
Never had access to it, and never looked at it.
One Loop, Four Steps
The team ran a single loop on OneShield AI Hub and repeated it until it stopped producing corrections. It took about 45 days from start to finish, with 3 people from Eydent and OneShield.
Frame the Domain
A claim starts with a claim file. A person explains what attaches to it and how the pieces relate.
Write the Specification
AI Hub turns the data structure, data files and reports into a written specification with acceptance criteria.
Correct It
Someone who knows the business marks what’s right, what’s wrong, what doesn’t apply on this line and what’s missing.
Build It
From the corrected fields and relationships, AI Hub builds the screens the business needs.
Steps 3 and 4 repeat until the specification and acceptance criteria are met.
Andy Scurto, the person who knew Eydent’s data, didn’t configure anything during the build. He corrected things, and that was the whole job.
Where It Got Hard
Eydent’s subrogation data had been stored around an old workaround, and AI Hub couldn’t infer the intent behind it. Well-designed data reads far better than data built around a workaround.
How It Grew
The original scope was an inquiry screen. Once people started using it, they asked for the way they actually work. And new claims kept coming in the whole time.
Claims Inquiry
- Look up a claim
- Enter basic accounting data
- Close claims as the book runs down
The Way the Team Actually Works
- Notes and letters
- Document storage and retrieval
- Workflow, because work moves between people
A Full Claims System on AI Hub
- Adjudicating claims, not just closing them
- Authority and security controls
- Multiple companies on one platform
Each addition shipped faster than the one before it. The first release is what made the rest feel routine.
Your next product doesn’t need a new core
Eydent was the hard version, with no source code, no documentation and no vendor support. Your next launch starts with more than that.
A Runoff Book
A $30M book of business in about 45 days, with a team of 3 and no source code.
A Small Book
A program too small to justify configuring your core for it.
A New Product
In market before your core roadmap gets to it.
A New Line
A line of business your core was never set up to write.
The same applies to MGAs and program administrators with programs that don’t fit the systems they run today. If you have access to your data, your reports and someone who knows them, you have what Eydent started with.
What You Bring
Your Data
It’s the specification, and it always was. What changed is that it can now be read fast enough to matter.
Someone Who Knows It
A person who can say what’s right, what’s wrong and what’s missing.
Honesty About the Workarounds
The specification is only as good as the data design. Where data was built around a workaround, someone has to explain the intent.
It runs on OneShield AI Hub, alongside the core you already have.
What’s Your Next Small Book?
AI Hub works alongside any core system, so the book, product or line your core can’t reach doesn’t have to wait.
Ready now? Schedule a Demo
Partner With Us Along Your Technology Journey
OneShield AI Hub is an AI operating system purpose-built for insurance. It gives carriers and MGAs private, secure access to the latest large language models and agentic capabilities, and lets business and IT teams design, deploy and govern AI agents on their terms. AI Hub is licensed as its own product and is compatible with OSE, OMS or any existing core system, so no core system replacement is required.
.svg){kind=logo}
Marlborough, MA
01752-3028 USA
.svg)