Direct answer
How do lumberyards find new construction projects?
Lumberyard lead generation means running several channels at once — permit portals, builder and GC relationships, plan rooms, referrals, and local business records — rather than depending on one. Assign each channel a boundary, an owner, and a review rhythm, then hand what it finds to the management workflow: verify, prioritize, assign, and follow up.
Free during the beta. No card required. We confirm your territory and get your reps into the queue. Tell us where your team sells. We'll confirm source coverage for that territory and get your reps into the queue.
The bigger picture
Three fronts, not one list of channels
Most LBM sales training splits prospecting into three jobs: sell more to the accounts you already have, sell into the categories they don't buy from you yet, and land brand-new customers. This guide is about the third job — the channels that get a project on your radar before another dealer's rep sees it. (NRLA's own sales training devotes a full session to the same three-part framework 7,8.)
Grow wallet share
Sell more of the categories an existing account already buys — just not all from you yet.
Penetrate underdeveloped accounts
Find the specific product categories a current account does not buy from you at all.
Acquire new customers
Warm and cold outreach, referrals, and — the focus of this guide — the channels that put a brand-new project on your radar before another dealer’s rep sees it.
Seen in the field
How three lumberyards actually run it
These are real dealers, not a formula — the specific numbers below are vendor-reported, but the systems behind them are worth stealing.
New-customer acquisition
PARR Lumber
A SalesJack case study puts PARR’s payoff at $500,000 in new revenue over six months (vendor-reported, not independently audited). The rule worth copying isn’t the number: every permit hit gets tied to an account and a rep automatically, routed by territory when there’s no existing relationship, with follow-up triggered the same day. 13
New-customer acquisition
Evanston Lumber
Evanston runs the digital side of the same idea: every website quote request flows into a shared pipeline, matched against ERP customer history, with a targeted follow-up sequence instead of sitting in an inbox. The same system flags inactive accounts and category gaps, so a web lead and a wallet-share opportunity get worked by the same process. 14
Wallet share & underpenetrated accounts
Hamilton Building Supply
Hamilton built its growth motion around the accounts it already has: customer and ERP data drives a share-of-wallet target for each one, backed by email, newsletter, and social outreach to re-engage accounts that have gone quiet. It’s the clearest example here of the first two prospecting fronts working as a system, not one rep’s personal habit. 15
Each of these three built this discipline on a different vendor's software. The tool matters less than the habit: a signal gets tied to an owner the moment it shows up. That same first-pass layer — supported local activity monitored and ranked into one queue — is what Radar handles for a lumberyard today.
Coverage, not a single source
A lumberyard territory rarely runs on one channel. A permit-portal feed catches what reaches a public record; a builder relationship can surface the same project earlier; a plan room covers larger work a portal search misses. The question for a sales leader is not which single channel is best, but which combination the team can realistically sustain.
Channel choice is also a boundary-setting exercise. A jurisdiction outside the delivery radius, a plan-room category the yard does not stock for, or a relationship with an account the yard cannot serve profitably is not extra coverage — it is a channel producing signals nobody should act on. Scope each channel to the territory and categories the team actually sells before adding it to the list.
What this means for your team
No single channel covers a territory by itself
Permit portals, relationships, plan rooms, and referrals surface different projects at different points in the lifecycle — a portal-only approach misses relationship and referral signals that can surface a project before any public record exists, and a relationship-only approach misses projects outside existing accounts.
Assign at least one owner and one review rhythm to each channel your territory can realistically sustain, rather than running one channel well and the rest not at all.
Outside reps already juggle several operating records
Outside sales work depends on current order, receivables, stock, and job-pricing information from more than one system 3. Adding an unmanaged lead-generation channel on top, with no owner or review rhythm, compounds that load instead of easing it.
Keep the channel list short enough for the team to actually maintain, and retire a channel that stops producing rather than letting it sit unreviewed.
Permit-portal fields and cadence are set by the jurisdiction, not the vendor
The Census Building Permits Survey documents authorization, permit-issuing place, and valuation as public-record concepts 1,2 — but the searchable fields, lifecycle labels, and update frequency on any specific local portal are set by that jurisdiction, so a channel that works well in one territory can behave differently in the next.
Document what each covered jurisdiction actually publishes and how often, rather than assuming portal behavior generalizes across territory boundaries.
Channel by channel
Six channels, and what each one is actually good for
No channel here is a complete system by itself. Each has a different lead-time profile, a different effort cost, and a different failure mode when it goes unmanaged.
The more useful comparison isn't a single "earliest" ranking — it's how early a signal shows up, how certain the project is, how far the channel scales across a territory, and how much qualification work lands on the rep. One dealer-sales channel breakdown frames it almost exactly this way: development and entitlement data as early but speculative, jobsite observation as certain but hard to scale, permit data as structured but slower to arrive, and referrals as better for finding people than for counting projects 11.
| Channel | What it is | Lead time | Effort | Manager question |
|---|---|---|---|---|
| Permit and public-record portals | City and county portals publish new-construction and major-remodel filings. Coverage, searchable fields, and update frequency vary by jurisdiction — some post daily, others in weekly or monthly batches (sourced below the table). | Early — often before framing starts | High if pulled by hand across several jurisdictions | Which jurisdictions does your territory actually cross, and who checks each one on a set schedule? |
| Builder and general-contractor relationships | A GC or production builder with a standing account can flag upcoming work before it reaches a public record. It depends on relationship maintenance, not a data pull. | Earlier than a permit — no fixed lead time | Ongoing relationship investment, not a one-time setup | Which accounts get a standing check-in, and who owns that relationship if the rep changes territory? |
| Plan rooms and bid boards | Regional plan rooms and bid boards list projects out for bid, useful for larger or commercial-adjacent residential work that a permit record alone will not fully describe. Planning-stage intelligence services can see the same class of project even earlier — Dodge, for one, says it tracks projects from a first planning permit months before they reach a bid board at all 12. | Mid — during the bid window | Moderate; usually a paid subscription with a review routine | Is the subscription scoped to categories this yard actually serves, or is it producing noise? |
| Trade and supplier referral networks | Framers, truss suppliers, and other trade contacts often learn about a project before the general market does. A referral is not a qualified lead, but it is frequently the earliest signal available. | Early — informal and inconsistent | Low cost, high relationship dependency | Does the team have a habit of asking trade contacts what they are seeing, or does this only happen by chance? |
| Existing-customer and account referrals | A satisfied account is a plausible source of introductions to the next project — its own, or a builder it works with. This channel scales with account satisfaction, not marketing spend. | Variable | Low direct cost; depends on account relationship quality | Is asking for a referral a standard step after a good job, or does it depend on one rep remembering? |
| Local trade associations and events | Regional builder and remodeler association meetings put a sales team in front of people planning work that has not reached a public record yet. | Early — relationship-driven, not transactional | Time investment; return is cumulative, not immediate | Is attendance assigned to someone accountable for following up, or is it treated as optional? |
Permit-portal fields and cadence are defined by the jurisdiction publishing them, not by any single vendor 1,2, and visibility speed varies a lot as a result — from a few days in fast-moving markets to two or three months in slower ones 9,10. Check what your specific jurisdictions actually do rather than assuming a national number. For how to read the fields a permit record actually returns, see the companion field guide Building Permit Data for Sales.
Weighting the mix
Which channels matter most for which project type
The six-channel table above treats every channel as equally relevant everywhere, which is not how a real territory works. A custom single-family build, a production-builder tract, and a small multi-family project tend to surface through different channels first — weighting the mix to a territory's actual project types is more useful than running every channel at equal intensity.
| Project type | Leading channels | Why |
|---|---|---|
| Custom single-family | Builder/GC relationships, trade referrals | A custom home often starts with a relationship between the owner and a builder long before a permit is filed. Relationship channels tend to see it first. |
| Production-builder tract | Permit portals, standing builder accounts | Production builders file permits in predictable batches within a subdivision. A portal covering the right jurisdiction, paired with a standing account relationship, catches the pattern early. |
| Small multi-family (2–4 units) | Permit portals, plan rooms | Small multi-family work is more likely to appear in a permit filing with a stated unit count, and larger projects in this category sometimes clear a plan-room threshold that single-family work does not. |
| Remodel-to-teardown rebuild | Existing-customer referrals, trade referrals | A teardown or major rebuild frequently starts as a remodel conversation. Account relationships and trade contacts often learn about the scope change before a new-construction permit is filed. |
For the residential new-build case specifically, see Residential Construction Leads for Lumber Dealers.
Setting it up
Four steps to a channel mix a team can sustain
Outside sales work already carries several operating records — orders, receivables, stock, and job pricing 3. A lead-generation channel that has no owner and no review rhythm adds to that load without adding coverage.
1. Map the territory to real channels
List the specific jurisdictions, accounts, plan rooms, and referral relationships your team can realistically sustain — not every channel that theoretically exists.
2. Assign one owner per channel
A channel without an owner degrades first. Give each source a name, a check-in cadence, and a place to log what it produced.
3. Set a review rhythm per channel type
Portals with daily updates need daily or near-daily review; relationship and referral channels need a standing check-in cadence instead of a data pull.
4. Hand results to the management workflow
Generation ends where verification, prioritization, ownership, and follow-up begin — see the companion guide for that workflow.
Keeping the mix current
Review the channels, not just the leads they produce
The companion guide's daily and weekly cadence reviews individual signals. A separate, slower cadence should ask whether each channel itself is still worth running — a relationship channel tied to one rep, or a portal scoped to a jurisdiction the territory no longer covers, can keep looking active on paper while producing nothing useful.
| Trigger | Review | Action |
|---|---|---|
| Quarterly | Is each channel still producing, and is the territory boundary it covers still accurate? | Retire, replace, or reassign a channel that has gone quiet. |
| At rep turnover | Which relationship channels depended on the departing rep personally? | Reassign the relationship explicitly instead of assuming it transfers with the territory. |
| At territory change | Do the covered jurisdictions, plan rooms, and association chapters still match the new boundary? | Update the channel map before the next review cycle, not after a gap is noticed. |
Where this breaks
The habits that quietly narrow a territory
Thin margins make the cost of a missed project higher than it looks — industry commentary describes lumber-dealer net profit as commonly around single-digit percentages, which is why deliberate coverage is worth the operating cost 4. Lumberyards that have moved toward more deliberate, data-informed sales coverage describe it as a shift in habit, not a one-time project 5.
Running one channel well and ignoring the rest
A portal-only or relationship-only approach misses whatever that channel structurally cannot see. Review the channel mix, not just the strongest source.
No owner for a channel that used to be someone’s job
When a rep leaves or a territory shifts, an unowned channel quietly stops producing. Reassign explicitly instead of assuming coverage continues.
Treating a referral or portal hit as a qualified lead
Every channel produces a signal, not a qualified buyer. The management workflow — not the channel — is where qualification happens.
Subscribing to a data source with no review habit
A plan-room subscription or portal feed that nobody checks on a schedule is a sunk cost, not coverage.
After generation: the management workflow
This guide stops at discovery on purpose. A channel that produces a steady stream of signals is not useful by itself if nothing happens after the signal arrives — unowned records pile up, duplicate outreach annoys accounts, and a sales leader loses the ability to say which parts of the territory were actually reviewed this week. Generation and management are separate disciplines that both need to work.
Once a channel produces a signal, the work of verifying it, deciding whether it fits, assigning an owner, and following up is covered in How Lumberyards Find and Prioritize New Construction Leads.
Where Radar fits: monitoring and first-pass prioritization
Radar does not replace relationship channels, plan-room subscriptions, or a rep's own territory knowledge. In the free beta, it monitors supported local building activity and brings it into a prioritized project queue for review 6 — handling the permit-portal channel's daily-pull effort so the team's time goes toward relationship channels and rep verification instead.
See the related building permit leads workflow for product context. Applications are reviewed for territory coverage and fit before activation.
Sources
This guide separates public-record definitions, first-party vendor sources, attributed trade-association commentary, one disclosed sponsored article, and named dealer case studies from local sales judgment.
1Primary government source for the survey purpose, geographic levels, and release cadence — the base public-record channel covered below.
U.S. Census Bureau: Building Permits SurveySource date: May 14, 2026 page update; reused from the companion guide
Limitation: The survey covers new privately owned residential construction and is not a directory of buyer contacts.
2Primary definitions for authorization, permit-issuing place, and valuation — the fields a permit-portal channel actually returns.
U.S. Census Bureau: Building Permits Survey DefinitionsSource date: Current definitions page; reused from the companion guide
Limitation: Definitions explain the public statistics; they do not establish a channel’s coverage or lead time for a specific territory.
3First-party vendor source: outside reps depend on current order, receivables, stock, and job-pricing information from several operating records.
DMSi Agility — ERP Software for Building Materials & Industrial DistributionSource date: Copyright 2026; accessed 2026-07-28
Limitation: A single-vendor description, not a market-wide prevalence claim about how dealers source leads.
4Trade-association commentary on why thin margins make deliberate territory coverage worth the operating cost.
NRLA: FIRING LINE: Understanding Profitability in the LBM Industry…and How Salespeople Can Make or Break ItSource date: October 2025 article
Limitation: Attributed industry commentary, not an audited benchmark or a LumberFlow measurement.
5Trade-association perspective on lumberyards using more deliberate, data-informed sales coverage.
NRLA: Lumberyard 2.0: How Data and AI Are Helping Lumberyards Grow SalesSource date: July 2025 article
Limitation: Industry commentary; does not establish a universal channel mix or product result.
6First-party product source for the free assisted beta, prioritized project queue, and rep ownership boundary.
LumberFlow RadarSource date: Current product page; reviewed 2026-09-20
7Trade-association sales guidance framing dealer prospecting as three parallel disciplines: wallet share, underpenetrated accounts, and new-customer acquisition.
NRLA: FIRING LINE: 3-Pronged Approach to ProspectingSource date: March 2025 article by Mike McDole
Limitation: Attributed sales commentary from a named, credentialed author, not an audited industry study.
8Corroborates S7: NRLA-affiliated sales training devoted a full session to the same three-pronged framework.
NRLA: EBMDA Sales Seminar, Prospect Prep and Profit (Session: 3-Prong Approach to Prospecting)Source date: February 10, 2026 event listing
Limitation: An event listing, not a published article; used only to corroborate S7.
9Sponsored vendor guidance on permit-availability timing and a territory permit-follow-up process.
NRLA (Sponsored Content from SalesJack): How Permit Data and AI Help Lumberyards Win More BusinessSource date: July 2026; disclosed sponsored content
Limitation: Sponsored content hosted by NRLA, not independent research. Timing figures vary by jurisdiction.
10Vendor-reported permit-to-platform latency for one city.
PermitGrab — Indianapolis, Indiana permitsSource date: Dynamic page; accessed 2026-09-21
Limitation: Specific to Indianapolis; not a national or universal figure.
11Dealer-sales guidance framing channels by four dimensions (earliness, certainty, scale, qualification effort) and quantifying development-pipeline lead time.
SalesJack: How to Find Active Construction Projects — A Guide for Building Materials DealersSource date: Dated "March 5" with no year shown on the page
Limitation: SalesJack’s own dealer-sales guidance, not independent academic measurement; the lead-time figure describes development-to-materials-need, not relationship-to-permit-filing.
12Vendor claim that planning-stage project tracking can precede bid-board publication by months.
Dodge Construction NetworkSource date: Current product marketing; accessed 2026-09-21
Limitation: A single attributed vendor claim about its own product scope; "planning permit" is not the same as a final building permit.
13Named dealer example of permit activity routed to the owning rep and paired with automated follow-up.
SalesJack case study: PARR LumberSource date: No date displayed; accessed 2026-09-21
Limitation: Vendor-hosted case study, not a LumberFlow or Radar result. The linked $500,000 figure traces to an LBM Journal article (Feb. 2026) that was not independently recovered.
14Named dealer example of inbound website leads tied to ERP context and automated follow-up.
SalesJack case study: Evanston LumberSource date: No date displayed; accessed 2026-09-21
Limitation: Vendor-hosted case study, not a LumberFlow or Radar result.
15Named dealer example of existing-account and wallet-share targeting.
SalesJack case study: Hamilton Building SupplySource date: No date displayed; accessed 2026-09-21
Limitation: Vendor-hosted case study, not a LumberFlow or Radar result.
By Alex Wu, Founder & Supply Chain Technologist — last updated .
Frequently asked questions
What is lumberyard lead generation?
Lumberyard lead generation is the set of channels a sales team uses to learn about new-construction and major-remodel projects in its territory — permit and public-record portals, builder and GC relationships, plan rooms, trade referrals, and local associations. It is the discovery step that happens before qualification, prioritization, and follow-up.
How do I find construction projects in my territory?
Run more than one channel at once rather than relying on a single source. Permit portals surface public-record filings; builder and GC relationships and trade referrals often surface a project earlier, before it reaches a public record; plan rooms cover larger or bid-out work. Assign each channel an owner and a review rhythm.
Which channel finds projects earliest?
No single channel wins on speed every time. Relationships and referrals tend to surface a project first — sometimes before any public record exists. Permit portals are the reliable floor underneath that. If a dealer has access to entitlement or planning-stage data, that can run six to eighteen months ahead of when materials are actually needed, according to dealer-sales guidance 11.
Is a permit or referral the same as a qualified lead?
No. A channel produces a signal — a name, an address, a stage. Whether it is worth pursuing, who the actual buyer is, and what happens next is a separate qualification and management step, covered in the companion guide.
How is this different from the construction-lead management guide?
This guide covers where signals come from — the channel mix and how to sustain it. The companion guide, How Lumberyards Find and Prioritize New Construction Leads, covers what to do with a signal once you have one: qualification, ownership, and follow-up cadence.
Does Radar replace these channels?
No. Radar is a monitoring and first-pass prioritization layer for supported local building activity, brought into one queue for rep review 6. It does not replace relationship channels, plan rooms, or the rep’s own territory knowledge, and a queued project still requires rep verification before it is treated as a qualified buyer.
Do different project types need different channels?
Yes. A custom single-family home often surfaces first through a builder or trade relationship, long before a permit is filed. A production-builder tract tends to show up in permit-portal batches tied to a subdivision. Small multi-family work is more likely to clear a plan-room threshold. Weighting channels to the project mix a territory actually sees is more useful than treating every channel as equally important everywhere.
How many channels should a lumberyard actually run?
Enough to cover the territory’s real project mix, and no more than the team can review on a set rhythm. A channel with no owner and no review cadence is not real coverage — it is just a subscription or a login nobody actually checks. Start with the channels that best match the territory’s dominant project types, then add coverage deliberately rather than all at once.
What did real lumberyards actually do to make this work?
PARR Lumber, Evanston Lumber, and Hamilton Building Supply each documented a different combination in vendor case studies 13,14,15: permit activity routed straight to the owning rep, inbound website leads tied to ERP context, and existing-account wallet-share targeting. See the dealer examples above for what each one actually does.
How should a territory organize permit follow-up so nothing goes unowned?
One documented process ranks the 50–100 most active builders in a territory, separates existing customers from prospects, assigns each qualified opportunity to a specific owner by region, company type, or existing relationship, and sets a defined response-time standard instead of leaving permits to sit unowned 9.
Give every channel an owner and a review rhythm
Free during the beta, no card required — tell us your territory and we'll confirm coverage before your reps start working the queue alongside their relationship and referral channels.