Fee checks
Instead of: fee terms dug out of side letters and recalculated in Excel every quarter.
Get quarter-end work off your team's plate.
Strive turns fee checks, side letter reviews and new commitments into apps built with AI around your office's process. Your team checks the work and signs off.
Quarter-end still runs on spreadsheets.
The work too particular to your office for any one software product, and too much for one person to check by hand.
Side letter rights
Instead of: every side letter reread to see which rights apply this quarter.
New commitments
Instead of: subscription documents filled in by hand for every new fund.
Quarter-end, built around your office.
Check fees, track rights and prepare commitments in views built around your managers, terms and sign-offs. Describe changes to AI in plain language, then review and approve the updated app.
Side letter rights: Read every side letter, list the rights we hold with each manager, and flag anything a manager didn't honor this quarter.
Instead of: every side letter reread to see which rights apply this quarter.
New commitments: Fill the subscription documents for our new commitments from our records, and flag anything that doesn't match.
Instead of: subscription documents filled in by hand for every new fund.
Instead of: fee terms dug out of side letters and recalculated in Excel every quarter.
GridAppBoard
Strive reads. Your team signs off.
- 1The documents come in.From email, manager portals or the tools you already run. Strive files each one with its manager.
- 2Strive checks the work.Fees, rights and commitments, checked against your LPAs, side letters and records. Every value links to its page.
- 3Your team signs off.They review the flags and approve what goes to a manager or the committee. Nothing goes out without them.
Works with what you have.
Your email, your manager portals, your accounting system and whatever you already use to collect statements. Strive doesn't replace them. It reads from them and keeps each quarter-end task in one place.
It doesn't replace your portfolio or accounting system. It does the checking around them.
Explore connections- OneDrive
- Gmail
- Box
- PostgreSQL
- Slack
Days of work, done in an afternoon.
Teams cut busy work by 50% or more. Here's what changed for two firms that moved their onboarding work onto Strive, in their own words.
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 quarter-end task. 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 quarter-end task