- The largest published range for hardware records is $45K to $1.35M per company, and it requires native CAD assemblies with feature trees.
- PCB files, drawings and BOMs, firmware, FEA and CFD files and measured test results raise value but do not qualify on their own.
- Keep three figures apart: published ranges, posted budgets for single jobs, and prices a company says it paid.
- Designs owned by customers and ITAR technical data stay out of any license.
- Closing hardware companies are now sold as counted lots of firmware, PCB, simulation and CAD projects.
Who buys native CAD files with feature history from a hardware company, and how much do they pay?
Five kinds of buyer show up in public on 19 November 2026: company data programmes that publish a range, a data company that states what it paid, a programme that names hardware records without a price, a liquidator selling a closed company's archive, and item buyers posting budgets for single jobs. Three kinds of figure appear below, and they are not the same thing. A published range is what a buyer advertises before it has seen your records. A posted budget is what one buyer offers for one job on a job board. A paid price is what a company says it actually paid. None of them is an offer for your archive.
| Buyer or source | Stated range or figure | Type of figure | Records asked for | Date checked |
|---|---|---|---|---|
| Mercor, hardware engineering listing | $45,000 to $1,350,000 per company | Published range | Required: full multi-part assemblies in native CAD with feature trees, designs the company owns. Nice to have: PCB designs and Gerbers, drawings and BOMs, firmware, FEA and CFD files, measured test results | 19 Nov 2026 |
| Telegraph Lab | $450K to "a 70-person engineering firm" | Paid price, as the company states it | CAD drawings, calculations, technical reports, revisions and project specifications | 19 Nov 2026 (page undated) |
| Handshake AI | No range for hardware on its page | None published | Design documentation, specifications, test reports | 19 Nov 2026 |
| AfterQuery | Not published | None published | CAD and design histories, quality processes, supplier coordination. Individual CAD submissions are paused; the company route is open | 19 Nov 2026 |
| Hilco Global, Project Beacon (liquidation) | No price; sale process under NDA | Liquidation lot | 202 firmware projects, 193 PCB projects, 373 simulation models, 424 CAD files, 53,712 engineering emails | 19 Nov 2026 |
| A buyer on a freelance job board | $5,000 to $10,000 for 100+ KiCad projects | Posted budget | Owned KiCad projects with schematics and PCB layouts | 19 Nov 2026 |
In their own words: Mercor's listing requires "Full multi-part assemblies in native CAD with feature trees, not only exported meshes" and "Designs the company owns, not customer IP", for companies of 20 to 2,000 employees, and says the deal "Depends on assembly count and completeness". It names automotive suppliers, aerospace, robotics, industrial equipment, product design consultancies, and EV and drone makers. Telegraph Lab's data partnerships page, read on 19 November 2026, lists "Engineering $450K Paid to the business" next to the 70-person firm; that is the company's own claim, with no date or counterparty named. Handshake's data partnerships page, read the same day, names "Design documentation, specifications, test reports" for hardware and engineering. AfterQuery's portal for individuals says it is "not taking new codebases, CAD designs or financial models right now", while its company page still names "CAD and design histories".
The posted budget comes from a KiCad archive request that lists "Budget / Salary $5,000-10,000" and a "Minimum preferred volume: 100+ KiCad projects" (getFreelancer job post, November 2026). That is roughly $50 to $100 a project before any check of what the projects contain.
We are a 60-person hardware company with 15 years of SolidWorks assemblies, PCB designs and test reports. What is the archive worth to AI companies?
There is no single price, and nobody can give you one before the archive is counted. What the public figures do show is where an archive like that sits. A 60-person company with 15 years of native SolidWorks assemblies fits the size band and the main requirement of the largest published hardware range, $45K to $1.35M. Where it lands inside that range depends on four things the listing and the paid example point to.
- Assembly count and completeness. The listing says the deal depends on both. A vault of full product assemblies with feature trees counts for far more than a library of single parts, which the listing rules out.
- Product generations. The listing asks for several products or product generations, because a model learns most from how a design changed between versions.
- Linked records. Test results, BOMs, drawings, change orders and simulation files that sit next to the assembly they describe add value. Separate folders with no link add less.
- Clean rights. Every design the company owns outright, with no customer IP and no export-controlled program, is one a buyer can actually use.
The other end matters too. If the archive is small, or mostly single parts, the realistic comparison is the item market: a posted budget of $5,000 to $10,000 for 100 owned KiCad projects is one example. The fastest way to know which end you are on is to count assemblies, product lines and years, and to mark which designs belong to customers. The CAD archive value calculator gives a first rough score.
Which hardware records raise the value, and which are excluded?
Buyers describe the same core and the same exclusions. Mercor's listing describes "native CAD vaults: complete assemblies with their feature history, circuit board designs, drawings and the test results that go with them". A liquidation listing that sells a whole archive describes its strength as "Related code, schematics, simulation, CAD and correspondence" (Hilco). In both, the value is in the links between records.
- Core: native CAD assemblies with feature trees and revision history. See licensing CAD and engineering data and the SolidWorks PDM and Vault guide.
- Raises value: PCB projects and Gerbers (Altium and KiCad guide), drawings and BOMs, firmware (firmware guide), FEA and CFD files (simulation archives), and measured test results (EVT and DVT test reports).
- Also named by buyers: calculations, technical reports and project specifications (Telegraph Lab), and quality processes and supplier coordination (AfterQuery).
- Excluded: single parts or parts catalogs, designs owned by your customers, exported meshes without native files, ITAR technical data and any program a customer or government contract restricts.
Our engineering firm designed parts for clients. Do we own the CAD files enough to license them for AI training?
Often not, and this is the question that rules most service firms in or out. Under US copyright law a work made by an employee belongs to the employer: the Copyright Office's circular describes a work made for hire as "A work prepared by an employee within the scope of his or her employment" (U.S. Copyright Office). So your firm usually owns what its staff drew. But most client agreements then assign the deliverables to the client, and a design made to order for a client counts as a work made for hire only in nine listed categories and only "if the parties expressly agree in a written instrument signed by them". CAD models are not one of the nine, so the contract's assignment clause decides.
In practice: read each client agreement for an assignment of deliverables and for confidentiality terms. Designs you assigned, or that carry a client's confidential information, need that client's written consent. Your own products, internal tools, templates and unassigned work are usually yours. Mercor's listing states the same line from the buyer's side: designs the company owns, not customer IP. The full analysis is in who owns CAD files, the consultancy or the client.
Are there export control issues with licensing CAD files and engineering drawings to an AI company?
Yes, for some programs. Under the ITAR, technical data is information "required for the design, development, production, manufacture, assembly, operation, repair, testing, maintenance, or modification of defense articles", and it "includes information in the form of blueprints, drawings, photographs, plans, instructions, or documentation" (22 CFR 120.33). In plain terms: drawings and models of a defense article are controlled, and they stay out of any AI license.
Commercial designs fall under the EAR. Most are EAR99, and the Bureau of Industry and Security says "EAR99 items do not require a license for export, reexport, or transfer (in country) in most situations", with exceptions for restricted end users, end uses and destinations (BIS). Controlled technology is different, and BIS reminds owners that "A deemed export refers to the sharing or release of controlled technology or source code to a foreign person within the United States" (BIS). So ask who at the buyer will open the files. The ITAR and EAR checklist walks through classification program by program.
Our hardware company is closing. Who would buy our CAD files, firmware and engineering records?
The same buyers as above, plus a route that is new in 2026: a liquidator packaging the whole archive as one lot. Hilco's Project Beacon offers a closed wireless-power company's "Proprietary engineering corpus spanning embedded software, electronics design, simulation and modeling, mechanical CAD, and dated engineering design history" (Hilco). The lot is counted in projects and files: 202 firmware projects, 193 PCB projects with 856 schematic sheets, 373 simulation models, 424 CAD files and 53,712 engineering emails from August 2017 to January 2024. No price is published; interested parties sign an NDA to join the sale process.
Two points follow for a closing company. First, export the vault with its history before systems are switched off, because a CAD archive without feature history fails the main requirement buyers publish. Second, only the party in control can sign: the board in a wind-down, the assignee in an assignment for the benefit of creditors, or the trustee in a Chapter 7 case. The hardware startup shutdown guide covers both steps, and estate records for trustees and assignees covers the sale side.
Which companies help hardware engineering firms license their CAD and test data to AI labs?
Three kinds of company do this work in public. Buyers run their own programmes and talk to companies directly; the table above lists the ones that name hardware records. Liquidators such as Hilco sell archives when a company has closed. Independent data partners help an operating or closing company count its records, separate what it owns, and put the archive in front of more than one buyer.
We help you license your data. Origin Data Partners is an independent data partner. Your company decides what is shared and signs any license itself, and a buyer may pay Origin when a deal closes. Origin never takes the records itself; the license is between your company and the buyer. If you hold an archive like the ones on this page, the two-minute estimate is the first step, and nothing leaves your systems until you decide.
Mercor offered to license our hardware company's CAD and circuit design archive. Is the offer fair, and what should we ask?
Start with the published band. Any offer from a programme that publishes $45K to $1.35M for hardware companies should be read against that range and against what drives it: assembly count, completeness, product generations and linked records. An offer near the floor for a large, complete vault with test results deserves questions. An offer near the ceiling for a small archive deserves a careful read of what you are giving up.
- Which designs are in scope, counted how: assemblies, parts, PCB projects, files or years?
- Is the license exclusive or non-exclusive, and for how long?
- May the buyer resell or sublicense the files, and to whom?
- What happens to the files and to models trained on them when the license ends?
- Who checks for customer IP and export-controlled data, and who carries the risk if something slips through?
- When is the money paid: at signing, on delivery, or after the buyer accepts the data?
The data offer checker compares an offer's terms with these points, and how to review a data licensing offer goes clause by clause.
What should a hardware company check before signing a data license for its CAD files and test results?
Run the checks in this order, because each one can remove records from the deal.
- Ownership: list every design made for a client and read the assignment and confidentiality clauses.
- Export control: classify each program as ITAR, an EAR ECCN or EAR99, and leave controlled programs out.
- Third-party content: vendor part libraries, purchased models and licensed IP blocks inside the files.
- People: names and emails in title blocks, change orders and engineering emails, and whether to remove them.
- Scope: name the systems, programs and years in the license, not "all engineering data".
- Use limits: training use only, no resale, deletion at the end, and an audit right.
This page is general information, not legal advice. The data licensing agreement guide explains the clauses.
How do three hardware archives compare? A worked example
This is an illustration written for this page, not real companies or offers. It shows how the same buyer requirements sort three archives that look similar from the outside.
| Archive | What it holds | How it reads against published requirements |
|---|---|---|
| A: 80-person robotics maker, 12 years | Native SolidWorks assemblies with feature trees for five product generations, linked BOMs, ECOs, DVT reports and firmware | Meets the core requirement and most nice-to-haves. A candidate for the upper half of the published company range |
| B: 30-person design consultancy, 10 years | Hundreds of client projects in native CAD, plus a small set of in-house products | Most files belong to clients. Only the in-house products qualify without consent, so the licensable archive is small |
| C: 15-person PCB design house, 8 years | 400 KiCad projects it owns, few mechanical assemblies | Below the company size floor of the largest listing. Closer to the item market, where one posted budget offers $5,000 to $10,000 for 100 projects |
The lesson from the example: count first, then sort by owner, then by export status. The archive that remains after those three steps is the one a buyer prices.
What is the first step for a hardware company that wants to license its engineering data?
Write down four numbers before you talk to any buyer: native assemblies, product generations, years of history, and the share of designs your company owns outright. Add which programs are defense or export-controlled. That one page is enough for a first conversation, and no file needs to leave your systems to produce it.
Origin's two-minute estimate asks the same questions. The EVT and DVT test reports, firmware and simulation archive guides cover each record type in more depth.
Origin Data Partners works with companies that own data and helps get it bought. We are independent of the services on this page, and a buyer may pay us when a deal closes (how Origin is paid). See what your data is worth.
Common questions
Do AI companies buy old product design files from hardware companies that are closing down?
Yes, when the files are native CAD with history and the company owns them. In 2026 a liquidator, Hilco, began selling a closed hardware company's archive as one lot, counted as firmware, PCB, simulation and CAD projects plus engineering emails, through an NDA sale process with no published price. Export the vault before systems close, because buyers require feature history.
I am the lawyer for a product design consultancy. Can it license its engineering archive to AI companies, and what should the contract say?
It can license what it owns: its own products, internal tools and work it never assigned. Client designs are usually assigned by contract and need written consent. The license should list the programs and years in scope, exclude client and export-controlled data, limit use to training, bar resale and sublicensing, require deletion at the end and give an audit right.
A data buyer offered our 40-person hardware company $150,000 for its CAD vault. Is that fair?
It sits inside the largest published hardware range, $45K to $1.35M, so it is not out of line on its face. Whether it is fair depends on how many complete assemblies, product generations and linked test, PCB and simulation records you hold, and on the terms: exclusivity, resale, deletion and when payment arrives. Count the archive before you answer.
Is a STEP export enough for a hardware engineering data license?
Usually not on its own. The largest published hardware listing requires full multi-part assemblies in native CAD with feature trees, not only exported meshes. STEP files lose the feature history that shows how a part was built and changed. Keep STEP exports as a companion to the native files, never as a replacement for them.
How much is a single PCB or CAD project worth to an AI data buyer?
Very little on its own. One posted budget offered $5,000 to $10,000 for 100 or more owned KiCad projects, roughly $50 to $100 a project, and that is a budget, not a paid price. Company-level ranges exist because a whole archive with history, versions and linked test records is worth far more than its parts.
Does a hardware company need to be in the US to license its engineering data?
No. Mercor's hardware listing gives its location as Anywhere, but export law follows the data. A US company checks the ITAR and the EAR before any file leaves; companies elsewhere check their own export rules and any US-origin technical data they received from suppliers or customers. Classify each program before you count it in.
Why did a company data programme stop taking individual CAD submissions?
AfterQuery's portal for individuals says it is not taking new codebases, CAD designs or financial models right now, while its company page still names CAD and design histories. The public signal is that single designers' files are not wanted at the moment, while company archives with history still are. AfterQuery has not published a reason.
Sources and further reading
- Mercor: Hardware Engineering Company listing (listing data, read November 19, 2026)
- Hilco Global: Project Beacon, wireless powering tech code and technical data assets
- U.S. Copyright Office: Circular 30, Works Made for Hire
- eCFR: 22 CFR 120.33, technical data (ITAR)
- Bureau of Industry and Security: Classify your item (EAR99)
- Bureau of Industry and Security: Deemed exports
