Read only
Observe the workflow and review its data without making changes.
Built by an LBM operator · For lumberyards and truss plants
Built by operators. Built around the work.
We’re operators. We started with the physical workflows—how material gets purchased, sold, pulled, loaded and delivered—then added the coding to build operating systems around how these businesses actually run.
We take a hybrid approach. Keep your ERP and choose how much LMBR does in each workflow. Start with read-only Shadow Mode, then use recommendations, drafts, or approved actions where you’re comfortable. You can use your ERP and LMBR at the same time. It’s up to you—not an all-or-nothing rollout.
The estimator shows its assumptions. It is not a customer result or a guaranteed savings claim.
Your workflows. Your comfort level. Your choice.
Hybrid by design. You set the pace.
Choose the level of authority for each workflow. Keep one read-only, ask another to prepare drafts, and allow a third to act within the permissions you approve. You do not have to give every workflow the same level of control.
Read and Recommend/Draft
Prepare recommendations or drafts for your team to review, edit, and approve.
Read and Act
Carry out approved actions within the workflow, permissions, and limits you choose.
Keep using your ERP and LMBR side by side for as long as you want. Choose the workflows, agree on the scope, and change the level of authority as your comfort grows. It’s up to you. It’s not all or nothing.
A delivery is promised. The material is committed elsewhere.
Take the controls.
Explore a sample operation. Follow the evidence. Make the next decision.
Prove the starting point
The first thing you buy is a controlled way to see what your own operation says.
Authorize
One branch, named people, approved exports, defined success measures, and explicit boundaries.
Reconcile
Normalize products and inventory while preserving the source and quarantining ambiguity.
Review
Bring auditable observations and recommendations to management without taking operational action.
Measure
Record decisions and referenced outcomes so verified savings, capacity, and opportunity stay separate.
The yard
Put a number beside every extra mile.
During Shadow Mode, a permitted aerial baseline and forklift travel measurements can expose repeated travel, bottlenecks, and layout questions. The point is not a colorful map. The point is a management decision backed by comparable before-and-after evidence.
Forklift travel measurements and a yard heat map are included in Shadow Mode at the agreed branch. Before collecting travel data, we agree on the equipment, site access, safety rules, data rights, and how routes and results will be measured.
Estimate the opportunity
Shadow Mode
Forty-five days. One authorized branch. Externally read-only.
The standard entry phase begins after data-readiness acceptance. LMBR stages approved product and inventory data, preserves lineage, identifies uncertainty, and presents recommendations for human adjudication. Missing customer data or access pauses the clock.
See how it works- Configured one-branch Shadow workspace
- Forklift travel measurements and a yard heat map
- Data-quality and ambiguity report
- Auditable recommendation and outcome history
- Executive evidence summary
- Final limitations and conversion readout
The rules it runs by
Evidence first. Authority only when it is earned and approved.
Read-only first
Shadow Mode begins without an ERP write path. Production authority requires a separate, named approval.
Uncertainty stays visible
LMBR preserves source lineage and routes ambiguous records for review instead of silently guessing.
People decide
Management can agree, disagree, override, defer, and record the reason and outcome.
Math stays inspectable
Assumptions, source data, recommendations, decisions, and measured outcomes remain distinguishable.
Your ERP stays in place
BOLT-ON begins beside the system you already run. Shadow Mode does not replace it.
Every material decision leaves a trail
The evidence, reviewer, decision, and outcome remain connected for later review.
Questions worth raising
Better here than three meetings in.
“Are you replacing our ERP?”
No. The current BOLT-ON entry phase starts beside it. The ERP remains the agreed system of record.
“We do not want AI writing into our ERP.”
Shadow Mode has no external write path. Any later production authority requires separate evidence, security, testing, permission, customer authorization, and commercial gates.
“Our data is not clean enough.”
Shadow Mode is partly a data-readiness exercise. Ambiguous records are quarantined with the reason instead of being treated as fact.
“Are the savings guaranteed?”
No. The estimator is planning math. Shadow Mode distinguishes verified savings, validated capacity, identified opportunity, assumptions, and unresolved evidence.
Meet Kenny Mays
I never thought I’d be known as a “Tech Bro.”
Kenny Mays built his career in building materials before building the technology around it. He started in sales in September 1999 and worked in lumberyards, truss plants and roofing yards. He retired in June 2026, before building LMBR.
“Every decision came back to two goals: make LMBR feel like a member of your team, not another system, and build something this industry has never seen.”
Next step
Start with the number.
Answer the yard estimator first, or book a 30-minute fit and data-readiness call with Kenny.