Loadpilot v2
A narrow TMS for solo freight brokers handling fewer than 50 loads a week that joins shipper requirements, carrier identity and authority evidence, rate confirmation, approved dispatch, check calls, delivery documents, invoicing, and correction without declaring any carrier safe or legitimate by score.
Solo freight brokers can be underserved between spreadsheets and larger transportation systems. They coordinate shipper requirements, carrier sourcing, identity and authority checks, rates, dispatch, status, documents, delivery, and invoicing across calls, email, portals, and load boards. The supplied research corrects a freight-automation funding claim from $85 million to $26 million, confirms an existing SMB-accessible TMS, finds no confirmed AI-native solo-broker product in the proposed band, and says the named open-source substrate was not independently verified. Loadpilot v2 therefore preserves the solo-broker opportunity but treats the code substrate and every integration as build gates. It assembles an evidence packet for each carrier and load, highlights discrepancies, drafts a rate confirmation and dispatch message, and requires broker approval before booking or sending. Identity, operating authority, insurance evidence, watchlists, contact verification, shipper approval, rate acceptance, tender, carrier acknowledgment, pickup, in-transit status, delivery, proof of delivery, invoice, settlement, claim, and correction remain distinct. A carrier match or authority snapshot never certifies safety, legitimacy, insurance applicability, performance, or fraud absence. The original stage referenced one API and verified none. The product cannot autonomously select a carrier, bind a contract, tender a load, change a rate, impersonate a broker, or represent destination readback it did not receive.
A solo freight broker or very small brokerage operating fewer than 50 loads per week and currently coordinating dispatch through email, calls, portals, and spreadsheets.
The solo broker, weekly load ceiling, current alternatives, and proposed band are unusually specific.
Current freight automation investment and SMB tooling support a timely test after correcting the funding figure.
The record shows a segment gap but not a clearly broken technical or distribution barrier.
A sharply defined solo-broker segment, several supplied market signals, an SMB gap, and a narrow dispatch workflow support the development.
The fork substrate was not independently confirmed, the original API was unverified, carrier evidence is high-stakes, direct SMB systems exist, and pure self-serve economics remain unproven.
Discussion
No comments yet — be the first to weigh in.
