← THE WORK / 01FREIGHT LANE↗

THE WORK.
THE TEAM.
ONE PLACE.

An operations workspace built inside
the department that uses it.

Follow the workflow ↓
ACTUAL APPLICATION / AUG 2026Original Freight Lane mobile application screenshotORIGINAL PRODUCT CAPTURE
LIVE AT D&L TRANSPORT4 DAILY DEPARTMENT USERSPRODUCT CREATOR / OPERATIONS LEADER
01 / OVERVIEW

THE INBOX WASN’T
THE WHOLE PROBLEM.

Shipment requests, documents, carrier updates and team conversations were scattered. Faster email alone would still leave people putting the case back together.

I created Freight Lane to put the request, its context, the team and the next action in one workspace.

03 / SOLUTION & PROCESS

FOLLOW
THE WORK.

ILLUSTRATIVE WORKFLOW
REQUEST → CONTEXT → ACTION
REQUESTShipment + intent
THE CASEFacts / files / conversation
THE TEAMJudgment + ownership
SCENE 01

Start with the request.

A shipment request enters the shared inbox. The work begins with what the person actually needs—not a disconnected email automation.

4PEOPLE.
EVERY DAY.
04 / OUTCOME & CURRENT STATUS

Built by someone
who stays in the work.

Freight Lane is used daily by me, two LTL team members and the Director of Pricing. Built for our department’s daily work.

Product use reported by Bryan, October 2026.
02 / CHALLENGE — A DETAIL FROM DAILY USE

A missing document
shouldn’t stop
the wrong task.

A pickup or tracking request should not be held up by a missing bill of lading when that document is unnecessary. I made sure each request asks for the documents it actually needs and keeps the team in control.

My role: I conceived the product, designed workflows, directed implementation with AI tools, tested requests, led rollout and defined AI authority and human takeover.

Have something that should work better?
Let’s build
what’s next.↗
zelljones40@gmail.com ↗

Based in Raymore, Missouri.
Open to collaboration & remote leadership roles.