01 / From inventory to payment
How does this work
Start with a simple inventory—not your data. We agree the scope and terms before any sensitive information is shared, and payment follows buyer acceptance.
In some cases, a buyer asks for a small de-identified sample before finalizing—never your whole data stack. If a deal does not go ahead, there is no obligation on your side.
- 01
Inventory first, no data
Tell us which systems you use—such as Google, Microsoft 365, Slack, Salesforce, Zendesk or Jira—plus rough volumes, date ranges and headcount. No files change hands at this stage.
- 02
Indicative offer
Based on your inventory, we usually respond with an indicative price range within 7 to 14 days. You see what your data may be worth before sharing anything sensitive.
- 03
Agreement
If you like the number, you sign our standard license agreement. A deal confirmation locks in the exact dataset, payout, rights and timelines.
- 04
De-identification and delivery
The data is processed and de-identified before any buyer sees it. The buyer then has a review window to confirm it matches what was described.
- 05
Payment after acceptance
Payment is made once the buyer accepts the dataset.
02 / Business data
Records your company already has
Everyday business records can capture something AI needs: real problems, decisions and outcomes. Start with what your company already creates—not new data collection.
Explore your recordsCustomer conversations
Operational workflows
Documents and knowledge
03 / Business data
Tools your team already uses
Potentially useful records may already live in your support, sales, operations and document systems. The first step is understanding where they are—not connecting every account.
Explore your data sourcesExamples of systems
- Zendesk
- Intercom
- HubSpot
- Zoho
- Jira
- Confluence
- Notion
- Asana
- Google Drive
- Dropbox
- Snowflake
- PostgreSQL
Support and service systems
CRM and sales systems
Operations and business software
04 / Business data
Who controls the data
Having a record in your systems is not the same as having the right to license it. A clear understanding of ownership, permissions and restrictions comes before a commercial agreement.
Understand rights and controlEstablish the right to license
Define a specific scope
Review privacy and confidentiality
05 / A first conversation
See if your company qualifies
Tell us what records you have, where they live and roughly how much there is. Scale, quality, licensing rights and AI-lab demand help determine whether there may be a fit.
See if your company qualifiesNo obligation, and no uploads, just a quick estimate
Describe your records and source systems
Discuss scale, quality and licensing rights
Review potential fit before any data transfer
An estimate is not an offer to buy or pay for data. Final offers and payments require review, compliance, data approval by AI labs, and signed agreements.
How it works
Three steps from data to dividends.
Describe
Outline your company’s records, sources and scale. No upload or account connection is needed.
Review
Discuss quality, permissions, privacy and preparation. Define the scope before any transfer.
Agree
Commercial terms and payments require compliance review, AI-lab approval and signed agreements.
Platform
A clear process for your data.
Connect sources
Map the systems holding your business records and discuss export options after scope review.
Agree your scope
Define the dataset, permitted uses, approval requirements and payment terms in writing.
Stay in control
Review rights, exclusions and confidentiality before approving any transfer or agreement.
For AI companies
Ethically sourced training data, at scale.
Discuss potentially useful business records, context, licensing permissions and preparation for your model-development needs.
- →Licensing rights review
- →Defined scope and context
- →Preparation and de-identification
- →Delivery agreed in writing
Company
We believe data creators deserve a share of the upside.
Datumi helps companies explore licensing the business records they already hold, with preparation, rights and confidentiality at the center.
Scope, permitted use, approval conditions and payout are reviewed and agreed in writing before any commercial data transfer.
Questions
Which companies may be a fit?+
Companies with organized business records, useful context and appropriate licensing permissions may be worth reviewing. Scale alone does not establish eligibility. Industry, quality, restrictions and AI-lab demand matter.
What records should we consider?+
Examples include support conversations and resolutions, operational workflows, approved documents and structured business events. These are examples, not pre-approved categories.
Do we need to upload records to apply?+
No. The first check uses descriptions and approximate counts. Do not submit confidential files, customer names, credentials or API keys.
Contact Us
Talk to a human.
Questions about company records, licensing or dataset requirements?
Contact us