Due diligence

The whole data room, read and answered.

Read a data room, answer your diligence questions with citations, and turn the findings into a tracker and a report your deal team signs off.

Discuss your use case
DiligenceProject Juniper · LeasesRed flagFilesTableChat
Juniper - Lease, 1200 Commerce Blvd.pdfp. 22 of 48
§ 19.1

Any assignment of this Lease, including by change of control of Tenant, requires Landlord's prior written consent.

§ 3.2

The term expires on June 30, 2027, with one option to extend for five years.

§ 4.1

Base rent of $41,500 per month, increasing 3% each lease year.

Extracted4 fields
Property1200 Commerce Blvdp. 1
ExpiryJun 30, 2027§ 3.2
Base rent$41,500 / month§ 4.1
AssignmentConsent on change of control§ 19.1
Checks
No consent needed for the transactionChange of control needs landlord consent
Term runs past closing plus 12 monthsExpires 9 months after target close
Rent matches the rent roll
Assign to counselAdd to report

What it handles

The whole data room, read and answered.

Every document in the room is read, your diligence questions are answered with citations, and the findings become a tracker your deal team signs off.

  • Key terms and red flags pulled from each document, quoted from the page and filed against your question list.

  • Every question on your list with its answer, its source and its status, so the team sees what is done and what is open.

  • Ask anything across the data room and get an answer with every document and page cited.

DiligenceProject Juniper · LeasesRed flagFilesTableChat
Juniper - Lease, 1200 Commerce Blvd.pdfp. 22 of 48
§ 19.1

Any assignment of this Lease, including by change of control of Tenant, requires Landlord's prior written consent.

§ 3.2

The term expires on June 30, 2027, with one option to extend for five years.

§ 4.1

Base rent of $41,500 per month, increasing 3% each lease year.

Extracted4 fields
Property1200 Commerce Blvdp. 1
ExpiryJun 30, 2027§ 3.2
Base rent$41,500 / month§ 4.1
AssignmentConsent on change of control§ 19.1
Checks
No consent needed for the transactionChange of control needs landlord consent
Term runs past closing plus 12 monthsExpires 9 months after target close
Rent matches the rent roll
Assign to counselAdd to report

How it fits

From the data room to the report.

Strive reads the room as documents land, answers your question list and keeps the deal team's findings in one place.

Comes in from

  • Data room exportEvery folder and document
  • Deal drivesModels, memos and notes
  • Question listYour diligence checklist
Strive
  1. 01ReadContracts, financials and filings
  2. 02AnswerEach question, with citations
  3. 03CompareAcross documents, flagging conflicts
  4. 04ReviewThe deal team signs off

Goes out to

  • A diligence appTracker, findings and chat
  • Updates in SlackNew red flags to the deal channel
  • The reportFindings exported for the memo

What you can do.

Answer your question list

Each diligence question answered from the room, with the document and page cited.

Find the red flags

Change of control, assignment, litigation and liens surfaced across every document.

Compare across documents

Conflicts between contracts, financials and schedules flagged for the team.

Export the report

Findings and sources exported for the memo once the team signs off.

Security

Security your IT team will sign off on.

SOC 2 Type II audited controls, encryption everywhere, single sign-on and role-based access. Your data never trains a model.

Security

SOC 2 Type II

Independently audited security controls, tested over time.

Europe

GDPR

Personal data handled under the EU's data protection rules.

California

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.

Questions

What people ask about due diligence.

How do we know an answer is right?

Every answer cites the document and page it came from. Click a citation to open the page and check it. Anything that needs a decision can go to a review queue with its source beside it.

We just want the work done. Do we need to build an app?

No. We can build it with you, around the way your deal team already runs diligence, so the first thing they see is their own deal in it. Your team can change it later, or leave that to us.

Does it read spreadsheets as well as PDFs?

Yes. It reads PDF, Word, Excel, CSV, plain text, Markdown, HTML, and PNG, JPEG, TIFF and BMP images. Scanned pages are read with OCR.

Do we pay per seat for the deal team?

No. Viewers and reviewers are unlimited on every agreement.

How do we get the data room in?

Upload an export of the room, or connect the Box, Google Drive, OneDrive or Dropbox folders where the deal documents live. Connected folders can sync on a schedule, so documents added later are read too. Any system with a REST API can connect as well.

Can it handle a large data room?

Yes. Drop in a folder of documents and keep working while it is read in the background. You can ask questions across thousands of documents, and a document already read is not read again.

Which document-heavy job would you hand over first?

Bring one process you want to improve and the information behind it. We build the first version with you in the session, so the first thing you see is your own work, running.

Contact Sales

An hour of your time and a process you know well. That's all it takes.