Last checked: 7 October 2026. For companies, not individuals.
Contractors write down a great deal of skilled judgment: how a job was priced, why a spec was questioned, what went wrong on site and how it got fixed. Some AI data buyers publish that they take the systems those records live in. The hard parts are who owns the drawings and how your field crews are counted.
A finished building hides the reasoning behind it. Your bid files, RFIs and daily reports do not.
Grepped writes on its site that AI systems need “real examples of how people take a task from start to finish.” Trades firms keep exactly that, often for years, in estimating spreadsheets, scheduling boards, email threads with general contractors and service platforms.
The buyers’ own pages point the same way. Mode lists AutoCAD and ServiceTitan among the sources it buys, next to QuickBooks, Google Drive and Microsoft tools. Grepped lists “Engineers & builders” with “Bids, specs, site reports” among the experts it is looking for; that list belongs to its program for individual professionals, and Grepped says it welcomes every vertical. micro1 says “Operational data from every industry can contribute” and names SOPs, project histories and QA processes among the material it wants (all as published, checked 7 October 2026).
Why does a construction record carry weight? Because it ties a decision to a result. An estimator chose a crew size and a markup. A superintendent resequenced work after a late delivery. A technician diagnosed a failed compressor and wrote what fixed it. Practitioners say raw records are the cheapest tier and that evaluations built from them are worth roughly ten times more. Linked job histories are the raw material evaluations get built from.
Takeoffs, unit pricing logic, assumptions, exclusions and the notes on why a bid was won or lost.
Questions raised against a spec, the answers that came back and how the work changed as a result.
Daily logs, punch lists, delay notes and change orders that show plan versus reality.
Call intake, dispatch choices, diagnosis notes and fixes, as kept in a field service platform.
Start from ownership. If your firm did not create a record, or a contract limits its use, it does not belong in a first scope.
Most contractors hold the same dozen kinds of records. Sorting them by who created them and whose details they contain does most of the scoping work.
| Record type | Where it usually lives | Usually includable? | Why |
|---|---|---|---|
| Estimates and takeoffs | Spreadsheets, Google Drive | Often, de-identified | Your own work product. Strip customer, owner and project names. |
| Bid packages received | Email, shared drives | Rarely | Created by GCs or owners and often sent under confidentiality terms. |
| Architect and engineer drawings and specs | AutoCAD files, PDFs | Rarely | Rights usually sit with the design team or the owner. |
| Shop drawings and details you made | AutoCAD | Often, if rights are clear | Your firm’s own drafting, but check what the contract says about deliverables. |
| RFIs and submittal logs | Email, Drive, project tools | Sometimes | Your questions are yours; the answers came from others under contract. |
| Daily reports and punch lists | Drive, field apps | Often, after review | Worker names and site addresses need to come out. |
| Service calls and dispatch | ServiceTitan | Often, de-identified | Strong diagnosis-and-fix records, full of customer details to remove. |
| Job costing and invoices | QuickBooks | Partly | The costing process is useful; customer payment data is not. |
| Payroll and timecards | Paychex or similar | Rarely | Employee personal data, including certified payroll on public jobs. |
| Injury and incident reports | Drive, insurer portals | No, if named | Medical and personal details about identifiable workers. |
| Site photos and video | Phones, Drive | Separate decision | Show people, homes, vehicles and private interiors. |
General guide for scoping, not a legal classification. Your contracts can move any row into or out of scope.
Many trades firms have 20 to 200 people, but most of them work in trucks and on sites. That matters because some published rules count office staff.
Mode publishes 20+ full-time U.S. office employees for most businesses. micro1 publishes 30+ employees, along with mature operations, documented processes and modern software tools.
Estimators, project managers, dispatchers, service coordinators and accounting staff are the people most firms would count here.
Mode’s published calculator asks for desk and non-desk employees as two separate numbers. Neither program’s page that we checked says exactly how field technicians affect eligibility.
So ask. Put your office and field counts in writing and let the buyer answer before you plan around a minimum.
| Program | Published company payout | Published eligibility | Note for trades firms |
|---|---|---|---|
| micro1 Enterprise Data Partnership | “$100k+ qualified”, “$500k+ large-scale”, “$1M+ highly unique” | 30+ employees, mature operations, documented processes, modern software tools, primarily English; U.S. prioritized, then other Western markets | Lists SOPs, project histories and QA processes among what it wants. |
| Mode company data | “$100K to $5M” | 20+ full-time U.S. office employees; several years of records the company owns; U.S.-based teams strongest fit | Lists AutoCAD and ServiceTitan among sources it buys. |
| Grepped | “$20K to $5M” | Any vertical; also pays individual professionals for expertise | Lists “Engineers & builders” (“Bids, specs, site reports”) among experts it seeks. |
Last checked 7 October 2026. Sources: each program’s own website (micro1 data partnerships page, data.mode.inc, grepped.ai). Figures are published ranges, not offers. Miro Advisory also publishes indicative ranges for operating datasets ($100K to $1M+); it is not covered by the buttons below.
Independent site. Some links are referral links: if your company signs with a buyer through them, the buyer may pay us a fee. You are not charged, and we never see your data.
Enter both numbers in the eligibility checker, which shows each published rule next to what you entered. The buyer programs comparison lays out the full published terms, including what each program says about privacy and process.
The legal questions for a contractor start with paperwork you signed with others. Personal data comes second, but it is still there in every service call.
General information, not legal advice. Talk to your own lawyer before you sign.
A scope is a plain list of systems, years and exclusions. Writing it first keeps you in control of what a buyer reviews. There is no price here, because a buyer sets any price only after review.
The same published rules land very differently on a small remodeler and a large commercial builder. None of these firms is real, and none of these scopes carries a price.
8 in the office (owner, two estimators, a project coordinator, accounting) and 14 on crews. Kitchens, baths and additions.
24 in the office (estimators, project managers, dispatch, accounting) and 46 electricians. Commercial tenant work plus a service division.
75 in the office and 115 in the field. A commercial general contractor with private and public-sector work.
A contractor’s files mention far more people than its own staff. Think about each group before export, not after.
These apply to any buyer and any agreement. They describe what to look for, not what any named program does.
If two or more items on the left are a “no”, fix those first. The questions on the right are worth asking any buyer early, in writing.
Ask the buyer. Mode publishes a minimum of 20+ full-time U.S. office employees, and its online calculator asks for desk and non-desk employees as separate numbers. micro1 publishes 30+ employees without saying how field crews are counted (both as published, checked 7 October 2026). Get the answer in writing before you plan around it.
Only drawings you own and are free to share. Mode lists AutoCAD among the sources it buys, but many drawings in a contractor's files belong to an owner, architect or engineer, or are covered by contract terms. Keep those out unless your lawyer confirms you hold the rights.
They show decisions with outcomes attached. A bid explains how scope was priced, an RFI shows a problem being resolved, a change order shows what happened when the plan met the site, and a service ticket shows a diagnosis and a fix. Linked together for the same job, they form a work history rather than a pile of files.
Often, yes. Photos can show workers, homeowners, house numbers, license plates and the inside of private homes. Treat photos and video as a separate decision with its own review. Many firms leave them out of a first scope entirely.
Expect months. Mode publishes that it generally expects about three months from the first conversation through payment, and practitioners cite 60 to 90 days to close. Neither is a promise, and sorting out drawing rights can add time.
Possibly not through the company programs. Mode publishes 20+ full-time U.S. office employees for most businesses (with lower lines only for accounting and law firms), and micro1 publishes 30+ employees. Grepped publishes that it welcomes any vertical and also pays individual professionals for expertise, listing engineers and builders among them (as published, checked 7 October 2026). A small firm may simply not fit, and that is a fine answer.
Scope is set in writing, so a single division can be the whole scope. Mode publishes that the agreed scope lists the approved systems and date ranges before any export, and micro1 says scope is agreed in writing. Check that any exclusivity clause covers only the slice you agreed, not all company data.
That depends on what your service agreements and privacy notices said, where your customers live and which laws apply. Many firms start by reading those documents and asking a lawyer whether a de-identified copy changes the answer. This is general information, not legal advice.
The checker runs in your browser and saves nothing. Enter your headcount, years of records and systems, and see which published rules you meet.