01
Counter
Make the front line easier to run.
The first tools handled real ServicePoint friction: customer translation at the counter and repeatable staff training around shipping judgment.
Mo / a long term operator relationship
The work kept expanding because every useful build made the next bottleneck visible.

The newest public layer
Travelyt


How the relationship moved
Counter
Customer
Operations
Venture
The relationship, organized
01
Counter
The first tools handled real ServicePoint friction: customer translation at the counter and repeatable staff training around shipping judgment.
02
Customer
CubicShip brought services, locations, quotes, orders, account paths, and customer trust into one public system supported by sales and agent workflows.
03
Operations
A private operating hub and freight workflows made active projects, meeting context, quote support, and next actions easier to see across the relationship.
04
New venture
Travelyt became the public product layer, supported by custody diagrams, pilot review material, decision briefs, outreach preparation, and a separate 3D sales prototype.

Why the relationship matters
I was not handed nine briefs. I stayed close enough to understand why the next system needed to exist.
What this proves
JDLO can learn how an operator moves across customer service, sales, internal coordination, logistics, and a new product, then build a connected layer around the work.
Important context
This is a working relationship with Mo across DHL ServicePoint, CubicShip, MEA, and Travelyt contexts. It is not presented as a direct JDLO engagement with DHL corporate. Travelyt review materials are not airline, airport, TSA, or IDEMIA approval.
Need a builder who can stay with the business?