Built for Asset-Based Carriers

Asset + Brokerage on
One Platform.

Dispatch your trucks. Broker your overflow. Settle both on the same screen — with AI handling carrier matching, document collection, and margin math.

No contracts. No setup fees. 14-day go-live.

$249/seat
Growth plan
1 screen
Assets + brokerage
7 AI
Employees included
14 days
To first load
The Problem

You're running two businesses on three systems.

Most asset-based carriers operating a brokerage division end up with a dedicated TMS for the fleet, a separate brokerage TMS for overflow loads, and a third AP/AR tool to reconcile both sides at month-end. That's three logins, three data models, and zero shared context between your dispatchers and your brokers.

When a shipper calls and asks about their load — whether it's on your truck or a contracted carrier — your team has to context-switch before they can answer. That delay is the operational cost of split systems.

HatchOS runs both operations in the same dispatch board, with the same carrier database, the same settlement engine, and the same AI layer watching everything.

Before HatchOS
Fleet TMS
McLeod / TMW
Brokerage TMS
Turvo / AscendTMS
AP/AR & Factoring
QuickBooks + spreadsheets
↓ Replace all three ↓
HatchOS — Unified Platform
Assets · Brokerage · Settlements · AI
Platform Capabilities

Built for how trucking companies actually operate

Five capabilities that replace the patchwork — purpose-scoped for fleets running dual-mode operations.

🗂
Unified Dispatch Board
Your own trucks and brokered loads share one live board. Dispatchers see asset availability and carrier capacity in a single view. No toggling. No reconciling later.
🚦
ELD Integration Hooks
Inbound ELD position and HOS data feeds into the dispatch board directly. Pull live driver location and hours-of-service status into load assignment without leaving HatchOS.
📋
Broker Authority Workflows
Broker authority compliance built in — rate confirmations, carrier onboarding, certificate of insurance collection, and FMCSA authority verification, all managed from one carrier record.
💵
Factor Routing + ACH Settlements
Route brokered payables to your factoring company automatically. Owner-operator and fleet settlements run on the same ACH pipeline — one settlement engine covers both sides of the business.
📊
IFTA-Ready Revenue Ledger
Every shipment records fuel surcharges, accessorials, and lane revenue at the transaction level. Export clean mileage and revenue data by state — IFTA prep that doesn't require a separate spreadsheet.
AI Employees — Trucking Context

The AI does the work, not just the describing

Three of HatchOS's seven AI employees are especially high-leverage for asset-based carriers running a brokerage operation.

Dash — Dispatch Copilot
Operations
Monitors the unified board for load gaps and asset capacity mismatches. When a brokered load comes in with a lane your fleet regularly runs, Dash flags it as an asset-first candidate before it goes to external carriers. On overflow, it matches against your preferred carrier network, surfaces rate benchmarks, and drafts the rate confirmation — in one action.
↑ Reduces empty miles on backhauls
📊
Mark — Settlements Clerk
Finance
Handles both sides of the settlement equation — driver pay and carrier payables run through the same period-close workflow. Mark catches margin compression before period close, flags anomalous fuel surcharge discrepancies, and generates settlement packages for owner-operators automatically at period end. No manual spreadsheet reconciliation.
↑ Owner-operator pay automation
🛡
Shield — Carrier Vetting
Compliance
FMCSA authority verification, insurance expiry monitoring, and double-broker detection runs automatically on every carrier in your network — not just new ones. For your own fleet, Shield tracks authority status and CDL expiry alerts. For brokered carriers, it enforces your onboarding standards before a rate confirmation is issued.
↑ Prevents cargo claims from bad carriers
ROI Math

What 75 trucks + a brokerage desk actually costs

Most TMS vendors don't publish pricing. Here's a real comparison for a mid-size fleet with a brokerage arm.

Current Stack — 75 trucks + 20 seats
Fleet TMS (McLeod/TMW) $3,500 – $6,000/mo
Brokerage TMS (Turvo/Ascend) $2,500 – $4,000/mo
AP/AR + settlements tooling $500 – $1,000/mo
Compliance (Highway/RMIS) $500 – $1,200/mo
Total stack cost $7,000 – $12,200/mo
HatchOS — Same team, one platform
20 seats × $249/mo (Growth) $4,980/mo
ELD integration Included
Shield AI (FMCSA + compliance) Included
7 AI employees Included
$2,020 – $7,220
Monthly savings vs. current stack

The math assumes nothing exotic.

A 75-truck fleet running mixed asset and brokered freight typically manages 15 dispatchers plus 5 brokers — that's 20 seats at the Growth plan rate of $249/month, totaling $4,980/month all-in.

The legacy stack comparison uses published floor pricing for each platform category. Mid-market fleets consistently report spending $8,000–$12,000/month across 3–4 tools before they consolidate.

  • No annual contract requirement — cancel anytime
  • No setup fee — migration concierge included
  • No per-load or transaction fees on top of seat cost
  • Scale plan adds dedicated CSM at $299/seat
  • White-label option available for enterprise fleets
Real Operation. Real Numbers.

Running today at Hatchway Trade Group

"
HatchOS gave us back our time. We went from 40-hour weeks managing spreadsheets and chasing carriers manually to having Dash handle the board and Rex surface the numbers. That's the difference — the AI does the work, not just describe it.
Hatchway Trade Group — RL Jarrett & Associates — running live since Q1 2026
898
Loads managed
$1.17M
Revenue booked
52%
Faster cycle time
14 days
Time to go live
Read the full case study →
Common Questions

Trucking-specific answers

HatchOS provides ELD integration hooks via webhook and REST API. Position data, HOS status, and inspection records from major ELD providers (Samsara, KeepTruckin/Motive, BigRoad, Omnitracs) can be piped into your dispatch board directly. The integration is configured once per provider — dispatchers see live driver status without leaving HatchOS. ELD integration is included in Growth and Scale plans.
Every load in HatchOS captures origin/destination and lane detail at the shipment level. The revenue ledger records fuel surcharges and accessorials per transaction. For IFTA, you can export a clean mileage-by-state and revenue-by-state report from the Finance module for any period. If your ELD is connected, mileage data can be pulled directly from GPS logs — no manual entry for quarterly IFTA prep.
No — owner-operator settlements and brokered carrier settlements run through the same Mark AI settlement engine. Owner-operators are set up as carriers with their own payment profiles, factoring assignments, and settlement rules. Mark calculates their pay at period close, flags discrepancies, and generates a per-driver settlement package including deductions, fuel advances, and accessorials. All settlements go through the same ACH pipeline.
Yes. HatchOS is built for dual-mode operations. You can operate your asset fleet under your MC number while brokering loads under a separate broker authority — both managed from the same platform. Rate confirmations, carrier agreements, and broker-carrier contracts are generated per-transaction based on the operating mode of the load. Shield AI monitors compliance for both your own authority and any contracted carriers.
For fleets migrating from McLeod PowerBroker or TMW, the typical migration window is 3–5 weeks for a parallel-run cutover. Your carrier database, customer accounts, and load history migrate via structured export from McLeod/TMW. Active loads are mapped to HatchOS during the parallel-run period — your fleet keeps dispatching throughout. HatchOS concierge migration handles the technical setup at no additional charge.
HatchOS supports custom factor routing for both your own receivables and your brokered carrier payables. Configure your factoring relationship in Settings → Factors — assign factors per shipper, per carrier, or per load type. Settlements are routed automatically based on your factoring rules. We support all major freight factors (OTR Capital, Apex, Triumph, RTS) with no lock-in or exclusive relationships required.
Yes — AscendTMS is one of the most common migration sources for growth-stage fleets adding a brokerage arm. The migration path covers carrier and customer import via CSV/API, load history transfer, and commission contract templates. AscendTMS migrations typically complete in 2–3 weeks. We have a dedicated migration playbook for AscendTMS available at hatchos.polsia.app/migrate/ascendtms.