Applications
Instead of: applications keyed into your system field by field.
Quote more submissions with the team you have.
Strive checks submissions for missing documents and mismatches in an app built with AI around your underwriting process. Your team reviews the flags and signs off.
Every quote starts with reading.
Your team reads every submission before anyone can price it.
Loss runs
Instead of: five years of loss runs read and totaled by hand.
Schedules
Instead of: vehicle and property schedules checked line by line against the application.
Submission intake, built around your process.
Check submissions, clear appetite and summarize loss runs in views built around your underwriting process. Describe changes to AI in plain language, then review and approve the updated app.
Clearance and appetite: Check every new submission for another broker on file and against our appetite, and hold anything outside our guidelines.
Instead of: every submission cleared by hand before anyone reads it.
Loss runs: Read the loss runs on every new submission, total the claims, and flag any large loss or missing year.
Instead of: five years of loss runs read and totaled by hand.
Instead of: every submission opened file by file before anyone can quote it.
GridAppBoard
Strive reads. Your underwriters decide.
- 1A submission lands.From a broker's email or your portal. Strive logs it and checks for another broker on file.
- 2Strive reads the file.Application, loss runs, schedules and prior policy, checked against each other and your guidelines. Every value links to its page.
- 3Your underwriter signs off.They review the flags and decide what to quote. Nothing goes out without them.
Works with what you have.
Your inbox, your broker portals, and your policy and rating systems. Strive doesn't replace them. It reads what they hold and keeps each submission in one place.
It doesn't rate or price the risk. Your underwriters still do that.
Explore connections- OneDrive
- Gmail
- Box
- PostgreSQL
- Slack
Days of work, done in an afternoon.
Teams cut busy work by 50% or more. Our case studies so far come from finance teams. Here's what changed for two of them.
Security your compliance team will sign off on.
SOC 2 Type II audited controls, encryption everywhere, single sign-on and role-based access. Your data is never used to train AI models.
SOC 2 Type II
Independently audited security controls, tested over time.
GDPR
Personal data handled under the EU's data protection rules.
CCPA
Personal data handled under California's privacy law.
Controls
Encryption
Encryption runs on every layer, built on Google Cloud's security controls. Data is encrypted at rest with keys held in Google Cloud KMS, and every connection is encrypted in transit, including traffic between our own services. The credentials your connections use are encrypted too, and never appear in an app.
- At rest
- AES-256, on Google Cloud.
- Keys
- Held and managed in Google Cloud KMS.
- In transit
- TLS on every connection into the platform.
- Inside the platform
- Traffic between our own services is encrypted too.
- Connection credentials
- Stored encrypted and entered through secure forms. Never shown in apps.
- Exported apps
- Credentials are left out.
No training on your data
Your data is never used to train AI models, and the AI services we use don’t train on it either: we use them on enterprise terms that exclude training. A data processing addendum makes our commitment contractual, and you decide how long your data is kept.
- AI model training
- Your data is never used to train AI models.
- AI services
- Used on enterprise terms, so they don’t train on your data either.
- In writing
- A data processing addendum makes it a contractual commitment.
- Retention
- You decide how long your data is kept.
Single sign-on
People sign in with the identity provider you already use: Google, Microsoft, Okta, or any provider that supports SAML or OpenID Connect. Their groups map to roles in Strive, so the right access follows them in. Systems connect with API keys.
- Providers
- Google, Microsoft, Okta, and any provider that supports SAML or OpenID Connect.
- Protocols
- SAML and OpenID Connect (OIDC).
- Roles
- Groups in your identity provider map to roles in Strive.
- Systems
- API keys.
- Rate limits
- Requests are limited for each organization.
Role-based access
Role-based access control: each person has a role, and the role decides which apps, data and actions they can use. The Assistant works with the same access as the person using it, so it can only see and do what they can.
- Roles
- Assigned to each person, or mapped from groups in your identity provider.
- Apps and data
- A role decides which apps, records and actions a person can use.
- The Assistant
- It has the same access as the person using it, no more.
- Changes it proposes
- They wait for someone with the right role to approve them.
- Actions that cost money
- They ask for confirmation first.
- Organizations
- Each organization's data is kept separate.
Bring us one submission. We'll show you it running.
We build it on mock data and walk you through it before anyone touches real files.
Bring us one submission