Cost to Build a Freight App Like Uber Freight or Flexport in 2026
A single-model freight MVP (brokerage load board, forwarding operations core, or visibility platform) costs $40K to $100K and takes 10 to 16 weeks. This guide breaks down the full cost across all three freight software models, explains how freight matching and milestone tracking actually work in plain language, covers the build-vs-buy math against Flexport fees and TMS subscriptions, and shows where freight software builds go wrong.

In this article
Short answer
A freight app like Flexport costs $40K-$100K for a first version (MVP) over 10-16 weeks. That covers one model: a brokerage load board, a forwarding core, or a visibility platform. A full platform with automated matching, carrier tracking, versioning (keeping a history of every change to each document), and a portal runs $90K-$220K over 16-28 weeks. Monthly costs are $500-$2K for carrier feeds plus hosting, EDI (the standard format carriers use to exchange shipment data), and messaging. Prototypes start at $10K.
Key takeaways
- One freight model done well is the MVP: a brokerage load board, a forwarding operations core, or a visibility platform. Do not build all three at once.
- Match acceptance, not match generation, is the hard metric in brokerage. A recommendation the carrier rejects because it ignores their preferred routes (lanes) and rates is worse than no recommendation.
- The milestone data model (how each shipment's events are organised) is the product in visibility builds. Every alert, status display, and analytics query comes from it. Get the 17 to 22 events per shipment right before building anything on top.
- Integration count is the single biggest cost and schedule variable, not the freight logic. Carrier APIs (connections to carrier systems), EDI feeds (standard shipment-data feeds), and ERP sync (keeping your main business system in step) should be scoped and prototyped first.
- The build pays back when platform fees cross roughly $40K to $60K per year, or when you move $5M+ in annual freight at 3 to 8% margin to a platform like Flexport.
- Treat freight documents as versioned records (every change kept as a new version), not file storage. A bill of lading gets amended after issue, and a folder of PDFs cannot hold that history.
You move $8M in freight per year. Your customers call to ask where their containers are. Your ops team spends two hours a day on status updates. And the platform you rent takes 4% on every shipment, which means you are paying $320K per year for visibility you do not fully own.
That is the wall most freight operators hit before they look at custom software. Not dissatisfaction with the technology. Dissatisfaction with paying for it forever, at rates that scale with your volume.
The real question is not whether to build. It is what to build first, what it costs, and whether the math holds. Here is the honest breakdown.
The cost, up front
A single-model freight MVP costs $40K to $100K and takes 10 to 16 weeks. Here is the full range:
| Scope | Timeline | Cost |
|---|---|---|
| Prototype (clickable demo to validate the idea before a full build) | varies | from $10K |
| Single-model MVP (brokerage load board, forwarding ops core, or visibility platform) | 10-16 weeks | $40K-$100K |
| Full platform (automated matching, multi-carrier tracking, documents, client portal) | 16-28 weeks | $90K-$220K |
| Multi-tenant scale (white-label SaaS - one system serving many customers, each under their own brand - plus an API layer, analytics) | 24-32 weeks | $250K-$400K |
| Monthly running costs (carrier data via project44/FourKites, hosting, EDI (the standard electronic format for swapping shipping documents), SMS) | ongoing | $500-$2K/month for data feeds, plus infrastructure |
The range inside each tier moves with integration count, mode coverage, and how many countries' customs systems you touch. A domestic trucking brokerage and an ocean-freight forwarder share the word freight and almost nothing else in the build.
Brokerage load boards sit at the lower end of the MVP band ($50K to $100K). Forwarding operations cores sit lower still on engineering but higher on integration risk ($40K to $90K). Visibility MVPs start higher ($80K to $120K) because the milestone data model is the product, not a feature.
Who actually builds freight software
Four kinds of operation reach for a custom build:
Growing brokers outrunning phones and spreadsheets. A traditional brokerage where every increment of volume means another dispatcher hire. The trigger is coverage: the team cannot cover more loads by hand, and public load-board fees plus margin leakage have become a monthly number.
Mid-size forwarders and NVOCCs (carriers that sell container space without owning the ships). They typically move 50 to 500 shipments a month and pay per-shipment platform fees that scale with volume instead of flattening. Or they work a niche mode or lane (reefer - refrigerated containers - project cargo, dangerous goods) that the standard platform handles badly.
3PLs needing a client-facing layer. They already run a TMS (transport management system - the software that runs their day-to-day freight operations) for internal operations. What they lack is a clean portal for the brand owner asking when their product arrives. A custom client layer on top of the existing TMS, without replacing it.
Importers and digital-first operators. Importers moving 500+ containers a year across multiple forwarders who need one dashboard instead of four portals and a spreadsheet. And technology companies building logistics SaaS, for whom the platform is the product, not an internal tool.
If a standard TMS fits how you move freight and the fees stay reasonable, stay on it. The build is for operators whose volume or differentiation has outgrown the standard.
How freight software actually works
Three mechanisms do the real work. Everything else is screens around them.
Matching is about acceptance, not generation. A load board that lists freight is trivial to build. The product is the recommendation a carrier actually accepts. That means modeling each carrier's preferred lanes, equipment type, and rate history, then ranking loads against that profile. A dispatcher-assisted version has a human approve each match, which is where most builds start. A fully automated version books instantly when the score clears a threshold. The mistake is optimizing for generating matches instead of accepted ones. A recommendation the carrier rejects because it ignores their lanes and rates is worse than no recommendation, because it trains carriers to ignore the system.
Milestones are the data model. A standard ocean shipment moves through 17 to 22 events. Booking confirmed, cargo packed, container picked up, arrived at origin port, customs cleared, vessel departed, arrived at destination port, customs cleared at destination, drayage (the short truck trip from port to warehouse) assigned, delivered. Each milestone carries a planned date set at booking and an actual date recorded when the event happens. Every alert, every status display, every analytics query derives from this schema (the fixed structure that defines what each shipment record holds). Get it wrong and everything built on top is wrong. Importers do not watch dashboards. They respond to exceptions, the milestone that did not happen on time. Build the alerting before the dashboard.
Documents are versioned records. A bill of lading gets amended after it is issued. Cargo details change, consignees change, and the document must carry that history. File storage cannot do this. Neither can a folder of PDFs. The shipment file is the center of gravity: one record every role can see, with quotes, bookings, and documents as versioned entries inside it. Customs filings (US AES, America's export filing system; EU ICS2, Europe's import filing system; the UK regime) each demand their own data formats and deadlines, so "customs integration" is really a per-country program, not a single feature.
Carrier data itself is a solved input. Project44 and FourKites normalize the inconsistent event formats, timestamp conventions, and latencies of dozens of carriers into one API at $500 to $2K per month. Without an aggregator, you build six to eight separate carrier integrations and add three to four months. The aggregator feeds your milestone model. It does not replace it.
This is the teardown we run in discovery before we ever quote you. If a vendor cannot explain how matching, milestones, and documents should work for your freight model, they have not thought about your product yet.
Where the budget actually goes
You are building a data platform with three faces: operations, carriers, and customers. Typical budget split for a single-model MVP:
| Build area | Share of budget | What it includes |
|---|---|---|
| Shipment data model and backend | 30-40% | Milestone schema, shipment file, document versioning, database, API layer |
| Integrations | 20-30% | Carrier APIs or aggregator, EDI feeds, ERP (the company's main business system) or accounting sync, customs filing connections |
| Operations web platform | 15-20% | Dispatcher or forwarder workflows, load board, booking, exception management |
| Client or carrier portal | 10-15% | Branded tracking portal, self-serve status, document downloads |
| Carrier mobile app (V2) | 10-15% | Self-serve booking, live location, document capture |
The backend and the integrations together are more than half the budget because freight software is a data-integration product wearing an app interface. Teams that budget the screens carefully and treat integration as an afterthought rebuild in year two.
What drives the price up or down
Integration count. Carrier bookings and milestone events, EDI trading-partner feeds, ERP sync: each integration fails in ways a sandbox (a test copy of the system) never shows. On a typical build, integration work is the largest single cost and the most common cause of a schedule slip. Scope every integration in discovery and prototype the riskiest one in the first sprint.
Mode and lane coverage. One mode (trucking, or ocean, or air) to start. Each additional mode adds carrier integrations, document types, and milestone definitions. Multi-mode is a V3 feature, not a V1 feature.
Customs country count. Each country's filing system is a separate integration with its own data requirements and maintenance burden. A forwarder on US-EU-UK lanes needs three before the software is usable. Scope country by country.
Carrier mobile app. A dispatcher-facing web platform covers V1. The carrier app for self-serve booking and live location is a V2 product with its own offline, battery, and location-permission complexity.
Payments and quick-pay. Moving money (carrier payouts, quick-pay fees, factoring) carries fraud, reconciliation, and compliance weight of its own. It deserves a dedicated phase, never a V1 checkbox.
Pricing engine timing. Dynamic pricing with no lane-rate history behind it produces confident, wrong numbers. Build the data collection first, the engine second.
V1, V2, V3: what to build and when
One freight model done well is the MVP. Everything else is V2 or V3.
Feature priority by version
V1
Launch ($40K-$100K, 10-16 weeks)
One freight model, done well. The operational core your team runs on.
- Brokerage: load posting, carrier onboarding with authority and insurance checks, assisted matching, rate entry
- Forwarding: shipment file, quotes, bookings, versioned core documents, one mode
- Visibility: milestone data model, one carrier data feed, exception alerts, ops dashboard
V2
Growth (add post-launch, +$30K-$80K)
Add these once the core is trusted and real volume is flowing through it.
- Carrier mobile app with self-serve booking and document capture
- Branded client portal with self-serve tracking
- Automated matching tuned on acceptance data
- EDI with key trading partners and ERP sync
- Demurrage and detention clock with pre-expiry alerts
V3
Scale (add at volume, +$40K-$120K)
Automation and monetization features that pay for themselves only at scale.
- Dynamic pricing engine on real lane-rate history
- In-platform payments with quick-pay or factoring
- Customs filing integrations per country
- Multi-mode support and automated freight audit
- Multi-tenant SaaS with white-labeling and API layer
The demurrage clock deserves a word. Free time at the port is a clock, and missing it lands a fee on the invoice weeks later, past easy dispute. A tracker that alerts before free time expires prevents fees instead of reconciling them. It is unglamorous, often the fastest ROI in the build, and easy to defer. Do not defer it.
How the timeline breaks down
| Phase | Duration | What happens |
|---|---|---|
| Discovery and data modeling | 2-3 weeks | Freight model selection, milestone schema design, integration mapping, customs country scoping |
| Operational core | 8-12 weeks | Shipment file, load board or booking flows, document versioning, roles; built in parallel with integrations |
| Integrations | 4-6 weeks | Carrier data feed, EDI partners, ERP sync; the long pole alongside the core |
| Hardening and migration | 2-3 weeks | Real trading-partner data, document edge cases, historical shipment migration |
| Beta with live freight | 2-4 weeks | Real shipments on the platform before full cutover |
Total: 10 to 16 weeks to a single-model MVP beta. Integrations are almost always the long pole. Any vendor promising 6 weeks is quoting the screens, not the platform.
The tech stack, without the sales pitch
Backend: Node.js (the server-side code) with PostgreSQL (the database) for the shipment and milestone data model, Redis for event caching (a fast temporary store that keeps recent shipment updates close at hand). The milestone schema is the most important design decision in the build. Spend the first two to three weeks on it before writing application code.
Carrier data: Project44 or FourKites through one API ($500-$2K/month) instead of six to eight separate carrier integrations. Non-negotiable past two carriers.
Documents: Versioned records in the database with PDFs on S3 (Amazon's file storage) linked to each shipment record, role-based access by user type. Not file storage.
Frontend: React for the ops dashboard and client portal. Cross-platform mobile for the carrier app in V2.
Notifications: Email and SMS for milestone exceptions and demurrage alerts. Push for the carrier app. The alerting layer matters more than any dashboard.
The business math
Three thresholds decide build vs. buy:
The TMS fee threshold. When your platform subscription plus per-shipment and integration fees cross roughly $40K to $60K per year, an owned platform built once for $90K to $160K pays back inside a year for most mid-size forwarders and keeps paying every year after. Below that, stay on the platform.
The Flexport margin threshold. Flexport charges 3 to 8% on every shipment. On $10M in annual freight, that is $300K to $800K per year. A $160K custom platform pays back in under eight months. The honest cutoff is around $5M in annual freight. Below $3M, the build cost does not close.
The coverage threshold. When brokerage volume outgrows what dispatchers can cover by phone and public load-board fees plus margin leakage become a monthly number, automation replaces headcount you would otherwise add with every increment of volume. An owned platform pays back on the coverage cost alone.
Model the decision on your fees and volume, not on features. The platform you rent charges for exactly the thing you are trying to grow.
Where freight builds go wrong
Underscoping the integrations. Teams budget the freight logic carefully and treat carrier and EDI integration as an afterthought. It is the opposite: integration is the largest single cost and the most common cause of a schedule slip. Scope it first.
Treating documents as file storage. A bill of lading gets amended after it is issued. If the system stores a PDF instead of a versioned record, the history is lost the moment cargo details change.
Building visibility before the data model is right. Milestone tracking is only as good as the shipment and container model underneath it. Rush the tracking screen before the model is clean and you rebuild both.
Optimizing match generation over match acceptance. Recommending loads is easy. Recommending loads a carrier takes is the hard part. A rejected recommendation trains carriers to ignore the system.
Bolting payments onto V1. Quick-pay and factoring carry their own risk, reconciliation, and compliance weight. They deserve a dedicated phase.
Ignoring the demurrage clock. Free-time tracking is unglamorous and easy to defer, and it is often the fastest payback in the build.
Carrier vetting: the fraud question that decides trust
A freight platform matches shippers with carriers it has never met, moving cargo worth tens of thousands of dollars. Carrier fraud, double brokering, identity theft, and cargo theft are the industry's open secret, and the vetting system is the product's immune system.
Verify operating authority and DOT registration (DOT is the US Department of Transportation) against the federal database, not self-reported forms, and weigh how long the authority has been active: new authority is the highest-risk segment. Verify insurance directly with the insurer, because certificates are trivially forged and policies lapse. Watch for double-brokering signals: equipment at pickup that does not match the dispatched carrier, impossible routes in tracking data, carriers who only text and never answer. Then keep watching, because authority status, insurance currency, and safety ratings change continuously, and automatic suspension triggers beat quarterly reviews.
One cargo theft traced to a carrier the platform failed to vet undoes a year of sales work. Shippers choose freight platforms on trust, and trust is the vetting system working when nobody is looking.
Two 2026 enforcement items belong in the vetting checklist. Since 16 March 2026, non-domiciled CDLs (commercial driving licences held by drivers living outside the US) go only to drivers in H-2A, H-2B, or E-2 status (temporary work-visa categories). So verify non-domiciled CDL status under the March 2026 rule and check Training Provider Registry provenance (confirm their training came from a federally approved provider). English-language proficiency failure is now an out-of-service violation at roadside, so check English-proficiency standing too. Treat Dalilah's Law (H.R. 5688) as pending legislation, not law: it passed a House committee in March 2026 and has not become law.
Off-the-shelf TMS vs. custom build
| Off-the-shelf TMS | Custom build | |
|---|---|---|
| Upfront cost | Subscription + per-shipment fees | $40K-$220K |
| Time to value | Weeks | 10-28 weeks |
| Custom matching or workflows | Workarounds | Built to spec |
| Carrier and EDI integrations | Vendor's roadmap | Your priority order |
| Customer portal differentiation | Same portal as every competitor on the platform | Branded, yours |
| Data ownership | Vendor holds it | You hold it |
| Total cost at 3 years | Scales with volume, forever | Build once, run at infrastructure cost |
The TMS wins when it fits how you move freight and the fees stay reasonable. Custom wins when the fees scale with your growth, when workarounds pile up, or when the matching, portal, or data itself is the differentiation. Most operators who build do it at the $40K to $60K per year fee threshold, not before.
Does this cover Uber Freight, Flexport, and CargoWise?
Yes. The three leaders map to the three freight models this guide consolidates, and the cost bands apply across all of them.
| Company | Model | What differs |
|---|---|---|
| Uber Freight | Digital freight brokerage | Load board plus managed transportation; the matching engine and carrier app are the product |
| Flexport | End-to-end forwarding with PO-level visibility | The milestone model and client portal are the product. Since October 2026 outside AI agents can search rates, track shipments, and book freight through Flexport's MCP server (a standard connection for outside AI tools), so a custom platform should plan for agent booking with human exception handling and clear liability for agent-made bookings |
| CargoWise | Forwarding operations system | Deep forwarding execution (WiseTech Global); Value Packs replaced seat (per-user) and transaction licensing in December 2025, with transaction-based charges for forwarding, customs, warehousing, and land transport, and advanced AI agents may be charged separately |
| Project44 / FourKites | Freight data aggregators | Not platforms. The $500-$2K/month data feed your custom platform consumes instead of building carrier integrations |
If you are building for one of these models, the cost bands in this guide apply. The budget moves with integration count, mode coverage, and customs country count, not with which logo you benchmark against.
Market context from Q3 2026: national van contract linehaul (the long-distance trucking leg, priced under contract) ran $2.39 per mile in July, up 18% year on year. Spot linehaul (the same leg booked on the day at the current market rate) was $2.21 per mile by late August, up 35.6%. Diesel ran $5.652 per gallon in the week of 24 August, up 52.4%, and primary tender acceptance (the share of offered loads carriers agree to take) recovered to 78% in August. Rates and fuel remain well above year-ago levels even after easing from July peaks.
How RaftLabs approaches freight builds
We scope one freight model for V1 at 10 to 16 weeks: the operational core your team runs on, with the milestone data model designed before any application code. Integrations are mapped in discovery and the riskiest one is prototyped in the first sprint, because that is where freight builds slip. Carrier onboarding and compliance are scoped as first-class work, matching is built around acceptance rather than generation, and documents are versioned records from day one.
The freight architecture shares its foundation with the matching, tracking, and payments layers we build across logistics. We do not charge you for the learning curve.
If you are running freight on spreadsheets and phone calls past the point where the math works, or paying platform fees that scale with the volume you are trying to grow, here is the first 90 days: two to three weeks of discovery to nail the freight model, milestone schema, and integration map, then 10 to 14 weeks of development to your first beta running live freight. Start your scope and we will tell you what belongs in V1 and what does not.
Ask an AI
Get an instant summary of this post from your preferred AI assistant.
Frequently asked questions
Straight answers to what buyers ask before they scope. Still stuck? .
- A single-model freight MVP (the smallest working version) costs $40K to $100K over 10 to 16 weeks. A brokerage load board with carrier onboarding and assisted matching runs $50K to $100K. A forwarding operations core with quotes, bookings, and documents runs $40K to $90K. A visibility MVP with milestone tracking and one carrier data feed runs $80K to $120K. A full platform combining automated matching, multi-carrier tracking, document versioning, and a client portal runs $90K to $220K over 16 to 28 weeks.
- A freight brokerage matches shippers' loads with carriers' trucks and earns the spread between the two rates. Uber Freight is the model. A freight forwarder arranges international shipments end to end, handling bookings, documents, and customs across ocean, air, and land. CargoWise is the established software. A freight management platform is the visibility and operations layer on top: milestone tracking, exception alerts, document management, and a branded client portal. Flexport is the model. Many operators blend two of the three, but each has a different way of organising records at its centre, which is why this guide treats them as one category with three variants.
- A single-model MVP ships in 10 to 16 weeks. A full platform with automated matching, multi-carrier tracking, and a client portal takes 16 to 28 weeks. A multi-tenant SaaS version (one system serving separate customer companies) with white-labelling (sold under your brand) and an API layer (connections other software can use) takes 24 to 32 weeks. The timeline depends most on integration count (carrier APIs, EDI feeds, ERP sync) and how clean your data is, not on the number of screens.
- The load board is the easy part. The hard part is match acceptance: recommending loads a carrier will actually take. That means modeling each carrier's preferred lanes, equipment type, and rate history, then ranking loads against that profile. A dispatcher-assisted version has a human approve each match. A fully automated version books instantly when the score clears a threshold. Most builds start assisted and automate once the acceptance data proves the model.
- Through a freight data aggregator. Project44 and FourKites pull real-time tracking events from ocean carriers, airlines, rail, and trucking through a single API (one connection) at $500 to $2K per month. Without one, you build separate integrations for each carrier, which adds three to four months. The aggregator handles the data feed. Your platform still needs its own milestone data model to turn those raw events into planned-vs-actual tracking and exception alerts.
- Budget $500 to $2K per month for the carrier data feed through project44 or FourKites, plus hosting, EDI transaction fees (charges for exchanging shipment data in the standard format), and SMS or messaging costs. The data feed is the largest fixed line. EDI fees scale with trading-partner count. Everything else scales with shipment volume.
- Building beats a TMS subscription when the platform's subscription plus per-shipment and integration fees cross roughly $40K to $60K per year, or when the platform forces workarounds for how you actually move freight. Building beats the Flexport API when you move $5M or more in annual freight at 3 to 8% margin. On $10M in freight, Flexport's fee runs $300K to $800K per year, and a $160K custom platform pays back in under eight months. Below those thresholds, buying is usually the better call.
- The software generates, versions, and routes the documents behind a customs entry: bill of lading, commercial invoice, packing list, and certificate of origin. Because bills of lading get amended after issue, documents must be versioned records, not files in a folder. Filing itself usually stays with your licensed customs broker per country; the software owns the document and data workflow and tracks filing status through a broker collaboration model. Each country's filing system (US AES, EU ICS2, UK post-Brexit regime) is a separate integration.
- Not in the first version (V1). A dispatcher-facing web platform covers load posting, matching, and tracking for the operations team. The carrier mobile app matters in the second version (V2), when carriers self-serve booking, upload documents, and share live location. For forwarding and visibility builds, the client portal usually comes before any mobile app. Build the web platform first and add mobile once the data model is proven.
- With a vetting system, not a signup form. Verify operating authority and DOT registration (the US Department of Transportation's carrier register) against the federal database, check how long the authority has been active, and verify insurance directly with the insurer rather than trusting uploaded certificates. Watch for double-brokering signals (signs a load was passed to another carrier without approval): equipment at pickup that does not match the dispatched carrier, impossible routes in tracking data, and carriers who only text. Then keep monitoring continuously, because authority status, insurance, and safety ratings change. One cargo theft traced to an unvetted carrier undoes a year of sales work.
