Process

From dormant archive to cleared payment.

Six stages, 30 to 60 days, and almost none of the work lands on your team. Here is exactly what happens and when.

At a glance
ManifestDay 0ValuationDays 1–3AgreementDays 5–15AnonymizeDays 15–35TransferDays 35–50PaidDays 40–60

The 30–60 day pipeline

From intake form to cleared payment, with most of the work on our side.

Workspace & communication
Google WorkspaceGmailGoogle DriveMicrosoft 365OutlookSharePoint
Planning & project tracking
JiraAsanaLinearMonday.comClickUpTrello
Customer, sales & finance
HubSpotSalesforceZendeskIntercomFreshdeskNetSuite
Engineering & data stores
GitHubGitLabBitbucketAmazon S3Azure Blob StorageGoogle Cloud Storage

What systems we buy from

Connectors for most SaaS; secure push endpoints for everything else.

Entity detectionIdentifier strippingHuman auditClient approval

Inside the anonymization pipeline

Automated redaction plus human spot-audit before anything leaves your tenant.

$100K–$500K25–100$450K–$1.2M100–500$1M–$1.8M500–2K$1.8M–$2M+2K+

How headcount maps to payout

Headcount sets the band; years, systems and volume place you inside it.

Timeline

The six stages.

Between the manifest and the wire, our team spent under four hours total. Legal spent one.
Head of IT · healthcare administration group, 640 employees
  1. 01

    Data manifest

    Day 0 · 2 minutes

    You describe your company, your systems, and roughly how much data sits in each. No credentials, no exports, no engineering time. This is the only step that requires anything from you before a price exists.

  2. 02

    Valuation call

    Day 1–3

    We benchmark your manifest against live demand and return a written range. Headcount sets the band; years covered, system diversity and volume place you inside it.

  3. 03

    Licensing agreement

    Day 5–15

    A single non-exclusive data licensing agreement between you and Corpus. No fees, no revenue share, no ongoing obligation. You retain full ownership of the originals.

  4. 04

    Anonymization review

    Day 15–35

    Automated multi-pass redaction plus human spot-audit. You receive a redaction report with samples and category-level statistics, and you sign off before anything transfers.

  5. 05

    Transfer

    Day 35–50

    Read-only connectors for supported SaaS, or a one-way encrypted push to an isolated blob endpoint for everything else. Your technical lead's IP is whitelisted in advance.

  6. 06

    Payment

    Day 40–60

    Payment clears on delivery confirmation. Larger engagements can be structured as an upfront tranche plus a delivery tranche.

Coverage

Every major system your company runs on.

Read-only connectors handle most SaaS. Anything else, your team pushes to a secure endpoint we provision.

Workspace & communication

Google WorkspaceGmailGoogle DriveMicrosoft 365OutlookSharePointSlackMicrosoft TeamsZoomDropboxBoxNotionConfluenceDocuments

Planning & project tracking

JiraAsanaLinearMonday.comClickUpTrelloSmartsheet

Customer, sales & finance

HubSpotSalesforceZendeskIntercomFreshdeskNetSuiteQuickBooksStripeWorkday

Engineering & data stores

GitHubGitLabBitbucketAmazon S3Azure Blob StorageGoogle Cloud StorageSnowflakeBigQueryPostgreSQLInternal data lake

Once anonymized, everything we acquire is used to train and evaluate leading AI models. Running something not listed? Add it in the intake form and we will scope it during the valuation call. Push-only systems are priced the same as connector-backed systems.

Find out what your archive is worth.