LumberFlow

Two focused products for lumber dealers

Find the next project. Make the right buy.

LumberFlow helps lumber dealers find projects worth pursuing and make buying decisions that protect margin.

Radar in action, from local project signal to one owned next action.

Radar is in Private Beta. LumberFlow Procurement is available now.

Compare LumberFlow products

Choose the workflow your team needs

Radar — Private Beta

Find the construction projects your sales team should call on next.

Explore Radar Private Beta

Procurement — Available now

Turn supplier emails and quotes into buyer-approved purchasing decisions.

See Procurement
The margin math

Two decisions decide whether the year is profitable.

Dealers run on a few points of net profit. Both of the decisions that move that number get made from information that already exists and that nobody has time to review.

Industry commentary from the NRLA puts typical lumber-dealer net profit around 4% — roughly $400,000 on $10 million in sales. Two decisions move that number: which jobs your team chases, and what you pay for the material.

The first is a margin decision, not only a volume one. NRLA reports commodity lumber typically carries a 20–25% gross margin while doors, windows, and millwork can carry 30–50%, and that high-performing yards have cut lumber from roughly 50% of revenue to roughly 30%.

Both decisions get made from information that already exists and that nobody has time to review. Radar organizes the sell-side review. Procurement organizes the buy-side one.

Radar Private Beta

Give outside sales a clearer place to look next.

Radar organizes supported local building activity into a prioritized daily project queue. Reps review the signal, claim ownership, and decide the appropriate next action; Radar does not turn a permit into a guaranteed buyer.

See

One ranked daily queue

Supported local building activity arrives in one prioritized queue instead of scattered portal searches.

Claim

Visible team ownership

All, Mine, and Team views show what is open and who already owns it, so a territory does not look covered while signals sit unreviewed.

Act

A recorded next action

A rep claims a project, logs activity, nurtures it, disqualifies it, or hands it off — Radar does not automate outreach or replace sales judgment.

Project signals still need rep validation. Radar does not turn a permit into a qualified buyer.

9:41
Radar daily project queue on a phone, showing All, Mine, and Team tabs and a ranked project card with permit applicant, address, and match score from public permit records
LumberFlow Procurement

From Supplier Email to Buyer-Approved Decision

Six procurement steps, one reviewed workflow: extract, reach, compare, time, approve, and learn.

1
EXTRACT

Quote Extraction

Supplier emails and PDFs arrive with mixed species, grades, dimensions, freight terms, and lead times. Buyers lose hours turning that raw email into comparable quote data.

LumberFlow reads every supplier response, extracts species, grade, dimensions, volume, $/MBF pricing, freight terms, and notes, then keeps the original email attached for review.

See this step in the interactive demo
2
REACH

Supplier Reach, Automated

Most RFQ waves stop at the contacts a buyer remembers first, even when other suppliers are a better fit for the product, lane, or timing.

The agent suggests relevant suppliers, drafts personalized RFQs and follow-ups, preserves thread context, and lets the buyer approve the outreach before it sends.

See this step in the interactive demo
3
COMPARE

Market Price Intelligence

The cheapest headline $/MBF can lose once freight, lead time, SKU substitutions, and team benchmarks are included.

LumberFlow ranks every offer by delivered $/MBF, freight, lead time, SKU match, target price, and recent team benchmarks so buyers compare the real delivered economics.

See this step in the interactive demo
4
TIME

Market Timing on Every Buy

A quote can look right until the market moves before the load lands. Buyers need current context at the moment they approve, not after the weekly report catches up.

Daily market analysis and weekly forecasts sit beside active RFQs so the buyer can weigh timing risk before sending a counter, award, or PO.

See this step in the interactive demo
5
APPROVE

You Approve Every Move

Automation only works for lumber teams if buyers keep control of supplier relationships, counters, awards, and purchase orders.

LumberFlow drafts RFQs, follow-ups, counters, awards, and POs. A buyer reviews and approves every action before anything leaves the system.

6
SHARE

One Shared Buying Brain

Pricing knowledge disappears when it lives in one buyer's inbox, a whiteboard, or a side spreadsheet no one else sees in time.

Every supplier response, quote, benchmark, and award becomes shared procurement intelligence so the next buyer starts with the team context already in place.

See this step in the interactive demo
Procurement payoff

What an AI procurement agent gives back to the buying desk

Modeled from email-heavy lumber sourcing workflows where buyers manually extract quotes, chase suppliers, compare market pricing, and time buys with scattered market context.

12
Average time saved per buyer per week
hours
$2,400
Modeled labor value recovered per buyer per month
typical
$800
Margin exposure protected per load with freight and forecast context
typical
50
Personalized RFQs drafted in one buyer-approved workflow
in under 5 minutes
Market context, built in: daily analysis and a 7-day forecast pulse sit beside every quote, so buyers weigh each decision with current market information — not a week-old report.
Loading forecast pulse...
LumberFlow Procurement

Every supplier quote becomes buyer-ready pricing context

LumberFlow brings quote extraction, freight terms, team benchmarks, and market timing into one shared view so every buyer compares the quote before approving the next move.

Try Interactive Demo
The shift

What Changes When Sales Sees the Project and Buying Sees the Price

Without LumberFlow

  • RadarProject discovery depends on whoever happened to hear about the job
  • RadarReps check municipal portals one at a time, or skip it and work the phone
  • RadarA territory looks covered because nobody can see what went unreviewed
  • ProcurementSupplier emails, PDFs, and price sheets scattered across individual inboxes
  • ProcurementManual spreadsheet cleanup before a buyer can compare offers
  • ProcurementTime to canvass only a handful of familiar suppliers per RFQ
  • ProcurementDecisions made on stale reports, gut feel, and side-channel market chatter
  • BothSales knowledge and pricing knowledge both walk out with whoever left

With LumberFlow

  • RadarSupported local building activity arrives in one ranked daily queue
  • RadarOne prioritized list, tiered by buy-timing, lumber volume, and who's buying
  • RadarEvery project is claimed, nurtured, disqualified, or handed off — visibly
  • ProcurementQuotes extracted into one shared buying workspace with source emails attached
  • ProcurementDelivered $/MBF, freight, lead time, SKU match, and benchmarks lined up automatically
  • ProcurementRFQs and follow-ups drafted for a broader supplier set in minutes
  • ProcurementDaily market signals and forecasts beside active quotes, with buyer approval on every send
  • BothProject history and quote history stay with the company as shared team intelligence

Radar and Procurement are separate products today and do not exchange workflow data. Each can be bought on its own.

Built by operators

Why I Built LumberFlow

Lumber runs on two decisions — which job to chase, and what to pay for it. Both get made with worse information than they deserve.

AW

Alex Wu

Founder & Supply Chain Technologist

10+ years in wood products supply chain and pricing systems

For a decade I watched lumber buyers make six-figure inventory commitments based on a weekly pricing report and whatever they heard from a supplier yesterday. That knowledge lived in individual buyers' heads and inboxes — and walked out the door when someone left.

Then I started asking the sales side the same questions and got the same answer back. Reps knew their accounts cold, but finding the next project meant remembering it, hearing about it, or clicking through municipal permit portals nobody had time for. A territory could look covered and still have projects moving through it unseen. It was the same problem wearing different clothes: the information a dealer needs to make money already exists — it is just scattered, and nobody has time to review it.

So LumberFlow works both ends. Radar brings supported local building activity into one ranked queue so sales knows which projects to work next. Procurement captures every supplier quote, layers in daily market analysis and ML price forecasts, and turns email threads into buying intelligence the company owns instead of one inbox. They are deliberately separate products — you can buy either one. They live under one roof because they answer the same question from two directions: where does the next profitable load come from?

I'd be glad to walk you through either one personally.

Book 15 Minutes With Me

No sales team, no pitch deck — just a live walkthrough. Radar or Procurement — tell me which.

Our Industry Credibility

10+ years inside wood products supply chain and pricing systems — I lived the problem before I built for it

Built AI that understands lumber-specific data: species, grades, dimensions, $/MBF, mill dynamics

Radar scores projects on lumber-sale logic — buy-timing, package size, and who actually purchases — not a generic B2B lead score

Designed both products so knowledge belongs to the company, not to one rep's memory or one buyer's inbox

Radar runs on supported public building-activity records, and every signal is reviewed and validated by a rep before it becomes outreach

Workflow proof

What Each Product Touches — And What It Leaves Alone.

No supplier portal. No inbox takeover. Your team keeps the relationship and gets a cleaner buying record.

Radar

  • Radar works from supported public building-activity records. It does not scrape private contact databases or buy consumer lead lists.
  • A rep reviews and claims every project signal. Radar does not send outreach on your behalf.
  • Radar does not replace your CRM or ERP, and does not exchange workflow data with Procurement today.

Procurement

  • AI drafts the RFQ, follow-up, counter, award, and PO. A buyer approves before anything leaves the system.
  • Quote extraction is reviewable: species, grade, dimensions, $/MBF, freight terms, lead time, and supplier notes stay attached to the original email.
  • Suppliers keep emailing as usual. LumberFlow uses a managed RFQ inbox that CCs your corporate domain for records.
Trusted infrastructure

Built on Enterprise-Grade Technology

Vercel - Deployment Platform
Clerk - Authentication
Google AI - Gemini
Google Cloud Platform
Cloudflare - CDN & Security
Stripe - Payments
Support & Enablement

Questions Lumber Teams Ask About LumberFlow

Straight answers on Radar project discovery, Procurement workflows, buyer approval, and supplier experience.

Two decisions. Start with either one.

Radar is in Private Beta for lumber sales teams. Procurement is available now for buying teams. They are sold and used separately.