Step 1
Detect supported local activity
Radar ingests supported public permit records and brings eligible project signals into one review workflow instead of leaving reps to repeat the same portal searches.
Radar Private Beta
Find the construction projects your sales team should call on next.
Radar ranks local building activity into a daily project queue for lumber sales teams.
Activation is by invitation while we expand. Tell us your territory and workflow; dealer demand helps determine what we build next.
9:41
LumberFlow Radar is construction lead software built for lumber dealer sales teams. It turns local building-permit activity into a prioritized project queue so outside reps can decide which opportunities to review and pursue next. Radar is currently a private beta, activated by invitation in supported territories.
Why visibility matters
The projects are already moving. The question is when your team sees them.
Public records can show that a project exists without telling a rep whether it deserves a call. Radar is designed to shorten the distance between finding a signal and making a deliberate review decision.
Project signals can sit across municipal portals, inboxes, spreadsheets, saved searches, and individual rep memory. A territory can look covered while early activity remains unreviewed. Reps may spend prospecting time assembling a list before they can decide which project, builder, or account is worth investigating.
That review job also sits beside the operating information a sales team already uses. DMSi describes outside reps needing current order, receivables, stock, and job-pricing information. That observation supports the narrow point that field selling depends on several records; it does not mean Radar supplies ERP, inventory, receivables, quote, or order data. See the DMSi Agility product page (accessed July 28, 2026).
Radar focuses on one earlier decision: which supported local project signals should enter a rep's review queue now?
Why this review matters
Which jobs get reviewed is a margin question, not only a volume one.
Mix is where dealer margin lives.
NRLA puts typical lumber-dealer net profit around 4% — about $400,000 on $10 million in sales. Commodity lumber typically carries a 20–25% gross margin versus 30–50% for doors, windows, and millwork, and high-performing yards have cut lumber from roughly 50% to roughly 30% of revenue.
How Radar works today
From local project signal to an owned next action
The current beta turns supported public activity into a visible, deterministic review workflow. Every step keeps qualification and follow-up with the sales team.
Step 2
Filter and prioritize
Deterministic rules exclude ineligible records and rank the remaining activity with visible project signals. The score supports triage; it does not declare a buyer qualified.
Step 3
Give reps a daily queue
All, Mine, and Team views show what is available, what a rep owns, and what another teammate has claimed so the territory can be reviewed together.
Step 4
Capture the next action
A rep can claim a project, log activity, nurture it, disqualify it, or hand it off. Radar records the decision without automating outreach or replacing sales judgment.
Where Radar draws the line
Radar organizes public project signals for your team to review. It does not replace rep judgment, your systems, or your supplier and customer relationships.
- A project signal is a starting point, not a qualified buyer — reps validate before acting.
- Reps confirm builder and applicant identity before acting.
- Radar is expanding market coverage during the Private Beta.
- Radar does not replace your ERP or CRM.
- Radar and Procurement do not share workflow data today.
What the queue gives your team
A rep asks the questions that matter: Is the project inside our delivery area? Is the work relevant to what we sell? Can we identify a builder, applicant, or account to validate? Is the timing actionable, premature, or already too late?
Radar gives that review one starting point and one owner. Teams inspect coverage, avoid duplicate claiming, and record why a signal moved forward, entered nurture, was disqualified, or needed a handoff.
Reps validate every signal. The beta works best with teams ready to make that call and tell us where the data or workflow needs to improve.
Built for lumber sales
A working queue, not another generic list
The distinction is the review workflow around the record, not a claim that its underlying public records are fresher, broader, or more accurate than another source.
| Raw lead or permit feed | LumberFlow Radar |
|---|---|
| Records to search, sort, and interpret | A prioritized daily queue to review |
| Generic permit and project fields | Lumber-sales-oriented project triage |
| Individual exports, saved searches, or lists | Shared claim ownership and team visibility |
| No dealer-specific workflow state | Review, activity, nurture, disqualify, and handoff states |
Private Beta fit
Who should request activation
The strongest beta requests describe a real delivery territory, a current project-discovery habit, and a team willing to review why a signal is or is not useful.
- Lumberyards, LBM dealers, distributors, and relevant wholesalers.
- Owners, GMs, sales leaders, and outside sales reps.
- Teams serving a defined delivery territory.
- Teams willing to review project signals and explain what was useful.
- Teams able to join a short workflow-fit call during the beta.
A clear fit matters more than a broad promise
Radar is built for lumber dealer sales teams deciding which local projects to investigate. It is not a consumer-lead service for contractors, an autonomous outbound system, a takeoff platform, or a replacement for account management.
Tell us the counties, municipalities, or delivery radius your reps cover and how they find projects today. Specific territory information helps us evaluate data support and prioritize where the beta should expand.
Also tell us what a useful queue decision looks like — new residential work to review, or clearer ownership across outside reps. We review workflow fit manually, not by promise.
Two independently useful products
Find the project on the sell side. Protect the decision on the buy side.
Radar is the sell-side direction: find the project and focus the rep. LumberFlow Procurement is the buy-side product: compare supplier responses, keep freight and lead time visible, and support a buyer-approved purchasing decision.
The long-term direction is a clearer path from demand signal to purchasing decision. That direction is not a current integration claim. The products are independently useful and do not share workflow data today. A sales team can evaluate Radar without changing its buying workflow, and a buying team can use Procurement without Radar.
For a broader view of macro permits, housing starts, and lumber demand, read the housing starts and lumber demand guide. Radar serves a different job: organizing supported local project-level signals for rep review.
Radar Private Beta
Request an activation invite
Share the territory your reps cover and what would make a daily project queue useful. The form is intentionally compact because the first step is workflow fit, not a long procurement or technical evaluation.
We review each request manually. Territory demand helps prioritize expansion, but submitting does not promise activation, coverage, or a response date. If the current beta can support a useful conversation, we will follow up directly.
Frequently asked questions
Radar Private Beta questions
The answers below state the beta boundary plainly so a project signal, an activation request, and a connected workflow are not confused with promises Radar has not made.
What is a construction lead for a lumber sales team?
A construction lead is a project signal that may deserve review by a lumber sales rep. It can indicate where building activity is moving, but it is not automatically a qualified buyer, a material list, or a guaranteed sales opportunity.
How does Radar find construction projects?
Radar ingests supported public permit records, excludes ineligible activity, and ranks the remaining project signals using visible project attributes. Reps receive a daily queue they can review, claim, and move into an appropriate next-action state.
Is every permit a qualified lead?
No. A permit is an early project signal, not proof that a builder is identified, materials are ready to quote, or an account will buy. Radar helps organize review; the sales rep still validates the project, buyer, timing, and fit.
Which territories does Radar cover?
Radar is expanding market availability during the Private Beta. Submit your sales territory with your activation request; dealer demand helps us prioritize where Radar expands next.
Is Radar generally available?
No. Radar is a Private Beta activated by invitation in supported territories. The beta is designed to validate territory coverage and the daily sales workflow before availability expands.
Does Radar replace a CRM or ERP?
No. Radar is a project-discovery and prioritization workflow for lumber sales teams. It does not replace customer records, inventory, receivables, quoting, order management, or other operating functions in a dealer CRM or ERP.
Does Radar connect to LumberFlow Procurement?
Not today. Radar and LumberFlow Procurement are independently useful products and do not exchange workflow data. Radar supports sell-side project discovery; Procurement supports supplier-response comparison and buyer-approved purchasing decisions.
What happens after I request an activation invite?
You receive an email confirming the request. We review each territory and workflow manually, then follow up when there is a useful fit or when coverage planning needs more detail. A request does not promise activation or a response date.
Radar Private Beta
The projects are already moving. See which ones deserve your team's next call.
Tell us where your reps sell and how they find projects today. Applications with a clear territory and active workflow are reviewed first.