Your project record holds the decisions behind the drawings.

Behind every finished building is a record of questions, changes and judgment calls: the RFI that took three rounds, the change order that reset the schedule, the daily log that explains why. Plenty of software can read a drawing. Far less of it has seen how the decisions around one actually played out. We take an anonymized summary of your record to several buyers at once, and you choose the license.

Small commission on close. Nothing up front.

Get your data priced How it works

Usually held in

Procore
Buildertrend
JobNimbus
Roofr
AccuLynx
CompanyCam
Outlook (Microsoft 365)
QuickBooks

What buyers pay for in construction.

Buyers value records that show a decision and what came of it more than they value finished paperwork. These are the parts of your record they look for.

RFIs, submittals and specs

The questions asked, who answered, how many rounds it took, and the review trail on each submittal. This is the back-and-forth that document-control tools have to learn.

Change orders and cost history

Scope changes, pricing and approvals, plus estimate against actual cost, line by line where you track it.

Daily logs and schedules

What happened on site each day, what slipped and why, and how the schedule moved against its baseline.

Site photos and progress capture

Dated, located photos tied to the phase of work they document and to the issues that followed.

Punch lists and closeout

Deficiencies found, the trade responsible and how the list closed out. Patterns across many projects are what a buyer is after.

Coordination email and messages

Owner, subcontractor and supplier threads where decisions get made. Employee-only channels and personal messages can be scoped out first.

Systems that hold it and what to watch for.

This is where the record usually lives. Where we've written a data guide for a system, its card links to it, with steps to find out how much you have.

Who buys it and what they do with it.

We describe buyers by category and don't publish their names. Each one is qualified and under NDA before seeing your summary, and when they bid you see every offer side by side, with exclusivity, term and payment next to the price.

Construction document AI

Tools that read RFIs, submittals and specs and route them. They need realistic document trails, including the messy ones.

Estimating and takeoff AI

Teams building software that prices work from plans. Estimates set against actual cost are the check on their models.

Scheduling and progress-tracking AI

Companies that forecast delays and compare site capture with the plan. Daily logs, schedules and dated photos are their raw material.

AI labs building agents

Labs that want long, multi-party workflows to train and test agents on, with owners, subs and suppliers all in the thread.

Insurers

Carriers that price construction risk and want to see how projects really run: how often scope changes, where delays start and which defects repeat.

What a package looks like to a buyer.

Before anyone signs, a buyer sees a summary shaped like this one. It is built from rounded ranges: no name, no website, no people, no addresses.

The numbers in this example are made up. Yours come from your intake and the review call, and you read the summary before any buyer does.

See the full process

Example package · Construction

Illustrative

Sector: Commercial and multifamily general contractor
Region: Mountain West US
History: 8+ years, continuous
Record: ~130 projects, ~14K RFIs and submittals, ~2.5K change orders, ~150K site photos
Mix: ~65% new build, ~35% renovation
In scope: Project documents, logs, schedules, estimate-to-actual history
Left out: Drawings you do not own, NDA material, HR and medical records

Illustrative only. Real packages and prices depend on your records and rights.

What stays out by default.

Some records aren't yours to license, and some shouldn't leave the building. Intake and the review call bring these up early. The main ones for this industry are below.

Drawings and specs you don't own
Plans and specifications are usually the architect's or engineer's work product. We leave them out unless the design professional's agreement allows more. Your own markups, RFIs and logs stay in scope.
Owner and GC confidential material
Contracts, pricing and project information you hold under an NDA, a master agreement or on behalf of a client. If a counterparty has the right to keep it private, it stays out or is aggregated. We talk through your agreements on the review call. This is not legal advice.
Employee HR records
Payroll, performance, discipline and benefits material is excluded by default. We also suggest leaving employee-only channels and personal messages out of scope.
Safety incident medical details
Injury and medical details in incident reports, and any other health information, are excluded by default. If a buyer wants safety patterns, aggregate counts can be discussed instead.

This is not legal advice. Whether a record can be licensed depends on your contracts, your software terms and how it was collected, and your counsel should review any license before you sign.

Licenses in our network closed by buyers, not by us.

Recent licenses of operating records, closed by buyers in our network. A general contractor is among them.

Roofing

$450,000

Roofing company

Exclusive · perpetual · full operating record

Construction

$300,000

General contractor

Exclusive · 24-month term · full operating record

Solar

$275,000

Solar company

Exclusive · 18-month term · full operating record

Marketing

$110,000

Agency with global clients

Exclusive · 24-month term · full operating record

Licenses closed by buyers in our network, shown to describe the market. They are not deals thedata.broker brokered and not a forecast of what your record will bring. Every record is priced on its own.

Construction questions worth settling early.

More in Answers, or ask us on a call after your intake.

Often both sides have a claim, and the contract decides. Your own RFIs, logs, estimates, schedules and photos are the core. Owner-supplied documents and design professionals' drawings usually carry restrictions. Intake asks whether your contracts allow licensing and whether you hold data for clients, the review call goes through the details, and the license is scoped around what you can grant. This is not legal advice; have counsel review before you sign.

It can be, and trades are welcome. Buyers care about continuity of history and the volume of real project work more than company size or whether you are the prime. If your record isn't a fit, we tell you early.

Buyers see an anonymized summary before signing, with no name, website or customers. Identifiers are removed before delivery under the license, and the license can require project and counterparty names to come out as well. Whether a contract requires you to tell a counterparty is a question for your counsel. This is not legal advice.

We don't take custody of raw data. Under the license, the records in scope move from your systems to the buyer, with identifiers removed first. Delivery needs admin access to the systems in scope. Intake only asks for counts and dates, not files.

It can be valuable, but it is where employee-only chatter and personal messages hide. We suggest leaving those channels out, and we check your tool's terms for what an export may be used for. Which channels are in scope is your call.

We are paid a small commission out of a deal that closes. If nothing closes, you owe nothing. You keep ownership of your records and keep using them.

Not quite your business?

See every industry we take on, the business functions buyers ask for, and which records need special handling.

All industries