FreightFlow
A web TMS that turns documents, loads, invoices, and settlements into one flow.
About project
FreightFlow: one system from document to settlement.
All-in-one trucking system for carriers.
TL;DR
01
Challenge
Create loads fast without manual retyping.
02
Approach
Design around roles and status-driven work.
03
Solution
Loads, invoices, settlements, dashboards, extraction.
04
Outcome
Faster operations measured via safe success proxies.
The product in real life
A dispatcher opens FreightFlow right after a new shipment comes in. They create a load, confirm stops, and keep updates attached to the trip. Later, accounting turns completed work into invoices and monitors what is unpaid. Meanwhile, a manager checks a quick dashboard snapshot to spot capacity gaps early.
When work starts
to feel heavy
In trucking ops, small delays compound fast. One missing field becomes a late pickup, then a late invoice, then a settlement dispute. The work is not hard once - it is hard dozens of times a day, under time pressure.
Pain behaviors
- Retype fields from documents
- Chase updates across notes and messages
- Scan tables to find urgent invoices
- Rebuild settlements after expense changes
- Double-check dashboards, then open spreadsheets
What we
noticed early
Insights
- Work starts from documents, not dashboards
- Statuses are the language of ops and finance
- Loads behave like moving checklists: stops, notes, exceptions.
- Finance needs queues to keep cash flow visible
Our approach
We designed around real operational moments instead of isolated screens: starting a load from a document, executing stops, and closing cash flow. From those scenarios, we shaped flows and a status spine that keeps work predictable.
Work ran with visible checkpoints: structure first, then key flows, then UI foundations, then high-fidelity screens and implementation notes. This cadence reduced ambiguity and prevented rework during build.
Key improvements
5 chapters
Create loads from PDFs
01
Situation
A new shipment arrives as a rate confirmation document, and the clock starts.
02
Change
FreightFlow starts with document upload, then extracts key fields into the load form. Users review, correct, and submit without retyping everything.
03
Result
Loads are created faster with fewer manual fields.
Run a load in one place
01
Situation
While a truck is moving, details change: stops shift, notes appear, exceptions happen.
02
Change
Loads management combines map visibility, stop tracking, and notes/events into a single workspace.
03
Result
Exceptions are resolved faster because updates stay in one workspace.
Treat invoices like a queue
01
Situation
Accounting needs to know what to send,
what’s blocked, and what’s paid.
02
Change
Invoices are designed as an action queue with status chips, filtering, and export for fast scanning.
03
Result
Accounting instantly sees what needs action next.
Close settlements with confidence
01
Situation
Settlements combine pay, fuel, and extras;
inconsistencies cause back-and-forth.
02
Change
Settlement becomes a dedicated workspace with totals, transactions, and related loads, plus export/send.
03
Result
Settlements close with fewer revisions and clarifications.
Spot issues in a glance
01
Situation
Leaders need an instant pulse without building reports.
02
Change
Dashboard surfaces signals like unpaid invoices, capacity, and revenue trend for quick checks that prompt
03
Result
Managers spot capacity and cash-flow risks earlier.
Feature Spotlight
FreightFlow's hero moment is turning a rate confirmation document into a workable load. Upload the document, extract key fields, review stops and details, then submit. The flow reduces startup friction while keeping humans in control where accuracy matters.
Navigation & information shape
Navigation mirrors intent: dispatch work, load execution, finance operations, then reporting - each as a stable "home" with predictable tables and filters. The hierarchy supports fast decisions by keeping status, ownership, and next actions visible in the same places across modules.
The system behind
the screens
FreightFlow was designed to scale through a consistent UI system: reusable components, table patterns, and clear state handling. Status chips standardize how work moves across loads, invoices, and settlements. Shared tokens (typography, color, spacing) and component variants reduce one-off solutions and help prevent regressions as modules expand.
Validation
& Risk control
For a new ops-heavy product, the main risk is misunderstanding states and edge cases. We treated clarity and controllability as first-class requirements and validated flows through scenario walkthroughs.
01
Scenario
walkthroughs by role
02
Edge-state coverage (empty/loading/error)
03
Component state
review before handoff
Handoff &
implementation
To reduce developer back-and-forth, we packaged the work around reusable patterns and explicit states. Core workflows were designed responsively and documented with consistent component behaviors, making implementation and future modules faster and safer.
01
Information architecture
Map and hierarchy.
02
UI foundations
Typography and color tokens.
03
Component library
Variants and states.
04
Interaction notes
High-fidelity responsive screens for core flows
What changed
- Work starts from document upload, not retyping.
- Loads run in one workspace with stops and notes.
- Invoices become a status-driven action queue.
- Rebuild settlements after expense changes
- Settlements export cleanly with fewer revisions.
Got a project in mind?
Let’s make it happen!
- We review your request right away
- We’ll share case studies relevant to your industry
- If we’re the right match, you’ll get a custom proposal
- Then, we’ll start with a 3-day trial to get the ball rolling