Don't Do It Yourself

How to Sell Hardware Engineering Data to AI

A hardware engineering company sells its data to AI by licensing its own CAD assemblies, circuit designs and test results to a buyer like Mercor.

Mercor pays hardware engineering companies $45,000 to $1.3 million. It wants several product generations from a company with 20 to 2,000 employees, anywhere.

Two things make this harder than most industries. Many designs belong to customers, and some are export-controlled.

For the full process across every industry, start with our guide to how to sell your company’s data to AI companies.

Key takeaways

  • Mercor’s hardware listing pays $45,000 to $1.3 million and wants native CAD assemblies with feature trees, not exported meshes.
  • It rules out “designs owned by your customers” and “single parts or parts catalogs.”
  • Automotive, aerospace, robotics and industrial equipment are its priority industries.
  • Releasing controlled technology to a foreign person in the US counts as an export under both the EAR and ITAR.
  • Part numbers, customer names and title blocks identify a program even after people’s names are gone.

What hardware engineering data do AI companies buy?

AI companies buy whole products, not parts. Mercor wants full multi-part assemblies in native CAD with their feature history, plus the circuit designs, drawings and test results that go with them. A single part or a parts catalog is rejected.

Mercor’s hardware engineering listing, read November 9, 2026, splits it up like this:

Data Mercor’s view Main risk
CAD assemblies and drawings Core of the license Customer ownership and export controls
Circuit designs Core of the license Customer IP and licensed reference designs
Simulation and test files Core of the license Test data that names a customer program
PCB designs and Gerber files Adds to what you earn Same as circuit designs
Drawings and bills of materials Adds to what you earn Supplier and customer part numbers
Firmware Adds to what you earn Third-party code and its license terms
FEA and CFD simulation files Adds to what you earn Controlled performance data
Single parts or parts catalogs Not a fit Rejected outright

The feature tree is the point. A native model records how an engineer built the part, step by step, and that’s what a model learns from. An exported mesh only shows the result.

Mercor names the companies it wants:

  • Automotive suppliers
  • Aerospace companies
  • Robotics and industrial equipment makers
  • Product design consultancies
  • EV and drone makers

It works with SolidWorks PDM, PTC Creo, Siemens NX, Autodesk Fusion, Onshape, Altium, KiCad and ANSYS.

How much is hardware engineering data worth to AI companies?

Mercor’s hardware engineering listing pays $45,000 to $1.3 million, depending on assembly count and completeness. That top end is the second-highest of Mercor’s 25 listings, behind manufacturing at $1.5 million. The low floor means a small vault with gaps earns little.
Mercor listing Company earns Size bar
Manufacturing and industrial $100,000 to $1.5 million 20 to 2,000 employees
Hardware engineering $45,000 to $1.3 million 20 to 2,000 employees
Construction $115,000 to $1 million 50 to 2,000 employees
Semiconductor and materials $100,000 to $750,000 10 to 2,000 employees

Completeness drives the number. An assembly with its drawings, bill of materials and measured test results is worth more than the same model on its own.

Mercor also shows a referral fee of up to $110,000 for hardware companies. That’s paid to someone who refers a company, not to the company.

Our guide to how much company data is worth to AI compares published payouts across industries.

Do export controls apply to CAD files and circuit designs?

They can. Under the EAR, releasing controlled technology to a foreign person in the US is a deemed export. Under ITAR, releasing technical data to a foreign person is an export too. Aerospace, defense and some automotive and drone designs are the usual cases.

15 CFR 734.13 says any release in the United States of technology or source code to a foreign person is a deemed export. It counts as an export to the person’s most recent country of citizenship or permanent residence.

22 CFR 120.50 says the same for ITAR technical data. A release to a foreign person in the US counts as an export to every country where that person has held citizenship.

That matters because an AI buyer’s annotation team is usually global. If your files include controlled designs, the people reading them are the export question, wherever the server sits.

Before you scope a deal, ask three things:

  • Which of our designs carry an ECCN other than EAR99, or an ITAR category?
  • Who at the buyer will touch the files, and in which countries?
  • Will the buyer accept a clause excluding controlled technology from the license?

Our guide to selling manufacturing data to AI covers ITAR and defense contract flowdowns for shop-floor records.

Can you license designs you built for a customer?

Usually not without the customer’s written agreement. Most engineering services and build-to-print contracts give the customer the design, and Mercor lists customer-owned designs as not a fit. Your own products are what you can license.

Sort your vault into three piles before you talk to a buyer:

  • Your own products: designs you developed and sell under your name. These are yours to license.
  • Customer programs: work done to a customer’s spec or under a development contract. The contract decides who owns it.
  • Third-party content: supplier models, vendor reference designs and licensed libraries. Someone else set the terms.

Read the IP and confidentiality clauses in each customer contract. A design consultancy may find that most of its vault belongs to clients.

Third-party content is easy to miss. Supplier CAD models and vendor reference designs often come with download terms that limit redistribution.

What should you leave out of a hardware data deal?

Leave out customer-owned designs, export-controlled files you haven’t cleared, third-party models you don’t have the right to share, and anything covered by a patent application you haven’t filed yet. Licensing unfiled inventions can hurt your ability to protect them.
  • Customer-owned designs without written consent
  • Controlled technology until your export lead clears it
  • Supplier and vendor models whose terms bar redistribution
  • Inventions you plan to patent but haven’t filed
  • Current-generation products you want to keep as trade secrets

The trade secret point is commercial, not only legal. A licensed design teaches a model how you solve a problem, and that model may be sold to your competitors.

Start with older product generations. They still show how your engineers work, and you give away less.

How do you prepare CAD files and schematics for licensing?

Strip what identifies people and customers, and keep what explains the design. That means clearing title blocks, file properties, PDM check-in history and customer part numbers, while keeping feature trees, drawings, bills of materials and test results together.
Item What to do
Title blocks Remove customer names, program names, drawn-by and approved-by names
File properties and PDM history Clear author, last-saved-by and check-in comments
Customer and supplier part numbers Replace with consistent codes across every file
Bills of materials Keep the structure, code the supplier names and prices
Test reports Keep the measured results, remove the customer and program
Firmware Remove keys and credentials, and check third-party code licenses

Keep the codes consistent. A model learns more from one coded part used in 40 assemblies than from 40 unlinked names, and you give up nothing by keeping the link.

Mercor says it signs an NDA, runs the export and removes or protects personal information. An engineer on your side should still check a sample before delivery.

Our guide to anonymizing data for AI training covers metadata tools in more detail.

Who buys hardware engineering data?

Mercor is the only buyer publishing a payout range for hardware design files. micro1 buys software and engineering process data from companies with 30 or more staff, which can fit an engineering team’s tickets, specs and documentation.
  • Mercor: CAD assemblies, circuit designs, simulation and test files, for companies with 20 to 2,000 employees. Pays $45,000 to $1.3 million.
  • micro1: engineering workflows, bug tracking, product planning and technical documentation, listed on its data partnerships page. It wants 30 or more full-time staff and publishes tiers from $100,000 to over $3 million. You can apply to micro1 here.

Our list of companies that buy business data for AI has each buyer’s terms.

What are the steps for a hardware company, start to finish?

A hardware company licenses its data in eight steps: count complete assemblies, split your designs from customers’, screen for export controls, pull third-party content, apply to a buyer, clean metadata and part numbers, have counsel review the license, then check a sample.
  1. Count complete assemblies. Native CAD with feature trees, plus drawings and test results, across several product generations.
  2. Split yours from your customers’. Read the IP clause in each development and build-to-print contract.
  3. Screen for export controls. Have your export lead classify anything aerospace, defense or dual-use before it goes in scope.
  4. Pull third-party content. Supplier models, vendor reference designs and licensed libraries.
  5. Apply to a buyer. Mercor’s listing asks which CAD system you use, how many assemblies you have and who owns them.
  6. Clean metadata and part numbers. Title blocks, file properties and PDM history included.
  7. Have counsel review the license. Our AI data licensing agreement checklist lists the clauses to check, including exclusivity and deletion.
  8. Check a sample. Have an engineer try to name the customer or program from 20 cleaned assemblies.

Chip and materials companies face foundry NDAs and stricter export rules. Our guide to selling semiconductor data to AI covers them.

Common mistakes when selling hardware engineering data to AI

The most common mistake is treating customer programs as the company’s own designs. These are the others:

  • Sending exported meshes instead of native CAD with feature trees
  • Ignoring deemed exports because nothing leaves the country
  • Clearing names from drawings but leaving them in file properties
  • Leaving customer part numbers in bills of materials
  • Including supplier models whose terms bar redistribution
  • Licensing current products you’d rather keep as trade secrets
  • Reading Mercor’s referral fee of up to $110,000 as what the company gets paid

Frequently asked questions

Can a hardware engineering company sell its data to AI?

Yes, for designs it owns. Mercor’s listing rules out designs owned by your customers, so build-to-print work and customer IP usually need the customer’s written agreement first.

How much do AI companies pay for hardware engineering data?

Mercor’s hardware engineering listing pays $45,000 to $1.3 million, depending on assembly count and completeness. The referral fee of up to $110,000 goes to whoever refers the company.

What hardware data do AI companies want?

Full multi-part assemblies in native CAD with their feature trees, circuit designs, drawings and the test results that go with them. PCB files, bills of materials, firmware and simulation files add to the price.

Do export controls apply to selling CAD files to AI?

They can. Releasing controlled technology to a foreign person in the US is a deemed export under 15 CFR 734.13, and releasing ITAR technical data is an export under 22 CFR 120.50.

Can I sell designs I made for a customer?

Usually not without the customer’s agreement. Most engineering services contracts give the customer the design, and Mercor lists customer-owned designs as not a fit.

Which CAD systems does Mercor work with?

SolidWorks PDM, PTC Creo, Siemens NX, Autodesk Fusion, Onshape, Altium, KiCad and ANSYS, according to its listing.

Last updated: November 9, 2026

Disclosure: some links on this page are affiliate links. If you sign up through one, we earn a commission at no extra cost to you.

This isn’t legal advice. Have counsel review any data deal, and your export control lead review any design files, before you sign.

Don't Do It Yourself
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.