InsightAdvocate is one product in VerticalServe’s Insight suite. It runs on its own — its own database schema, its own policies and letters — and it shares a platform with the broker products beside it and the carrier products across the table. This post says what connects today and what is designed but not yet wired.
claims advocacy"] -- "loss brief for the renewal" --> IP["InsightPlacement
renewal and placement"] PR["InsightProofing
policy checking"] -. "the policy as issued" .-> IA X["InsightXtract
document reading"] -. "carrier letters into positions" .-> IA PU["InsightPulse
company 360"] -. "client profile and news" .-> IA IA <-. "same claim, other side" .-> CW["InsightCW
carrier claims"]
Solid: prepared in the product today (sent as a dry run). Dotted: designed, or done today by a stand-in.
InsightPlacement: the loss story into the renewal
The loss-trend analyst prepares a brief for the placement team when a client with an open claim renews. In InsightPlacement the same loss runs feed renewal readiness and the submission’s five-year loss history. Today the brief is a document sent as a dry run, not an automatic exchange. The use case shows it.
InsightProofing: the policy as issued
Half of reading a carrier’s letter is knowing exactly what wording the client was issued. InsightProofing is the broker’s policy-checking product: it compares the policy issued with what was bound. A position that cites an endorsement the client was never issued is the claims-side echo of a proofing discrepancy.
InsightXtract: letters into positions
A carrier letter becomes positions on the claim. Today a stand-in reader does this inside InsightAdvocate, and the screens say “read by Xtract (stand-in)”. InsightXtract, the suite’s document reader, is the intended reader.
InsightCW: the same claim from the carrier’s side
InsightCW is the carrier’s claims workbench. Its coverage agent prepares a reservation of rights; InsightAdvocate’s coverage engine reads one. Both cite the policy at the loss date, both keep a decision record, both cap their agents at ask first. They are separate products for separate firms and do not share data.
InsightPulse: the company 360
InsightPulse keeps a company profile and news on each client; InsightPlacement already reads it for submissions. For claims, the same profile gives the advocate context on a client’s operations. It is a designed connection for InsightAdvocate.
The shared platform
| Package | What InsightAdvocate uses it for |
|---|---|
insight_agents | The agent pipeline, registry, autonomy, traces |
insight_decisions | The decision record and sign-offs |
insight_rules, insight_broker | Rules Studio and claim controls; the broker roster |
insight_diligence | The agents’ model kit and grounding helpers |
insight_assist | The copilot |
insight_home, insight_identity | Home per persona; sign-in, roles, tenancy |
