Northwind Freight (mock) · 2024

Northwind Freight

Mock case study. Details and metrics are placeholders and should be replaced with real client-approved language before launch.

Context

Northwind’s quoting process worked—until volume increased. Pricing lived in multiple spreadsheets, new edge cases were handled ad-hoc, and the “source of truth” changed weekly.

What we did

• Defined the object model: lanes, accessorials, constraints, and exceptions.
• Designed for auditability: every quote needed a reason you could read later.
• Built an ops-first UI: speed of entry mattered more than visual polish.
• Added guardrails: validation, sane defaults, and explicit override reasons.

Outcomes (placeholders)

• Quote turnaround improved by 25–40%.
• Manual overrides reduced by 15–25%.
• Fewer “pricing mysteries” because the rules were visible and versioned.

What we’d do next

• Integrate carrier performance data.
• Add scenario testing for upcoming rate changes.

Outcomes

• Reduced quote turnaround time (placeholder: -25% to -40%)
• Fewer manual overrides (placeholder: -15% to -25%)
• Created a shared pricing language across sales + ops