DEFINE THE LOSS BEFORE THE PRICE
Define the loss.
Then discuss the price.
An agent’s value can indicate business dependence, but it is not automatically an insured loss. Risk discussion also needs permissions, exposure, controls and verifiable evidence.
| Context | Possible event | Loss to define | Key question |
|---|---|---|---|
| Personal assistant | Wrong bookings, file changes or purchases outside authorization | Non-refundable spending, direct expenses and restoration | What was authorized, and has any refund already been received? |
| Business agent | Incorrect payments, interruption or erroneous customer commitments | Net funds lost, evidenced interruption and third-party claims | Who held the tool permissions, and can approvals be traced? |
| Sensitive information | Disclosure of private or confidential content | Investigation, notification, remediation and related liability | Which data, recipients and contractual boundaries are involved? |
| Unauthorized activity | Execution after revocation or changed oversight | Containment, forensics, recovery and affected operations | Are controls independent of the agent? |
Make the coverage discussion specific
Specify the protected person or organization, agent and tools, event trigger, loss calculation, deductible, limit, waiting period, exclusions and evidence. An agent can submit structured information; doing so does not itself create an insurance contract.
Separate probability from consequence
An experiment shows a possible behavior; it does not tell you how often your workflow will experience it. Explore loss and limits using explicit assumptions, then calibrate with operational and incident data. Keep unsupported inputs uncertain.
AgentCover is a research and calculation prototype. There is no policy, insurer, premium collection or claims service. These questions are a design framework, not a promise about any existing insurance product.
Open the pricing sandbox →