BLACKSIG SYSTEMS/Resources/Data licensing/Construction and Contracting

Data licensing

Can a Construction Company Sell Its Data to AI Companies?

Yes, and the project file is the thing a contractor most wants to sell and least owns. The drawings belong to the design team, the submittals belong to the subs, and what is left is the part a lab actually wants to buy.

Last updated · 2026-11-10

Disclosure: BLACKSIG may receive a referral fee from buyers named on this page when a company we introduce licenses its data. There is no fee to the company.

The short version

A construction company can license its data to AI companies, and the part worth the most is the part it owns outright, which is smaller than the project archive it has been keeping. Under AIA B101-2017 the architect and the architect's consultants are deemed the authors and owners of their Instruments of Service, and the Owner receives a license to use them solely and exclusively for constructing, using, maintaining, altering and adding to that Project. Drawings and specifications reach a contractor through that license, and nothing in it names licensing them to an AI lab. Sub bids, shop drawings and product data came from third parties for one project. What a contractor owns is its own work product: estimate build-ups, the RFIs it wrote, change order justifications, schedule logic, its own daily logs and its own means and methods. According to Polyshares' track record page, read on November 10, 2026, it has licensed a general contractor's records for $300,000 and a roofing company's for $450,000, both described as perpetual and exclusive.

Can a construction company sell its data to AI companies?

A construction company can license its own records to AI companies, and "its own" is the phrase that decides how much of the archive is in play. The company owns the record of how its people estimated, sequenced, questioned and built the work. It does not own most of the documents that arrived from everybody else on the project.

The market is real and funded. The Next Web reported on October 9, 2026 that micro1 alone will spend "$1bn over the next 12 months" on "buying and licensing operational data from companies", with Citi and Hercules Capital providing the capital. Construction sits well inside what buyers say they want, because the reasoning behind a build is detailed, sequential and almost entirely absent from the public internet.

The deals that have been published for this sector are specific. Polyshares lists four selected licenses on its track record page, read on November 10, 2026: $450,000 for a roofing company, $300,000 for a general contractor, $275,000 for a solar company and $110,000 for a global marketing agency. Each is described as a "Perpetual exclusive license to the operational record. Anonymized before delivery", with an offer "within one to two weeks" and payment "net 30 to 60".

What those numbers do not tell you is which documents were in the dataset. That is the question this page answers, because a contractor who offers a buyer the whole project archive is offering material that is not his to grant, and a contractor who offers only his own work product is offering the part the buyer actually wants. Both conversations start the same way and end very differently.

Which parts of a construction project file does a contractor actually own?

A contractor owns what its own people produced and holds most of the rest under a licence or a confidence. That is the whole analysis, and running it on your archive takes an afternoon.

Design documents belong to the design team. AIA's own guidance on the rights of an architect's Instruments of Service, read on November 10, 2026, states that under B101-2017 "the Architect and the Architect's consultants are deemed the authors and owners of their respective Instruments of Service", and that "The Owner receives a license to use the Instruments of Service solely and exclusively for constructing, using, maintaining, altering and adding to the Project." That guidance speaks to the Owner and does not mention contractors at all. A contractor builds under that license, and licensing the drawings onward for model training is not among the purposes it names. That is a reading of the named purposes rather than a statement AIA makes about contractors, which is why it is worth an hour of your own lawyer's time on your actual contract.

Material that came from subcontractors and suppliers arrived for the project. Sub bids carry pricing the sub considers confidential, shop drawings are the sub's or the fabricator's work, and product data belongs to the manufacturer. Owner-furnished information, including the program, site data and anything commercially sensitive, is usually governed by the prime contract.

What is left is substantial and it is yours.

DocumentWho owns itLicensable by the contractor
Drawings and specificationsArchitect and consultants under AIA B101-2017No
Shop drawings and product dataSubcontractor, fabricator or manufacturerNo
Sub bids and sub pricingThe subcontractorNo
Owner-furnished project informationThe owner, per the prime contractUsually no
Your estimate and its build-upYouYes
RFIs you wrote and the reasoning in themYouYes, with project identifiers removed
Change order justifications and cost backup you preparedYouYes, with project identifiers removed
Your schedule, logic and updatesYouYes
Your daily logs, means and methods, safety and QC recordsYouYes
Your own SOPs, checklists and training materialYouYes

Read the right hand column as a scope rather than a loss. The yes rows are where the judgment lives, and judgment is what a lab is buying.

What construction records do AI companies want to buy?

AI companies want the records where a decision was made and the outcome is attached, which in construction means the estimate, the RFI, the change order and the schedule rather than the drawing set. Labs are training agents to perform business tasks, and a drawing shows a result while an RFI shows somebody working out what to do.

Handshake's data partnerships page, read on November 10, 2026, says "Your documentation, workflows, and project history capture how your business operates". Scale AI says on its data partnership page, read the same day, that it takes "never the raw systems themselves, only structured, de-identified records", drawn from warehouses, chat, email, documents, work tools and business platforms. micro1 lists SOPs, process documentation, internal knowledge bases, workflows, templates, CRM records and support tickets on its data partnerships page, names operations and logistics among its industries, and adds a category it calls agent trajectories, the record of how a task was actually carried out, which it says it licenses "for $1-2M annually, with your approval".

For a contractor, four archives map onto that directly:

  • Estimating, where a takeoff, a set of assumptions and a bid number form a complete chain of reasoning.
  • Project correspondence, where RFIs and their answers show a problem being resolved.
  • Cost control, where a change order carries a justification and a priced outcome.
  • Scheduling, where a sequence was built, broken and rebuilt against real constraints.

Depth beats breadth here. micro1 says on the same page that "Companies with several years of records across multiple business systems are generally a stronger fit." Ten years of estimating in one system, tied to the jobs those estimates became, is worth more than a scattered archive covering everything once.

Does a construction company qualify to license its data?

Most established construction companies qualify to license their data on the published size screens, and the screen that decides an offer is how much of the work is in software. Here is what each buyer publishes, read on its own pages on November 10, 2026. Where a buyer publishes nothing on a point, the table says so rather than guessing.

BuyerPublished size screenWhat it says sets the paymentPublished payout range
micro130 or more full-time employees; several years of records across multiple systems preferred; records primarily in English; US first"the quality, uniqueness, and value of the data provided"$100K to $500K for qualified partnerships, $500K to $3M for large-scale or multi-team data, $3M+ for highly unique data
MercorNot published"Compensation is based on data volume, the tools you connect, and the depth of your data"Not published
Scale AI"40+ employees is our preferred starting point", assessed case by caseBeyond size: established data systems, real operational workflows, domain depth, stakeholder alignment"$10K to $1M+", labelled illustrative and scaling with cadence
HandshakeNot published; its estimator asks employees, tools used, years in business and countryNot published"Earn $100K to $4M+" as a headline
PolysharesNot publishedNot publishedFour selected licenses, including $300,000 with a general contractor and $450,000 with a roofing company

Two practical notes on that table. The payout ranges are ceilings attached to words like unique and large-scale, so treat the top of any range as a description of somebody else's dataset until a buyer has seen yours. And a contractor that has run projects through a single platform for a decade is in a stronger position than one with twice the revenue and three years of records, which is the opposite of how most firms assess themselves. Every buyer here is read side by side in which AI company pays the most for business data.

Can you export project data out of your construction software?

You can export your own project data from your own account, and you may not be able to get it out through a third-party integration, which is a distinction that has already caught firms out. The route matters as much as the right.

Procore updated its API terms and introduced a new Developer Policy on September 30, reported by Engineering News-Record on October 31, 2025 in Jeff Yoders's account of Trunk Tools losing API access. Under the updated terms, marketplace partners cannot bulk download data from the platform for commercial purposes, including "the training of large language models". Procore told ENR that the changes "are being implemented to protect the integrity and security of all our customers' data" and that its commitment to "customer data remaining customers'" is unchanged.

That says two things at once: the data is yours, and the pipe a broker might want to use to pull it is closed. So the export has to be the native one you perform as the account owner rather than an integration somebody else runs on your behalf, and any buyer whose process depends on connecting an app to your project management platform needs to show you where that is permitted.

Check three things in your own software agreements before you scope anything: whether you can export in bulk and in what formats, whether the platform asserts any right to use your data for its own model training, and whether your subscription has to stay live for you to get at the archive. A cancelled account with a short export window is a different asset from a live one.

None of this stops a license. It decides the sequence: get the export in hand, under your own account, before you agree to deliver anything.

What must a construction company leave out of a data license?

A construction company has to leave out everything that came from somebody else for one project, and the list is longer than a privacy checklist. Start with ownership rather than with personal data, because that is where this industry's real exposure sits.

These stay out of any scope you describe to a buyer:

  • Drawings, specifications and any other Instrument of Service from the design team, for the reasons above.
  • Shop drawings, product data and submittal content prepared by subs, fabricators and manufacturers.
  • Sub bids and sub pricing, which are the subcontractor's commercially sensitive information and are often covered by the bid instructions themselves.
  • Owner-furnished information and anything the prime contract marks confidential. Public agency work frequently adds its own clauses, and some federal and defense projects add security restrictions that put the whole file out of reach.

Also out, on the standard grounds that apply across this lane: client material under NDA, HR and payroll records, health information including anything that reached you through a workers compensation file, and call or video recordings made without all-party consent. Site photography deserves its own look, because it can carry faces, plates, neighboring property and in some sectors security-relevant detail.

What survives is your own work product with project identifiers removed, which is the dataset to describe to a buyer. De-identification here means more than stripping names: a project at a named address with a distinctive scope is identifiable from the scope alone, so the scoping conversation should cover how far that goes.

One rule covers the awkward cases. If a document would have reached you anyway without the project, it is probably yours. If it exists because a particular owner hired a particular architect, it is not.

What is a construction company's data worth, and on what terms?

A general contractor's published comparison is $300,000 and a roofing company's is $450,000, both from Polyshares, both described as perpetual exclusive licenses to the operational record, read on November 10, 2026. Those are the only construction figures in this market with a named source behind them, and the terms attached to them matter as much as the numbers.

Perpetual is the word to slow down on. An exclusive license for a defined term costs you other deals for that term. A perpetual grant costs you all of them, and in this market the two usually arrive together. Once records have trained a model they cannot practically be removed from it, so the training that happens under the first license is permanent whatever the contract says afterwards.

That is not an argument against signing. It is an argument for pricing the term separately from the data. Exclusivity can be limited by time, by field of use or by scope, and each of those is a smaller concession than a perpetual exclusive grant over your whole archive. Our page on exclusive versus non-exclusive licenses sets out how to separate them, and can I sell my company's data to AI companies covers the market as a whole.

What raises the number for a contractor is specialization and continuity. A firm with fifteen years in one building type, with the estimates tied to the jobs and the change history intact, holds something few others can supply. A generalist with three years of records in four systems holds what many others can. Ask for the comparison on your own scope rather than against a headline, because the headline belongs to somebody else's dataset.

Frequently asked questions

How much does a construction company get paid for licensing its data?

According to Polyshares' track record page, read on November 10, 2026, it has licensed a general contractor's records for $300,000 and a roofing company's for $450,000, each described as a perpetual exclusive license to the operational record. Per micro1, the tiers are $100K to $500K for qualified partnerships, $500K to $3M for large-scale or multi-team data and $3M+ for highly unique data, and Scale AI shows $10K to $1M+ as illustrative. Those are ceilings rather than quotes, and figures circulating on broker sites that attribute per-industry ranges to buyers who do not publish them should be treated as unverified.

How does a construction data license actually work?

You describe which systems you hold and how far back they run, the buyer scopes a dataset, an offer follows, records are de-identified and payment follows delivery. Polyshares publishes an offer within one to two weeks and payment net 30 to 60. The step specific to construction comes first: separating your own work product from the design documents, sub submittals and owner information in the same folders, because only the first category is yours to license.

Can a contractor license drawings, specifications or BIM models?

Generally no. AIA's guidance on B101-2017 states that the Architect and the Architect's consultants are deemed the authors and owners of their respective Instruments of Service, and that the Owner receives a license to use them solely and exclusively for constructing, using, maintaining, altering and adding to the Project. That guidance addresses the Owner rather than the contractor, and a contractor's access runs through it, so training an AI model is not among the purposes named. Your own coordination work on a model may be a different matter and is worth asking counsel about on a specific contract, since project agreements vary.

Is a specialty contractor's data worth less than a general contractor's?

Not necessarily, and sometimes the reverse. Polyshares publishes a higher figure for a roofing company than for a general contractor. What buyers pay for is depth and uniqueness in one domain, and a specialty trade with a long unbroken record in one building type is exactly that. A general contractor's advantage is breadth of workflow; a specialist's is that nobody else holds the same thing.

Should I get help with this?

You can do this yourself with counsel, and the ownership questions on this page are worth a lawyer's hour on your actual contracts. The commercial decision, which is what the archive is worth and what terms to accept, is a different question. This page is published by BLACKSIG, which reviews these offers with owners and takes companies to the buyer whose terms fit, so read it the way you would read any interested party's account of the work it is paid for. We are independent of every buyer named here and we are not a partner, agent or representative of any of them. The buyer pays us a referral fee when a license closes and there is no fee to the company. We are not lawyers and this is not legal advice.

Related resources

Find out which part of your project archive is licensable

We separate what your firm owns from what arrived for the project, then take you to the buyer that fits. The buyer pays our fee, so it costs your company nothing.