Data partnerships
Your company’s archive, licensed.
Mapier turns the chat, email, documents, tickets and code a company has built up into a licensed dataset for teams building AI agents.
How it works
Four steps, in this order.
Nothing is connected and nothing is signed until the step that says so.
Apply
Tell us about the company, the tools it ran on and the rights it holds. Answers save as you go, so you can stop and come back.
We review it
Someone on our team reads every application and replies by email.
NDA, then a licence
If it’s a fit, you sign an NDA first. Then we write the data licence with you: what it covers, for how long, and the price.
Tool access, then payment
Once both are signed, our team arranges access to the tools the licence names with you, and you are paid on its terms.
What we look for
The things that shape an archive’s value.
No single one decides. Tell us what is true and we will tell you where it leads.
Team size, today and at peak
A team that was larger once left a larger record. We ask for both numbers.
Years of history
How long the company has been working, and how far back its records go.
The tools you ran on
Chat, email, docs, tickets, CRM and code: wherever the day’s work was written down.
Rights you hold
Whether the company can license its records for AI work, and whether anyone holds them already.
Mostly in English
Records written mostly in English. If yours are not, tell us when you apply.
Who applies
Three kinds of company, one application.
You pick one early on, and the questions that follow are the ones that fit it.
General business
The everyday records of running a company, from engineering to finance.
Engineering, sales, support, finance, legal, people
Health or life sciences
Clinical, research or payer data. At intake you describe it; nothing is uploaded.
Providers, payers, pharma, diagnostics, research
Data or code firm
You hold code or data that came from several companies, and the right to license it.
Agencies, dev shops, wind-down buyers, data marketplaces
How we work
What we do, stated plainly.
Applying commits you to nothing
Sending the application is not an agreement. Nothing is binding until you sign one.
You set the scope
You decide which tools, and which parts of them, are in. The licence writes that down.
A person reads every application
Staff review each one by hand. Nothing is approved automatically.
Agreements before any data moves
An NDA and a signed data licence come first. No tool is connected before both.
Questions
Before you apply.
Who can apply?
Any company that holds the records of its own work, and firms that hold code or data from several companies with the right to license it.
Does the company need to still be operating?
No. Companies that are winding down, or have closed, can apply as long as someone can still sign for the company and the records still exist.
What data are you interested in?
The everyday record of work: chat, email, documents, tickets, CRM, call notes and code. Health and life-sciences companies answer their own set of questions.
How does pricing work?
We scope a price with you once we understand what you hold, and it goes into the data licence. Nothing is binding at intake.
What happens after I send it?
Someone on our team reads it, and we reply by email either way.
What happens to the application if you decline it?
We tell you by email. If something changes later, reply to that email and we can reopen it rather than ask you to start over.
Can teammates see the application?
The people you invite, each as an admin or with view-only access, and the Mapier staff who review it.
Do I need an account?
You sign in with your work email and a six-digit code. That is your Mapier account.
Start with one application.
Answer the questions, save as you go, and send it when it is ready.