Skip to content
FactorFox

Freight distribution

LoadBoard Network

One posting reaches many load boards, which is how a factor's private carrier board gets filled.

Everything below came from that company’s own website or from dated trade coverage, and the sources are at the foot of the page. Where they publish nothing, this page says so rather than filling the gap with an estimate.

Two claims, kept apart

Freight distribution

The relationship

A fact about two companies. Ours to assert.

FactorFox works with LoadBoard Network. Confirmed 28 August 2026. It requires no code to be true and it implies none.

The connection

A fact about software. Engineering’s to evidence.

Not built

No row exists in the integration register, so nothing in the product connects to them today.

The same two questions are worth asking of any vendor’s partner page, including this one.

What they do

What LoadBoard Network actually sells.

  1. LoadBoard Network is a load posting aggregation service for freight brokers and shippers. It is deliberately not a load board itself. A broker enters a load once and it is distributed to many boards at once.

  2. Founded in 2022 by Mark Draeb, based in Hebron, North Dakota. Draeb previously co founded PostEverywhere, which was acquired by Truckstop in 2018 and retired in 2022, and LoadBoard Network was built as its successor.

  3. Pricing is published openly on their site, banded by broker revenue or shipment volume, with unlimited users on every plan. Published pricing is rare enough in this industry to be worth noting.

Why it matters

Why a funding business should care.

Written for the lender rather than for the borrower, which is the audience every page on this site is written for.

  1. This is the partner with the least direct connection to a funding decision, and it would be dishonest to dress it up as more. It does not assess credit, file liens, detect fraud or move money.

  2. Its relevance is distribution. A factor that operates a private load board for its own underwritten carriers has a supply problem, not a demand problem, and this is a pipe that fills it with brokered freight.

  3. The strategic reading is that a factor who can put freight in front of its own carriers is competing on something other than rate, which is the recurring theme across this entire partner group.

What would move

What would flow between the two systems, and in which direction.

This is the question a technology partnership starts with, because it determines whether there is anything worth building. It describes the exchange, not a shipped feature.

  1. One direction: load postings out from a transport management system, distributed across the board network.

  2. For a factor operating a carrier facing board, the plausible flow is inbound load postings into that board.

  3. They publish no public API documentation. Their documented integration pattern is with transport management systems using an integration key, so any connection here would be a partner negotiated build.

Where this stands in the product

The connection, stated the way the register states it

No register rowNothing connects today

A commercial relationship. No connection is recorded in the FactorFox integration register today.

How every status word is defined

What we could not establish

Published deliberately, rather than quietly left out

Employee count, funding, revenue and ownership structure.

A partner page that has an answer for everything has usually stopped checking. Several companies in this group publish no founding year and no headcount at all, and that is a finding about the industry rather than a gap in the research.

Sources

Where these facts came from.

Check them. That is the entire point of publishing them.

The commercial relationship was confirmed by FactorFox on 28 August 2026. The connection status above is not confirmed by anybody at FactorFox. It is read from the integration register, which only engineering writes to.

Ask us what connects today, and we will answer with the register open.

Not with a logo strip. If the answer is that nothing connects to a vendor you depend on, you will hear that in the first conversation rather than in week five of an implementation.