FurtherAI × YC
Domain Specific AI for Insurance (a16z, YC)
The production was done well and the video delivered in a good way.
About
Underwriting and claims finally talking to each other without a six month integration project would be genuinely useful. Curious how you handle the carrier-specific schema chaos though.
Naive question but if underwriting and claims have always been separate systems, who at the carrier actually owns the budget for a cross-functional tool? Seems like nobody and everybody.
Insurtech keeps getting smaller every year and yet every quarter someone announces the orchestration layer for it. At some point the layer is going to be thicker than the cake.
Would love to chat about which carriers are in the early design partner cohort whenever you have ten minutes. Off the record is fine.
ok wait, an orchestration layer means nothing if the underlying carrier APIs are still SOAP from 2009. how are you actually moving data between these legacy systems?
Where does the PII sit when claims data crosses the underwriting agent? Need to know before I let anyone on my team open a sandbox.
This is probably the last insurance product anyone ships before the entire stack becomes agents calling agents. Bookmarking this tweet for the museum.
The tweet got cut off mid-sentence on the most important word. Bold strategy to launch with a cliffhanger on 'AI'.
Site is clean but the hero section has three different greys fighting each other. Pick a neutral and commit.
Every vertical eventually gets the orchestration layer it deserves. Insurance has been waiting a long time.
Are there webhooks for claim status changes or am I polling forever? Also what does rate limiting look like during a CAT event when everyone fires at once?
hot take: vertical AI infra companies are going to eat horizontal orchestration platforms alive over the next year. we're 3 weeks from shipping something adjacent in healthcare and the playbook rhymes.