- To:
- Operations, HR and knowledge-base owners
- From:
- Sell Company Documents
- Date:
- Re:
Sell Company Documents
A handful of AI training-data buyers now license internal documents: SOPs, policies, manuals, playbooks and wikis. Their published figures are per company, not per page, and they want the documents cleaned of names first. Three answers up front:
Can we license our SOPs?
Usually, if the company wrote them. On its data page, micro1 names SOPs, process documentation and internal knowledge bases as material it wants, and it asks for an established firm with a full-time staff of at least 30. Procedures written for a client, or lifted from a vendor, are not yours to license.
micro1 data partnerships page, read Nov 7, 2026What do buyers pay for documents?
Nobody posts a rate per document. micro1 lists $100K to $3M+ for each company and Scale AI shows an illustrative $10K to $1M+ for each partnership, and both mean whole datasets. Treat both as advertised ranges: not offers, and actual licenses are frequently far lower.
micro1 and Scale AI data partnership pages, read Nov 7, 2026What must be removed first?
Names, emails, phone numbers and IDs of staff and customers, then passwords, keys and internal paths. Scale AI does its own anonymizing on your systems ahead of extraction, yet your own pass should come first.
Scale AI data partnership page, read Nov 7, 2026
Which company documents can be licensed?
Anything the company wrote about how it works, with people taken out. The trouble is material written about people, for clients, or by someone else.
| Type | Example | Who wants it | Personal-data risk | Usually licensable |
|---|---|---|---|---|
| SOPs and work instructions | Month-end close checklist; warehouse receiving procedure | micro1 (lists SOPs and process documentation) | Low | Yes |
| Runbooks and process docs | Incident runbook; new-hire IT setup steps | micro1 (process documentation); Scale AI (documents and files with metadata) | Low | Yes |
| Internal wiki or knowledge base | A Confluence space; a Notion team workspace | micro1 (internal knowledge bases); Scale AI (Jira and Confluence knowledge records) | Medium | Yes |
| Company policies | Expense, travel, security and acceptable-use policies | Scale AI (documents and files with metadata) | Low | Yes |
| Employee handbook | Handbook with PTO, conduct and benefits sections | Not named as a type on any buyer page we read | Medium | Yes |
| Operations and product manuals | Field service manual; customer onboarding guide | Not named as such; nearest is micro1’s "operations records" | Low | Yes |
| Sales and support playbooks | Objection-handling playbook; escalation guide | Not named as such; nearest are micro1’s sales and support records | Medium | Yes |
| Project and meeting docs | Planning docs, retros, meeting notes | micro1 (product planning); Scale AI (documents and files) | Medium | Yes |
| HR case files and reviews | Performance reviews, investigations, payroll exports | Scale AI lists HR records, with employee identities excluded | High | No |
| Client deliverables | Reports, decks or code written for a client | Buyers ask for rights you hold; these are often the client’s | Medium | No |
| Third-party material | Purchased courses, vendor manuals, copies of paid standards | Not yours to license | Low | No |
Disclosure: a buyer named above can pay us once an introduction turns into a deal. The table is written without regard to it.
What has to come out before a buyer sees anything?
Every buyer page we read says it de-identifies. Do it first anyway: you know which names matter and which paths lead somewhere sensitive.
Receiving procedure, revision 4. Owner: , Operations.
Step 3. If the count is short by more than 2%, phone before signing the delivery note.
Step 4. Log the variance in and tag for approval.
Refunds go against account ; the portal login is .
- People. Employee and customer names, emails, phone numbers, employee IDs, signatures and photos.
- Access. Passwords, API keys, VPN details, internal hostnames and file paths.
- Accounts. Customer account numbers, contract values tied to a named client, bank details.
- History. Comments, @mentions, suggested edits and page history, which keep names the body text no longer shows.
- Other people's work. Client deliverables, vendor manuals and purchased templates.
- The full redaction guide, by document type
How do you export a knowledge base?
Not yet. Count first, export once a buyer has scoped what it wants.
- Notion
- Workspace owners can export a whole workspace as Markdown and CSV or HTML from the workspace settings. Names written into page text travel with it.
- Confluence
- Space admins export a space from its settings to HTML, XML or PDF. Count pages per space before choosing which spaces to offer.
- Google Drive
- A Workspace admin can export all users' data with the Data Export tool; a single user can use Google Takeout. Docs convert to Word or PDF formats.
- SharePoint
- No single export button. Sites and libraries are usually copied out by sync or download, or by an admin through Microsoft Purview.
Menu names change often; check each tool's own help pages. Exporting a knowledge base, step by step
Which buyers license company documents, and on what terms?
Four buyers' own pages list documents or workspace content. Their terms, as published:
Last verified November 7, 2026, from each buyer's own page.
| Buyer | What it lists | Published pay | Who qualifies |
|---|---|---|---|
| micro1 Company data partnerships | Names SOPs, process docs and internal knowledge bases outright, beside operations and legal records | Three tiers per company, starting at $100K and running past $3M | A full-time staff of 30 or more, mostly English material; US, UK and Canadian firms most sought |
| Scale AI Data Partnership | Files and documents that carry metadata, Jira and Confluence records, HR records stripped of identities | An illustrative $10K–$1M+ a partnership, rising with delivery cadence; Scale calls this no guarantee | Prefers companies of 40 or more people, yet looks at each case |
| Nyne Company data partnerships | Records more than documents: books of account, CRM, service and ticket history, Asana and Jira projects | Partnerships "commonly worth $100K or more" | Three years trading and a US payroll of 20+ full-time W-2 staff |
| SimpleClosure AssetHub | Shutdown-stage workspaces (Slack, Drive, mail, Notion, Figma) alongside code and IP | Not published | Founders closing their company through SimpleClosure; no written criteria |
Disclosure: several of these buyers reward introductions that end in a signed license. Rows are ordered by how much each page says about documents, and a fee moves nothing here.
Independent: none of these companies owns, funds or endorses this site. Full terms, what we left out, and the changelog
What are company documents worth?
Less than the headline ranges suggest, for most companies. The published figures are for whole operational datasets. Reported sales that included documents show the spread:
- Spirit Airlines' business data, covering staff emails, Teams chats, spreadsheets and calendars, drew a $10 million bid from Google against $7.5 million from Mercor, with de-identification promised before closing. Reuters reported both bids on August 17, 2026; no judge had approved the sale by then.
- On the small side, MIT Technology Review described in October 2026 a closed startup whose code fetched about $25,000. Code rather than documents, but it shows how modest the small end can be.
Our document value check takes headcount, years trading and head-office location, then lists the advertised ranges your company meets the rules for. Not an offer. Actual licenses are frequently far lower.
Sources, with read dates
- micro1.ai/data (opened 11/7/2026)
- scale.com/data-partnership (opened 11/7/2026)
- nyne.ai/sell-company-data (opened 11/7/2026)
- simpleclosure.com/product/assethub (opened 11/7/2026)
- Reuters report by Dietrich Knauth on the Spirit Airlines data sale, Aug 17, 2026, as carried by The Star
- MIT Technology Review (Matthew King), Oct 13, 2026, on wind-down data sales
Which rules decide whether you can license?
Ownership comes first. Your own SOPs and policies, yes. Material produced for clients normally belongs to them under the services contract, and customer personal data is out unless both that contract and the law permit it.
Buyers de-identify, and you still go first. Strip personal details while the files are still inside your walls; whatever a buyer runs afterward is a second pass.
Employee promises count. If a handbook or offer letter tells staff how their information is used, a license has to fit inside that promise.
Your lawyer reads the agreement. Scope of use, exclusivity, deletion and warranties are in the license, not on the buyer's web page.
Estimates are marketing. Advertised ranges and calculators are where a conversation starts. The number that counts is the one written into a signed agreement.
How does a document license usually run?
- Scoping. You describe types, counts and where they live. No files.
- Samples. The buyer asks for a small, cleaned sample or reviews one in your environment.
- Agreement. Scope, rights, acceptance criteria and price go into a written license, reviewed by your counsel.
- De-identification. You clean first, the buyer second. micro1 lets you look over representative samples; at Scale AI nothing ships without your approval of the package.
- Delivery and payment. Only micro1 among these states a payment window: 30 days from acceptance. The others leave timing to the contract.
Questions on file
- Do buyers want documents on their own, or only as part of a bigger dataset?
- Both appear. micro1 lists SOPs, process documentation and internal knowledge bases next to CRM, support and legal records, and its published tiers are per company, not per document. A collection that is only documents is scoped like any other; expect fewer buyers and smaller figures than a full operational dataset. See which documents sell.
- Is there a price per page or per document?
- No buyer we read publishes one. The published figures (micro1 $100K to $3M+, Scale AI an illustrative $10K to $1M+, Nyne commonly $100K or more) are per partnership. Our document value check shows which of those published ranges your company's size even qualifies for.
- Do we hand over the files to get an estimate?
- No. Scoping runs on a description: kinds of document, rough counts, which tools hold them, how much personal detail they carry. Scale AI goes further and does its anonymizing on your own systems, signing off each package with you. At the first stage nobody needs a single file.
- Who owns the documents after a license?
- You do, on every page we read that addresses it. micro1 states that the underlying data stays yours. Nyne leaves ownership and the rights you grant to the signed agreement. A license hands over use, so the scope of that use is the clause your lawyer should read hardest.
- Can a company that has shut down still sell its workspace?
- Yes, and it is the clearest case for documents. SimpleClosure's AssetHub takes workspace data from Google Drive, Notion and Slack for founders winding down. Pay for workspace data is not published.
- Does licensing documents breach employee confidentiality?
- It can, if the documents are about people. A procedure about receiving freight is the company’s; a performance review is about an employee. Keep HR case files out, strip names from the rest, and have counsel check any confidentiality promises in your handbook.
- What do you charge?
- The company pays us nothing. Our income is the referral fee some buyers pay once a license we introduced gets signed. Before any of that, you get the names of the buyers that fit.
Get a quote
Tell us what kind of documents the company holds and roughly how many. We check which buyers’ published rules the collection meets, then tell you who they are.
Note: we make introductions, and the buyer at the other end may pay us for them.
Keep documents, exports, share links and samples to yourself. We work from your description alone.
Filed. Next steps:
- Your answers get compared with every buyer's posted size, region and content rules.
- An email follows, naming each buyer that fits and why, or telling you no buyer fits so far.
- The company's name reaches a buyer only after your yes to that particular buyer.
- Until then, leave the files exactly where they are. Copies are not needed.