A commercial project's material spend is decided during estimating, when the general contractor is assembling a bid. Suppliers who first hear about a project after buyout are not competing for the order — they are asking to be considered next time. Closing that gap is a coverage problem, and coverage is a data problem before it is a headcount problem.
The commitment happens before the project is visible
Ask a regional sales manager at a building products company where the next new account comes from, and the honest answer is usually: a relationship that already existed. A referral. A contact who moved to a different general contractor. A trade show conversation from two years ago that finally landed.
That is a real pipeline. It is also a pipeline with a ceiling, and the ceiling is geographic. It grows where the reps already know people, and it does not grow anywhere else. For a supplier operating in one metro, that is manageable. For one selling across a dozen states, most of the territory is being covered by whoever got there first.
The uncomfortable part is that "first" is earlier than most supplier sales organizations are built to reach.
A commercial project's material spend is effectively decided during estimating. The general contractor is assembling a bid, and to assemble a bid they need pricing. They call the suppliers they called last time. Those quotes become the basis of the number they submit. If they win the job, buyout converts those quotes into purchase orders with very little re-shopping — because re-shopping means reopening a margin assumption they have already committed to in writing.
How much runway that gives a supplier depends on the delivery method, and it is worth being exact about it rather than describing one sequence as though it were the only one. On design-build, negotiated and construction-manager-at-risk work, early records are typically filed while the material package is still being priced — the record and the estimating window are open at the same time, which is the case this article is about. On hard-bid design-bid-build, the record is filed by the winning contractor after award, and it reaches you once quotes are already locked. Both are worth having. They are worth having for different reasons: the first is this project, the second is the next one from that contractor and that owner, with six months of warning instead of none.
The window also has a rough shape you can plan against. Published industry guidance puts a typical commercial bidding and pricing period at three to four weeks, evaluation and award at one to two weeks after that, and buyout — where quotes become signed purchase orders — at two to six weeks following award, longer on complex projects with many trade packages. Long-lead items are ordered in the first week of buyout, which is why they close first. On a project where the record is filed early, that adds up to something in the order of six to twelve weeks between the record appearing and the package being locked. Next day is what turns that window from theoretical into usable.
By the time the project is visible from the road, the framing package, the concrete, the roofing membrane and the mechanical equipment are largely spoken for. A rep who calls at that point is not competing for the order. Buyout is finished. They are asking to be considered next time.
None of this is a secret. Every supplier sales leader already knows it, which is worth conceding plainly, because the insight was never the hard part. The hard part was that information about which projects were entering estimating — in which markets, at what size, filed by whom — sat scattered across hundreds of separate local authorities, each publishing in its own format, on its own schedule, with its own definition of what counts as a record. Assembling that picture nationally was possible in theory and impractical in practice, which is the problem the underlying data set exists to solve and why coverage across jurisdictions matters more than depth in any one of them. It is also why suppliers, general contractors and developers tend to arrive at the same conclusion from different directions.
A rep who calls after buyout is not competing for the order. They are asking to be considered next time.
What arriving late actually costs
Most suppliers cannot say what late contact costs them, because the loss is invisible. It does not appear as a lost bid. It appears as a project that was never bid at all, which shows up in no report anywhere. Suppliers are not alone in this — general contractors, subcontractors and developers each run a version of the same calculation from their own side of the job.
Here is a way to size it. It is deliberately built to be filled in with your own numbers rather than ours, because the only figure that matters here is yours. If you would rather test it against real records than estimate, a sample of building activity in your markets gives you line A directly.
| Input | How to get it | Your number | |
|---|---|---|---|
| A | Commercial projects per year in your served markets, in your material category | Your territory definition | |
| B | Share of those your reps actually quoted last year | CRM opportunities ÷ A | |
| C | Your close rate on projects you did quote | CRM | |
| D | Average material value per project won | Finance | |
| E | Revenue you captured | A × B × C × D | |
| F | Revenue available at full quote coverage | A × C × D | |
| G | The coverage gap | F − E |
Line G is not lost revenue in the sense that you would have captured all of it. It is the size of the pool your reps never got a shot at. Enter B as a decimal — 30% coverage is 0.30, not 30.
For most suppliers running the numbers honestly, line G comes out larger than the entire annual growth target, which is why the supplier view of this data gets built around territory coverage rather than one-off project lookups. Two things fall out of that.
First, improving line B, quote coverage, is almost always cheaper than improving line C, close rate. Getting reps in front of more of the projects that exist is a coverage problem. Raising close rate against the same set of projects is a selling problem, and selling problems are slow and expensive to fix — you are retraining people and rebuilding relationships. Second, quote coverage is the only input on that list that data moves directly. Nothing you buy will make a rep more persuasive. Something you buy can put that rep in front of three times as many estimating conversations.
Which turns the whole question into an arithmetic one. If line G, the coverage gap, is worth several million and closing even a fifth of it costs a fraction of one additional territory manager, the decision stops being a marketing judgement and becomes a budget comparison. That is the calculation worth putting in front of whoever signs off on headcount.
Construction project data closes coverage without closing headcount
The instinct when line B is low is to hire. More reps, more markets, more calls. That works, and it is the most expensive version of the fix.
A rep who does not know which projects are entering estimating in their territory spends a substantial share of the week finding out — calling general contractors to ask what they are bidding, checking bid boards, working relationships for intelligence. That is research time billed at sales compensation, and it does not scale: doubling the territory doubles the research, not the selling.
The alternative is to hand every rep a filtered view of building activity in their territory, already assembled. Alliance Data Solutions assembles new records daily across 39+ states and 300+ jurisdictions. A record filed at its source is generally available in a delivered file the next day, and within a few days in jurisdictions that publish more slowly. The research step is done before the rep opens the file, against the same record specification every time, so the week goes back to selling, and coverage rises without headcount rising.
That is the argument for buying construction project data rather than assembling it, and it is worth being plain about what it does not do. It does not make reps better at selling. It makes sure they are selling to the right accounts at the right moment — a different problem, and a considerably more tractable one. If your close rate is the constraint, this will not fix it. If your coverage is the constraint, nothing else will.
Want to see what coverage looks like in your markets? We can put together a sample drawn from the jurisdictions you actually sell into, filtered to your material category.
Request a sample or call 888-888-1214What to demand from a construction data provider
If you are evaluating a construction data feed — from us or from anyone — these are the questions that actually separate providers. It would be poor form to publish a list like this without answering it, so each one is answered for Alliance Data Solutions in the same terms.
Which markets, and how do you define a market? "Nationwide" is not an answer — ask for the list, and ask whether a state counts because one county in it is covered. Alliance Data Solutions: 39+ states and 300+ individual jurisdictions, defined at the level of the issuing authority rather than the state. The current list is available on request and in the coverage detail.
How long between a record appearing at source and appearing in the feed? This is the whole argument. A feed lagging six weeks delivers projects after the estimating window has closed, which is the problem you were trying to solve. Alliance Data Solutions: generally next day, and within a few days for jurisdictions that publish on slower cycles. The constraint is the authority's own publishing schedule, not our collection.
What is actually on each record? Project type, valuation, location and status are table stakes. Contact information is where providers diverge sharply, and where you should ask hardest. Alliance Data Solutions: up to 20 data points per record — record number, filing date, property type, record type and sub-type, project description, job address, job cost, status, owner name, applicant name, county or city, and state. Contact details for the contractor and the applicant are included where the issuing jurisdiction publishes them, which varies by jurisdiction. Any provider claiming universal buyer contact coverage is describing something other than public records.
What happens to a record between collection and delivery? Automated collection at national scale is the only way to get coverage. Automated collection with nothing after it is how you get a file full of duplicates. Alliance Data Solutions: records are deduplicated, then graded and scored on how many of the 20 data points are populated, then filtered to the fields and thresholds you have specified. Worth naming the limit of that: completeness scoring measures how much of a record is present, which is not the same as verifying that each field is correct. Further detail on how records are handled sits with the wider questions.
How does it reach our systems? A supplier with a national sales organization is not going to have reps downloading spreadsheets one at a time. Ask what is live today versus what is on a roadmap, and insist on the distinction. Alliance Data Solutions: CSV and Excel files, or SFTP, filtered to your specification. API access is on the 2026 roadmap and is not live today. The quickest way to judge the format is to look at an actual file.
How is it priced, and what does the agreement actually commit you to? Volume, frequency and territory should all be things you set rather than things you accept. Alliance Data Solutions: nationwide programs and data licensing are handled as custom-quoted agreements, with delivery frequency, filtering and volume set in the agreement rather than fixed to a tier. Published plans exist for smaller single-market use; supplier programs at national scale sit outside them.
Why Alliance Data Solutions for a supplier program
Everything above is true whichever provider a supplier picks. Here is the specific case for this one, in the same six terms.
It is built to the shape of a territory, not a lookup. Most sources of building activity answer one question at a time — a single address, a single county portal. A supplier program needs every qualifying record across 39+ states and 300+ jurisdictions, cut to the markets each rep actually owns. That shape is the product, not a feature of it — the jurisdictions currently covered are listed rather than summarized.
It arrives inside the estimating window. New records assembled daily, generally available in a delivered file the next day. The entire argument of this article is that timing decides the order, so a provider that cannot speak precisely about lag is not a provider you can act on.
Filtering happens before delivery, not after. Records are deduplicated, scored on how many of the 20 data points are populated, then filtered to the fields and thresholds you set. That distinction matters more than it sounds: the alternative is a rep opening a file of 4,000 rows and spending Monday deciding which 200 are worth a call. You are buying the triage as much as the data.
It arrives how your team already works. CSV, Excel or SFTP, cut to your specification, dropped on the cadence written into your agreement rather than a cadence chosen for you. API access is on the 2026 roadmap and we would rather say so than imply otherwise.
The terms match a program. Nationwide coverage, data licensing and partner arrangements are custom-quoted, with volume, filtering, territory and frequency set in the agreement. A national supplier should not be fitting a sales organization into a published plan built for one metro.
And the honest limit, stated plainly: this is public building activity, assembled, scored and filtered at national scale. It is not a proprietary intelligence network and we do not claim one. If your constraint is that your reps are excellent but only ever see a third of the projects in their territory, this closes that gap. If your constraint is something else, it will not — and we would rather tell you that early than sell you a file you cannot use.
Where this leaves you
If your reps are consistently reaching projects after estimating, more calls will not fix it. Earlier information will — delivered into the systems your team already works in, covering the markets you actually sell into rather than the ones where you happen to know somebody.
Run line G on your own numbers before you talk to anyone, including us. The questions we get asked most are collected separately if you want the short version first. If the gap is small, your coverage is good and this is not your constraint; spend the money on something else. If it is large — and across multiple markets it usually is — the question worth putting to your team is how much of that gap is a data problem currently being solved with headcount.
The follow-up question is the one in section four: what would you need a provider to prove before you moved budget? Write that list down first. Then make every provider you talk to answer it, in writing, in those terms. The record specification we work from is published rather than described on a call. Ours are answered on the supplier page and in more depth on request. We have tried to answer it here so that you can hold this page up against the next vendor conversation you have — including the next one you have with us. When you are ready, start that conversation here — or call 888-888-1214.
Common questions
How current is construction project data?
Alliance Data Solutions assembles new records daily across the jurisdictions it covers. A record filed at its source is generally available in a delivered file the next day, and in some jurisdictions within a few days, depending on how quickly that authority publishes.
What information is on each construction record?
Each record carries up to 20 data points, including record number, filing date, property type, record type and sub-type, project description, job address, job cost or value, status, owner name, applicant name, county or city, and state. Contact details for the contractor and the applicant are included where the issuing jurisdiction publishes them, which varies by jurisdiction.
How is construction project data delivered to a supplier?
Data is delivered as CSV or Excel files, or over SFTP, filtered to the specification agreed with the customer. API access is on the 2026 roadmap. Delivery frequency is set in the customer agreement rather than fixed. Request a sample file to see the layout.
What does the review step check before data is released?
Records are deduplicated, then graded and scored on how many of the 20 data points are populated, then filtered to the fields and thresholds the customer has specified. Completeness scoring measures how much of a record is present, which is a different measure from whether each individual field is correct.