DAT Load Board Clone Business Model: Six Lines, One Load Record
Freight platforms make money in two different ways at once: a subscription that is predictable and a transaction fee that is not. Six revenue lines are modelled separately here so an operator can tune one without disturbing the others, and because the bid and the assignment both land on the same load record, a fee event always has an unambiguous thing to attach to.
Design My Revenue Model →See PricingWhy Liquidity Comes Before Pricing
Six observations that decide whether a freight platform earns anything, in the order they start to matter.
An empty board is worth nothing to either side
Carriers will not subscribe to a board with no freight, and shippers will not post to a board with no carriers. Whichever side you solve first has to be given away, and pricing before that point simply stops the marketplace forming at all.
Carriers pay for access, brokers pay for evidence
The two sides value different things. A carrier is buying visibility of freight; a broker is buying verification, credit scores and performance history at the point of tender. Pricing them identically leaves money on one side and drives the other away.
Subscriptions are predictable, transactions are not
A subscription tier gives you revenue you can forecast and staff against. A per-load fee scales with the volume the board actually clears. Most durable freight platforms run both, because either alone is either capped or unpredictable.
A fee needs something unambiguous to attach to
Because the bid and the assignment both land on the same load record, a placement fee or a commission on an accepted bid has one event to fire against. Platforms where booking happens off-system cannot charge a transaction fee at all, which is why they stay subscription-only.
The console can run a desk, not just watch one
The same admin control plane that governs the platform can run brokerage or dispatch operations on behalf of customers. That turns a software business into a services business alongside it, at whatever ratio you choose.
Plans have to move without a release
Pricing in freight gets renegotiated with large accounts. Tiers held in a pricing_plans table as configuration rather than in code mean an enterprise negotiation is an afternoon rather than a deployment.
There is no revenue projection on this page and no market sizing. Both would mean inventing assumptions about your lane volume and carrier base and presenting them back to you as findings.
Six Revenue Lines, One Platform
Each is modelled separately so you can tune one lever without disturbing the others. All six ship in the base build.
Subscription tiers
Recurring seat or tier-based plans through Stripe. The documentation models Basic at $49 to $99 per user, Professional at $149 to $299 and Enterprise pricing, all held in the pricing_plans table as configuration rather than code.
Transaction fees
Per-load placement fees or a commission on an accepted bid. Because the bid and the assignment both land on the same load record, the fee event has an unambiguous thing to attach to rather than needing a reconciliation.
Payment processing margin
A margin on processing once Stripe is connected. The payment adapter ships with a mock implementation, so the whole flow is demonstrable before any live key exists and you can model the margin before committing to a processor.
Managed dispatch services
Operator-led brokerage or dispatch run through the admin control plane. The console that governs the platform can also run desk operations on behalf of customers, which is a services line beside the software one.
Add-on modules
AI coverage, cold chain monitoring, compliance submissions, advanced analytics and extra storage sold as modules. Module toggles mean an add-on is switched on for an account rather than deployed, so upsell is a setting.
White-label licensing
License the platform to partners under their own brand. System configuration, module toggles, branding, pricing plans and SEO surfaces are what make that possible without maintaining a fork per partner.
The two that move the numbers most are subscription tiers and transaction fees. One is predictable recurring revenue, the other scales with the volume the board actually clears.
How the Category Itself Makes Money
The reference model for freight marketplaces, and which parts of it this platform reproduces.
| Line | What it sells | In this platform |
|---|---|---|
| Board subscriptions | Access to freight, sold to carriers and brokers | Tiered plans in the pricing_plans table, billed through Stripe |
| Market rate data | Rate intelligence sold as a premium tier | Rate history and hot lanes from your own data; an external feed is your subscription |
| Carrier vetting | Verification and credit information sold to brokers | Company verification, ratings, credit scores and fleet visibility, built in |
| Transaction fees | A cut of freight that clears the platform | Placement fees or commission on an accepted bid, on the load record |
| TMS software | Operational software sold to carriers separately | Included rather than a second subscription, which is the competitive argument |
| Managed services | Brokerage and dispatch run for the customer | Run from the same admin control plane that governs the platform |
The TMS row is the one worth dwelling on. In this category carriers usually pay for a load board and an operational system separately, and bundling them is a real differentiator for a challenger.
Monetization Approaches, Ranked by Growth Stage
Which line is realistic at which point, and what has to be true before it works.
| Stage | The line that works here | What has to be true first |
|---|---|---|
| Pre-launch | White-label licensing | You are selling the platform to an operator who already has the freight |
| One side only | Nothing | Whichever side you have has nothing to transact against yet |
| Both sides present | Carrier subscriptions, priced low | A carrier logging in on a Monday finds freight worth bidding on |
| Freight clearing | Transaction fees | Bookings happen on the platform rather than moving to the phone |
| Brokers active | Broker tiers and vetting access | Enough carrier history exists that verification and scores mean something |
| Established | Managed services and add-on modules | Customers ask you to run the desk, or want capabilities beyond the base |
The fourth row is the one to watch. If bookings drift back to the phone, your transaction fee disappears, which is the commercial reason dispatch, tracking and invoicing all live on the same record.
What the Alternative Actually Costs
Before any of the six lines earns anything, the platform has to exist. Here is what that costs each way, in the terms the documentation actually states.
What we do not publish, and why
There is no revenue projection on this page and no market sizing. Both would require inventing assumptions about your lane volume, your carrier count, your subscription mix, your take rate and how much freight actually clears the board rather than moving to the phone, and then presenting them back to you as a finding. The levers are all here and all operator-set; bring your own expected numbers and we will model them with you rather than for you.
The distinction that matters commercially: a per-seat fee is charged on exactly the carrier growth you worked hardest for, and a one-time price is not.
Which Lever to Switch On First
A practical sequence for the first year, with the signal that tells you the next line is ready.
| Order | Switch on | Move to the next when |
|---|---|---|
| First | Free access on both sides | Loads posted on Monday are covered by Wednesday without you calling anyone |
| Second | Carrier subscription, entry tier only | Carriers log in daily because the board is where the freight is |
| Third | Broker tier with vetting access | Enough carrier history that verification and credit scores are informative |
| Fourth | Transaction fee on accepted bids | Bookings reliably complete on the platform rather than moving to a call |
| Fifth | Add-on modules | Customers ask for cold chain, analytics or compliance beyond the base |
| Sixth | Managed services and licensing | Someone asks you to run their desk, or to run your platform under their brand |
Every one of these is a configuration change in the admin console rather than a release, because plans and module toggles are held as data.
Three Ways Operators Run This Platform
The same six lines, weighted three very different ways. Most operators are a blend of two.
The regional board
One country or corridor served properly, competing on local carrier density rather than on national scale. Subscriptions carry it, and the bundled TMS is the reason a carrier chooses you over a larger board.
- Carrier subscriptions priced against local willingness to pay
- The included TMS is the differentiator, not the board itself
- Transaction fees introduced only once coverage is reliable
The brokerage that productised
An existing brokerage putting its own operation onto the platform, then opening it to others. Supply and demand are solved on day one because the brokerage already has both.
- Managed dispatch is the existing business, now on better software
- Transaction fees viable immediately, because freight already clears
- Carrier subscriptions become a second line rather than the first
The white-label licensor
An operator deploying branded freight platforms for associations, shippers or regional groups from one codebase. Revenue is a licence fee and a share rather than end-user subscriptions.
- Module toggles and pricing plans make each deployment configurable
- No per-seat fee, so a large partner is not a larger bill
- Adapters mean each partner can use their own providers
The second shape is the most reliable start in this category, because it inverts the cold-start problem: the freight already exists and the software is what improves.
Common Freight Platform Monetization Mistakes
Five that are expensive to undo
Charging both sides at launch. One side has to be given away until the other is worth paying for. Charging carriers and shippers simultaneously on an empty board is how a marketplace fails before it forms.
Letting bookings move to the phone. The moment a deal completes off-platform your transaction fee is uncollectable and your rate history stops being real. Dispatch, tracking and invoicing living on the same record is what keeps the booking where the fee is.
Pricing carriers and brokers the same. They buy different things. A carrier is buying access to freight; a broker is buying evidence about carriers. One rate card for both leaves money on one side.
Selling the TMS separately. Bundling operational software with board access is the strongest argument a challenger has against an incumbent. Splitting it into a second subscription discards that advantage.
Hard-coding the plans. Enterprise freight customers negotiate. If a tier change needs a deployment, you will lose the account or spend a sprint on a contract you already signed.
Each of these is a configuration decision here rather than a code change, which is what makes correcting them realistic once you have the data.
See the modelled deployment and what we have not done yet
A modelled reference deployment for a mid-market brokerage, the six-step build process, and every limitation named in writing - on the Development Company page.
Frequently Asked Questions
Should I charge carriers or shippers?
Do you take a percentage of subscriptions or transaction fees?
How do I change a pricing tier for one customer?
Can I really charge a transaction fee?
What are add-on modules worth?
Is running a brokerage desk on the platform realistic?
Model it against your own lanes
Bring your expected carrier count, your lane volume and what you think a subscription is worth in your market. We will map the six lines against them rather than hand you a projection we invented.
Explore the DAT Load Board Clone
Six revenue lines. One load record. No cut taken.
Subscription tiers you set in a table, transaction fees on accepted bids, processing margin, managed dispatch, add-on modules toggled per account and a platform you can license, on full source you own outright.
Talk to Us →Miracuves is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by DAT Load Board.
“DAT Load Board Clone” is used descriptively. It is how the software industry refers to building a platform with functionality similar to DAT Load Board, and how clients search for it.
The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from the DAT Load Board website or applications.
DAT Load Board and all other third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.
