Software Build Specification
Seven Stages.
One Operating System.
FreightShift begins by recruiting and activating independent owner-operators, then builds the operating infrastructure required to control drayage, domestic transportation, warehouse execution, analytics, finance, and platform expansion.
Canonical Business Metrics
Canonical model assumptions — not current production performance.
$2,100
Average GMV / load
30%
Total take
$630
Net revenue / load
7-day
Carrier pay
+$53K
Per tractor / year in the loop
The Seven-Stage Roadmap
Investor view — milestones, moats, sequence
Stage 1
Initial MVPDriver Recruitment & Compliance
IOO Onboarding
Apply → verified → insured → contracted → first load → paid, in one mobile app, in 48 hours. Today that journey crosses 5 separate vendors (Tenstreet → Highway/RMIS → Foley → Openforce → a load board) and takes 1–3 weeks. Nobody owns the whole funnel. We will.
Stage 2
Core OperationsDispatch & Drayage Operations
Import / Export
Chain the import dray to the domestic reload. Every port TMS stops at the warehouse door; DrayNow starts at the ramp. Nobody dispatches the tractor’s NEXT revenue move. The loop — dray + transload + outbound + empty repo — dispatched as one unit is the moat.
Stage 3
Core OperationsMode Expansion
OTR, Intermodal and LTL
A published, transparent take rate on a mode-agnostic quote. Every marketplace hides its spread; every TMS is mode-siloed. One quote showing truck vs rail+dray vs LTL — with our fee printed on it — is something Uber Freight structurally cannot copy without cannibalizing its spread.
Stage 4
Initial MVPDriver App, Communication & Service Standards
The portable driver workspace
The portable driver workspace. Every driver app today binds the driver to someone else’s account — the fleet’s ELD, the broker’s tracker, the recruiter’s ATS. A driver who leaves loses history, documents, and pay records. Ours travels with the driver — and that is why they never leave.
Stage 5
ExpansionWarehouse & Transload
WMS + VAS
Warehouse + freight in ONE record. WMSs treat cross-dock as a picking shortcut; TMSs treat the dock as a black box. Inbound container → inventory → signed outbound BOL → freight billing in one system of record does not exist anywhere. We own both sides, so only we can build it.
Stage 6
ExpansionAnalytics, Refinement & Efficiency
Control tower & shared market truth
Give data back to the people who generate it. Enterprise visibility costs $100K–$2M/yr and carriers feeding it get nothing. Our drivers see the same market map the shippers see. Self-serve, both-sides intelligence at SMB price is unserved whitespace (SONAR’s $24.99 tier proved the demand).
Stage 7
Future PlatformPlatform Engines
Finance, Audience and Expansion
Monetize the float and the attention without ever charging the driver. Factor their OTHER brokers’ loads at 2.5% (keep ours free), lend against inventory we physically hold, take the audience revenue ($56.5M potential) — engines built on assets incumbents don’t have: the eBOL/GPS chain, the pallet, and daily driver opens.
Stage Connection Story
Every stage creates the data, trust, capacity, or operating control required by the next stage.
Initial MVP Focus
- Stage 1 foundation
- Selected Stage 2 operational functions
- Selected Stage 4 driver experience
- Existing driver + fleet decision-layer prototype
Next Operational Expansion
- Remaining drayage functions
- Shipper and client workflows
- Warehouse seam
- Analytics
Future Platform
- Finance
- Wallet
- Sponsored placement
- Multi-industry redeployment