Tidewell Underwriting
Automated claims intake and routing across five previously disconnected systems.
Industry
Finance & Insurance
Timeline
11 weeks
Team
2 engineers
Category
Workflow Automation
Where things stood
A single claim at Tidewell touched five disconnected systems, and staff were manually re-keying the same data into each one — the delay was entirely process, not underwriting judgment.
How we got there
System audit
Mapped exactly how a claim moved through all five systems before automating anything, since two of them turned out to be redundant.
Integration layer
Built a middleware layer that pushes claim data to each system automatically as status changes, instead of a human re-typing it.
Exception queue
Routed anything the automation couldn't confidently classify into a review queue rather than forcing every claim through a rigid pipeline.
What changed
5 → 1
Systems requiring manual re-entry
~65%
Reduction in claim intake processing time
0
Weeks of downtime during rollout
Tech stack
Node.js
Runs the middleware that translates a claim update into each downstream system's format.
PostgreSQL
Tracks claim status as it moves through the five connected systems.
REST/SOAP integrations
Bridged two decades-old underwriting systems that only spoke SOAP with three newer REST APIs.
AWS Lambda
Runs each integration as an independent function so one system's outage doesn't take down the others.
TypeScript
Typed every claim-status transition to catch integration mismatches before they hit a live system.
Docker
Packages each system integration as an independent, restartable service.
“Communication was excellent throughout — no black-box weeks, no surprises at launch. Just steady, visible progress.”
Daniel Osei
COO, Tidewell Underwriting
