Contract management — the 1.71× rule in code
Stage 3 · Mode Expansion
P1Core Operations
Four-Lane View
Software Function
- ›Quote-time enforcement: contract pricing (17.5%) blocked unless committed volume ≥1.71× equivalent spot Anchor cap alerts (no client >20% of corridor volume) Rate indexing + accessorial pricing mandatory fields — the deck’s rules as validation logic Contract performance tracking: promised vs tendered volume, auto-renegotiation triggers
Service Provider / Admin
- ›Sales sees WHY a deal is blocked and what volume fixes it Leadership dashboard: contract vs spot mix, margin impact, float exposure per contract (terms feed the working-capital model)
User — Driver / IOO
- ›Contract freight = the committed legs that make loops predictable — visible as "guaranteed week" portions
Customer — Client / FF / NVOCC
- ›Honest contract talks: we show the volume math instead of hiding a spread — anchors get real CLIENT/FF/NVOCC capacity guarantees in return
Software Function
- ›Quote-time enforcement: contract pricing (17.5%) blocked unless committed volume ≥1.71× equivalent spot Anchor cap alerts (no client >20% of corridor volume) Rate indexing + accessorial pricing mandatory fields — the deck’s rules as validation logic Contract performance tracking: promised vs tendered volume, auto-renegotiation triggers
Competitors
Every TMS stores contracts; none enforce deal quality. This is strategy-as-software nobody else has because nobody else published their economics.
Differentiation
The deck’s hardest-won finding (contracts buy volume with margin; 1.71× is the floor) becomes a system constraint — sales literally cannot sign a value-destroying anchor.
Make It Better
Zero contracts signed below break-even volume, ever. The discipline that kills most brokerages is automated away before Series A.