Lands clean in the system you already run
Structured submission data is pushed into your policy administration system. Below is exactly what is live today, what is in progress, and what we build against your instance — stated plainly, because finding out in a proof of concept is worse.
Integration status, stated plainly
Four destinations, three different levels of readiness.
| System | Status | What that means |
|---|---|---|
| Dayd ALIS | Live in production | Running against production submissions today. Token-based auth, policy and quote lookup, structured posting after human review. |
| Vertafore IMS | In development | Being built now with a design partner. The extraction pipeline that feeds it is live; the connector itself is not generally available yet. |
| Guidewire | Built on request | No off-the-shelf connector. Built against your specific instance during onboarding, on the custom-API path. |
| Custom API | Available | Any system that can accept an authenticated HTTP call. This is how every non-standard system of record gets connected. |
How we think about integrations
Four rules that hold regardless of which system sits at the end.
Your data lands in your system
RM Assistant is the intake layer. Structured records are pushed into the platform your underwriters already work in, rather than creating another place your submission data has to live and be reconciled.
Nothing posts without human approval
Every integration writes only after a person has approved the extracted data in the review queue. This is a property of the pipeline, not a per-integration setting.
The destination is swappable
Document classification and extraction are independent of where the record ends up. Changing or adding a system of record does not mean re-doing the document work.
We say what is not built yet
An integration that exists on a website and not in production is discovered during the proof of concept, which is the worst possible moment. Status on this page is deliberately explicit.
Integrations, answered
Which policy administration systems does RM Assistant integrate with?
Dayd ALIS is live in production. Vertafore IMS is in development with a design partner. Guidewire and other systems are built against your specific instance during onboarding using our custom API path. We state status explicitly rather than listing every system as equally available.
What if our system of record is not on the list?
That is the normal case, and it is handled by the custom API path. If your system can accept an authenticated HTTP call, we can push structured submission records into it. Integration work is scoped against your environment during onboarding.
Does our data stay in RM Assistant?
Records are pushed into your system of record; RM Assistant holds the submission documents and extraction history that produce the audit trail. Data is isolated per tenant, is not pooled across customers, and is not used to train shared models.
Can we start before our integration is built?
Yes. Extraction, confidence scoring and human review deliver value on their own, and most teams begin there while the write path to their system of record is built.
How long does an integration take?
It is scoped against your environment rather than quoted generically, because the variance between instances is larger than the variance between vendors. The extraction pipeline is already live, so the work is confined to the write path.
Tell us what you run
30 minutes. Bring your system of record and a real submission, and we will tell you straight what is live, what needs building, and roughly what that takes.
Book a demoNo sales pressure. We confirm within one business day.