Value-First Team — Client Relationship

Mead Lumber

Building materials and design-to-completion service for home builders, contractors and remodelers across the Plains and upper Midwest. meadlumber.com

USS + VFT co-delivery

Snapshot

What they do

Mead Lumber supplies building materials and personalized service to home builders, contractors and remodelers, carrying a project from the design phase through to completion across a multi-location footprint. Mid-market, privately held. Columbus, Nebraska.

Engagement

Custom integration work connecting their ERP and a building-permit data source into HubSpot, alongside their wider sales platform rollout.

Focus

Giving the sales side a view of new opportunity and customer context without moving anything out of the system that actually runs the business.

Delivery

Co-delivered by Value-First Team and USS.

The relationship

Where they started

Mead runs on BisTrack. Quoting, inventory, special orders, the whole ordering path — it is the system the business is actually operated from, and it works. Nobody wanted that to change, and the engagement never proposed that it should.

What BisTrack could not do was face outward. When a builder in a rep's territory pulled a permit for a new project, nothing told the rep. That opportunity surfaced only if a person happened to notice it, which in practice meant it often did not surface at all — across a footprint where permit activity ranges from a handful a week in the small markets to around a hundred in the larger ones.

The second gap was the mirror of the first. Customer information lived in the ERP, so a CRM would open as an empty shell — and a sales platform that cannot show a rep who they are looking at is a platform reps stop opening. Matching was its own difficulty: in rural markets the same contractor is written three different ways, often with no website and no email to match on, so any attempt to bring outside data in would generate duplicates faster than anyone could clean them.

So the real question was not which system wins. It was whether the sales side could gain a genuine view without asking anyone to leave, duplicate or replace the system they already trusted.

What we delivered

  • A building-permit feed into HubSpot — permits from eight subscribed regions arriving on a scheduled sync, filtered to the construction types and valuation range worth a rep's attention, each one attached to the contractor who filed it, with a daily digest that reaches the team without anyone going to look for it.
  • Contractor matching that holds up in rural markets — a unique contractor ID from the permit source made the primary matching key with a platform-level uniqueness constraint, backed by a four-step fallback: ID, then website, then name, then create. On the ninety-day backfill, twenty-four companies matched records that already existed instead of duplicating them.
  • A scheduled BisTrack customer and contact sync — incremental and one-way, moving only records new or changed since the last run, deduplicated on both email and Epicor customer ID, with contacts attached automatically to their parent company and handling for contacts whose company has not synced yet.
  • Run-level visibility as a deliverable, not a by-product — persistent state tracking and per-run history, so for any sync the team can see what was created, what was matched to something existing, and what errored.
  • Around fifty mapped permit fields, a complete field-mapping reference and technical documentation, so the mapping is something Mead's side can read rather than something only the builder understands.
  • Two integration alternatives built and demonstrated live — an embedded operational dashboard and an on-demand extension view — so the choice between full record sync and lighter approaches was made against working examples rather than estimates.

What changed

Permit data stopped being something anyone had to go and find. By the spring the feed was running without intervention and had dropped out of the issue list entirely — the client's own read at the time was that it was populating and doing what it was built to do, arriving as a daily digest rather than a system someone had to remember to open.

The matching problem was answered with evidence rather than assumption. Bringing outside company data into a CRM usually creates a duplicate cleanup job; here the approach was proven against a real ninety-day load first, where a quarter of the companies resolved to records that already existed instead of becoming second copies.

And the operations side took on no new risk to get any of it. The sync is one-way and read-only by design — nothing writes back, and BisTrack remained the system of record exactly as it was. The build was sequenced foundation-first, so customers and contacts land before anything associates to them, which is what makes job and quote data an extension rather than a rebuild.

In a sentence

Mead needed new-construction opportunity and customer context to reach their sales side without touching the ERP that runs the business — so the integration was built one-way and read-only, and their system of record never changed at all.

At a glance

Delivery

USS + VFT

Permit regions live

8

Permit fields mapped

~50

On record since

Jan 2026

Key contacts

Barry KrihaDirector of Marketing