How to size a credit line for a production homebuilder

Most line-sizing worksheets start in the wrong place. An analyst pulls the builder's permit list, multiplies lot count by average draw value, and calls it exposure. That number is only as good as the permit list, and a permit list tells you what a builder is entitled to build. It says nothing about what's moving through construction this quarter.

If you supply lumber, trusses, concrete, or rough-in packages to production builders, your credit limit is really a bet on draw timing. Set it too low and you lose share to a competitor who'll carry more paper. Set it too high against a builder who's slow-walking starts, and you're financing a lot sitting in silt fence with no slab poured.

Start with trailing closings, not the permit count

The permit count is a ceiling, not a forecast. A builder with 80 active permits in a county might have 30 under active construction, 20 sitting on a graded pad waiting for a market read, and 30 that will get pulled and never start. Sizing a line off 80 units assumes a draw cadence that doesn't exist yet.

Pull trailing 12-month closings by builder from your local MLS or the county recorder, and pair that with their current backlog (units sold but not closed, per their last investor filing if they're public, or per their sales office if they're not). Divide backlog by trailing monthly closing pace. That gives you a rough months-of-backlog figure, which is a better proxy for sustained draw volume than any permit total.

Build the limit off cycle time, not lot count

Once you have a realistic unit count moving through the build process, translate it into dollars using your own cycle-time math: average draw value per unit times the number of units you expect in active construction at any given point. That figure tracks sustained draw volume. The entitlement count doesn't.

A typical production schedule runs permit to foundation in 4 to 8 weeks, foundation to dry-in in another 8 to 12, and dry-in to closing in 60 to 90 days depending on the market and the builder's trade availability. If your terms are net-30 against material delivered at framing and rough-in, your real exposure window is the time between delivery and the builder's draw hitting their construction loan, not the full permit-to-closing span.

Multiply that exposure window by your expected delivery rate per month, and you get a credit limit tied to cash cycle rather than to how many lots a builder happens to hold entitlements on.

Where builders inflate the picture

Builders don't usually lie about permits. They pull permits early to lock in fee schedules before a jurisdiction raises them, or to hold a spot in a phased release, long before a crew shows up. A stack of pulled permits with no cleared pad, no footer forms, no framing lumber on site tells you the builder is land-banking entitlements, not building homes. If your credit terms were set off that permit count, you're carrying a limit sized for activity that may be six months away or may never happen if the market softens.

Checking the permit list against what's happening on the ground, lot by lot, on a cadence that matches your review cycle closes that gap. That's the work Pipeline Validation was built to do: it takes a builder's permitted-project list and returns a dated verdict per lot, active, stalled, or no activity seen, refreshed monthly against a current overhead pass.

A simple sizing checklist

Before you finalize a limit, run the builder through four questions. Trailing closing pace by month is the first. Current backlog in units, pulled from their last filing or their sales office, is the second. Third is realistic cycle time from permit to closing in this market. And last: of the lots on their permit list, how many show cleared pads, poured foundations, or framing underway right now?

The first three come from public filings and your own experience. The fourth is the one most credit desks skip because it used to mean a drive-by or a trust-the-builder conversation. If you want that last number without the windshield time, that's the whole reason Pipeline Validation exists.