The redeploy kit — one stack, ten industries
Stage 7 · Platform Engines
Four-Lane View
Software Function
- ›The five engines as configurable modules: credentialing, matching, rating, settlement, document automation Industry config packs: nurse licenses vs CDLs, shift matching vs load matching — 20% of original build cost per the deck Multi-tenant architecture decisions made NOW (Stage 1–6) so the redeploy is configuration, not rewrite
Service Provider / Admin
- ›Platform team owns the abstraction line: freight features vs platform features tagged from day one Expansion gates enforced: FMCSA licence, 200 vetted carriers, 95% coverage before anything else (the deck’s discipline)
User — Driver / IOO
- ›Freight-side users feel nothing — the wedge stays sharp
Customer — Client / FF / NVOCC
- ›Future two-sided markets (3PL, construction, staffing) inherit proven trust rails: verified identity, CLIENT/FF/NVOCC transparent fees, 7-day pay
Software Function
- ›The five engines as configurable modules: credentialing, matching, rating, settlement, document automation Industry config packs: nurse licenses vs CDLs, shift matching vs load matching — 20% of original build cost per the deck Multi-tenant architecture decisions made NOW (Stage 1–6) so the redeploy is configuration, not rewrite
Competitors
Uber (rides→eats→freight proved the pattern), Amazon (books→everything), vertical SaaS that never abstracted and died niche
Differentiation
The $1,544B thesis lives or dies on whether Stage 1–6 code was built as one infrastructure layer. This "function" is an architecture mandate, not a feature.
Make It Better
Industry #2 (supply chain/3PL, Year 2–3) launches at 20% of freight’s build cost — the proof the platform capture table ($12B–$278B) rests on. APPENDIX Original requirements checklist — MC’s notes The founder’s outline, kept verbatim and mapped to the build. ✓ covered · ⟳ iterate · ☐ open. This checklist is live in the mapping tool’s right-side panel. ✓ Build mapping This tool ✓ Create driver data Stage 1 Create functionality in each area a driver interacts ✓ Drayage — import/export Stage 2 ✓ OTR Stage 3 ✓ Intermodal Stage 3 ✓ LTL Stage 3 ✓ Conversely create admin functionality vs. driver All stages ✓ Port / Customer information Stage 2 ✓ Audience: clients / Freight Forwarders / NVOCC’s / importer-exporter, all commodities Stage 2 · Stage 3 ✓ Dispatching Stage 2 · Stage 3 ✓ Communication Stage 4 ✓ Routing Stage 2 · Stage 3 ✓ Productivity Stage 4 ✓ Service standards Stage 4 ✓ Analyzation / Refinement / Efficiency Stage 6 Warehouse Stage 5 ✓ Space availability Stage 5 ✓ Service Stage 5 ✓ Transloading Stage 5 ✓ Distribution Stage 5 ✓ Pick/Pack and Ship Stage 5 ✓ Storage Stage 5 ✓ Value-added labor services: hand off load · forklift · clamp · palletization · shrink wrap/banded · labeled Stage 5 ✓ Inbound receipt Stage 5 ✓ Inventory at staging Stage 5 ✓ Decision tree based on client expectations Stage 5 ✓ Put away FIFO/LIFO Stage 5 ✓ Pick FIFO/LIFO Stage 5 ✓ Outbound staging Stage 5 ✓ Pickup confirmation Stage 5 ✓ Signed BOL Stage 5 ✓ Office and client communication Stage 5 ✓ Inventory reconciliation Stage 5 ✓ Mapping tool: input form — software function · service provider function · user view · customer view; competitors + differentiation This tool ✓ Start with the most simplistic functionality: driver recruitment & compliance to onboard IOOs to us as service provider Stage 1