The submission is an inbox, not a form.
An email, an ACORD application, an SOV in the broker’s own template, loss runs from several carriers, a risk engineering PDF. Someone re-keys it into the system of record before the underwriter can start.
Industries · Insurance
Submissions, SOVs, loss runs and policies, read and cited before an underwriter opens the file
From the broker’s email to a structured record with a citation on every field. Exceptions go to a person. Nothing writes to your policy system until someone approves it.
Forward a redacted submission. Get the structured record back, with the citations.
Runs in your VPCNo training on your dataCitations on every claimApproval before anything sends
What customers say
“It's good to understand the capability of the platform. That how far, and how quickly you guys can get these things going [...] that has been impressive overall.”
“Lets us get a lot more out of our data than [...] We can sit on top of all of the data in [our data warehouse] as opposed to just, like, our little ingested, you know, three gigabytes semantic models. I think we have a lot of power here.”
“Gave Athena the spreadsheet, explained which column I was trying to figure out, and then ten secs it told me... exactly how the calculation was based on the other data.”
“He wrote the entire stuff. By itself. And I was there, and I was thinking, alright. If I had to write all this stuff, I mean, I would've spent days, days, days.”
“I send that to the programmer and he said, alright. I read your file. I copied the section of the code because he has the right interface, and it works. Wow. Just like magic.”
“One workspace. All different, let's say, avatars of their output data. Right? Suddenly, it's dashboard. Excel is here. PowerPoint is when it's all together. It's very impressive.”
“Use the Athena platform probably closer to the concept and how it was designed, like, with the spaces architecture where you've got a set of primitives and capabilities, and you bring together the right set of capabilities to solve a task.”
“Digital worker, it gets spun up, it gets given access to the toolkits that it needs. It gets given access to the data that it needs. Just exists for the period it needs to exist to perform the task. And then it gets torn back down again afterwards.”
“I like that direction, that concept of the agent is the agent. It becomes an entity in its own right with its own ownership and its own missioning, and you get rid of the gray area and the blurry lines.”
“It was PowerPoint... there was no kind of distinction between the two. So that was killer. And I literally had a meeting on it today, and people said how great it was.”
Verbatim from customer calls. Customers anonymized.
Challenges
What insurance teams have to get right
Every line has its own quirks.
A property SOV, a marine cargo schedule and a cyber questionnaire do not share fields. The extraction rules live in a senior underwriter’s head, and the taxonomy is yours, not a vendor’s.
Claims and renewals are the same problem, later.
A first notice of loss arrives as an email thread. A renewal means comparing this year’s terms with last year’s across two sets of PDFs. Reinsurance reporting means doing it again in a different format.
Use cases by team
What insurance teams run on Athena
Underwriting & submissionsFrom the broker’s email to an underwriter-ready file.
Submission intake
Watch a shared mailbox or take a forward. Classify each item (new, renewal, endorsement, not ours). Extract applicant, limits, locations and dates into your schema, each field cited to its page. Low-confidence items go to an exception queue with the reason. The acknowledgement to the broker is drafted and held for approval.
SOV normalization
Messy exposure schedules mapped into your template in an Athena Sheet. Missing construction, occupancy or year built flagged. TIV rolled up by location and catastrophe zone. Every edit attributed and reversible.
Loss run and renewal comparison
Five years of loss runs from several carriers in one development table. Expiring and renewal terms side by side, differences highlighted, each with its source.
Referral drafts
When a submission falls outside an underwriter’s authority, the referral is drafted with the reasoning attached and routed by your authority table, a sheet your underwriting managers edit.
Policy & wordingReview against your playbook, not a generic one.
Policy and endorsement review
Compare a policy to your standard form. Deviations, exclusions and notice conditions listed with citations. Suggested redlines held for a reviewer.
Coverage-position outline
Given a policy and a claim letter, draft an outline with each point tied to the clause it rests on, for a coverage professional to review. Athena does not give a coverage opinion.
Treaty and contract abstraction
Retentions, limits, reporting obligations and notice dates pulled from reinsurance treaties into a table.
ClaimsTriage and summaries. Never the decision.
FNOL intake and triage
Classify the notice, extract loss details, route to the right adjuster queue by your rules, and flag the items your special investigations team has asked to see. Athena does not decide coverage or deny a claim.
Claim file chronology
A cited timeline for the adjuster, updated as correspondence arrives.
Finance & reportingAssembled, reconciled and explained, for an analyst to approve.
Bordereaux and reporting
Assemble the bordereau from policy data in the cedent’s or capacity provider’s format, reconcile to the ledger, and draft the variance explanations for an analyst to review. Athena does not produce final numbers on its own.
Compliance & distributionRegulatory change and a front door for brokers.
Regulatory bulletin watch
State insurance department bulletins and filings checked on a schedule. A digest with the source document, retrieval time and a short note on why it matters. Monitoring does not replace your compliance team’s obligations.
Broker submission portal
A firm-branded portal for brokers: upload, then submit, then underwriter acceptance, as three separate steps. Brokers do not need an Athena license.
How you go live
Shadow mode first, so you see the accuracy before you rely on it
Four steps. The first two take no risk, because Athena acts on nothing.
Shadow mode. Athena runs next to your team on live submissions, read-only. It acts on nothing.
Publish the accuracy. Field-level accuracy and exception rate against your underwriters’ own entries, on your documents, before anyone relies on it.
Approved writes. Athena prepares each write to your policy system or CRM. A named person approves it.
Automatic for high-confidence cases only. Above the threshold you set, with sampling. Everything else stays in the queue.
Example workflow
A 14-location property renewal, from inbox to underwriter-ready
Illustrative workflow, shown on synthetic data.
Integrations
The systems insurance teams already run
Athena works with the systems you already run, with each user’s permissions, and can run in your VPC.
Mail & files
OutlookGmailSharePointLocal files
CRM & workflow
SalesforceDynamicsServiceNow
Data platforms
SnowflakeDatabricksSQL databases
Policy, claims & rating systems
By API where one existsGoverned browser where none does
Office & collaboration
ExcelWordPowerPointTeamsSlack
What to plan for
Athena is not a policy administration system, a claims system or a rating engine. It works on top of them, reads with each user’s permissions, and writes only after a named person approves.
Security and compliance
What your security and compliance review will ask
Attribution on every field. Zero data retention at every model provider. Nothing writes to a policy or claims system without a named approver.
Runs in your VPC
Managed cloud, your cloud account, on-prem or air-gapped. Same platform in every option.
Zero data retention (ZDR) with every model
No customer data used to train any model. Zero-data-retention agreements in place with every model provider Athena calls.
SOC 2 Type II and HIPAA
Athena holds SOC 2 Type II certification and is HIPAA compliant, relevant for life and health lines.
Attribution on every change
Every field, edit and output carries the session, the person or agent, the model, and the source.
Approval gates
No write to a policy or claims system and no outbound email without a named approver. Default is draft, cite, and ask.
Model governance
AGS records which model, which instructions and which sources sat behind each agent action, so you can explain the work to a regulator.
For every stakeholder
Answers for everyone who signs off
Can we cover more submissions without adding headcount?
Athena takes intake, extraction and first-pass summaries. Underwriters spend their time on judgment, and you see the accuracy in shadow mode before anything depends on it.
Does it decide anything?
No. It triages, summarizes and drafts. A person decides coverage and payment.
Can this run in our environment without our data training a model?
Yes. VPC, on-prem or air-gapped, with zero data retention at every model provider.
How do we explain it to a regulator?
Every output cites its source. Every change has an author and an undo. The log shows the model and instructions behind each action.
What will Athena not do?
It is not a system of record. It works on top of your policy, claims and ledger systems, and nothing writes without approval.
FAQ
Does Athena make underwriting or claims decisions?
No. It extracts, compares, drafts and routes. A named person approves every decision and every write.
Which lines of business?
Any line where the work starts from documents. Start with one line and one inbox.
Does it replace our policy administration system?
No. It reads the same documents your team reads and writes to your systems only after approval.
How do we check it is accurate?
Run it in shadow mode first. You get field-level accuracy and an exception rate measured against your own team’s entries.
Can it run in our environment?
Yes: managed cloud, your VPC, on-prem or air-gapped, with the same platform in each.
Where should we start?
With one line, one mailbox and 20 redacted submissions.
One platform underneath
AGS · Athena Governance System
Records every change by a person or an agent, rolls back one contributor's edits without losing anyone else's, and keeps the model, instructions, and sources behind each agent action.
Palladium · deployment
How the platform is deployed: Athena's managed cloud, your cloud on AWS, GCP, or Azure, on-prem, air-gapped, or GovCloud. Same platform in every option.
How it fits together
Build, Work, and Data on top; 150+ connectors and every surface in and out; one map of the whole platform.
Related
Athena Library
Run this on a schedule
Ready-made insurance briefs you can run on a schedule.
- AI agent starters for insurance8 ready-made starters, 3 that run on a schedule.
- Submission intake sweepNew submissions from your inbox, in one sheet, every week.
- Bordereaux builderThe monthly bordereau, assembled and reconciled.
- State insurance bulletin watchWhat the departments of insurance published, and what it means for you.
Forward us a redacted submission.
We will send back the structured record with the citations.
Runs in your VPCNo training on your dataCitations on every claimApproval before anything sends