Skip to content
Yusuf Mohammed-Ali
WorkAboutContact
Lagos --:--, GMT+1Résumé

© 2026 Yusuf Mohammed-Ali

  • LinkedIn
  • Contra
  • Behance
  • Dribbble
  • Résumé
All work

PNLHub

Designing both sides of a logistics marketplace

Role
Product Designer
Timeline
2 months
Platform
Shipper app / Transporter app
Status
Live site

Chapters

  1. 01Thinking
  2. 02The opportunity
  3. 03Constraints
  4. 04The job to be done
  5. 05The decision
  6. 06Priority
  7. 07Learnings

PNLHub connects people who need goods moved with transporters who have the trucks. I designed both web apps, the shipper's and the transporter's, as an MVP in two months, so a single shipment could be created, bid on, agreed and tracked from either side.

Transporting CompanyTheir BidStatusYour Amount
GFGood Fellas Inc.New Bid • Just now
$120
New Bid
$45
AcceptBargainReject
SLSwift LogisticsCounter Offer • 4 mins ago
$520-$20 from $540
Negotiating
$95
AcceptBargainReject
RTRapid Transport Co.Awaiting response • 5 minutes ago
$328
Counter Sent
$145+$100 from $45
AcceptBargainReject
EFExpress Freight ServicesPending confirmation • 22 min ago
$230
Accepted
$45
ConfirmReject
PHPinnacle HaulersNew Bid • 2 hours ago
$380
New Bid
$45
AcceptBargainReject
NCNimble Cargo SolutionsAwaiting response • 7 minutes ago
$120
Counter Sent
$100+$65 from $45
AcceptBargainReject
ADApex Delivery GroupCounter Offer • 4 mins ago
$709-$100 from $809
Negotiating
$45
AcceptBargainReject
New Bargaining Bid from Good Fellas Inc.$120 • Just Now

01 / Thinking

One shipment, two completely different users.

The goal was to help shippers get a load moved, and transporters find work that fits their trucks, inside one product. Both web apps shipped as an MVP in two months.

02 / The opportunity

One transaction, seen from opposite ends.

Moving goods takes two parties: someone who needs something moved, and someone with a vehicle to move it. The MVP brief brought the whole transaction into one platform: creating a shipment, discovering transporters, bidding and negotiating, tracking, notifications and ratings.

The opportunity wasn't two dashboards. It was one transaction that two people see from opposite ends.

03 / Constraints

Status, not GPS.

The minimum a transporter needs before bidding (size, weight, pickup and destination) set the shipment form. Tracking in the MVP was status-based rather than live GPS, so three states, Booked, In transit and Delivered, had to feel trustworthy without a map. Escrow payments, route optimisation and AI matching were deliberately left out of the MVP.

Shipment detail, In transit: delivery progress told through status
Shipment detail, In transit: delivery progress told through status

04 / The job to be done

Shipper

“When I have goods to move, I want to post the job once and choose a transporter I trust, so I'm not chasing drivers by phone.”

Transporter

“When my truck is free, I want to find loads that fit it and agree a fair price fast, so I'm not driving empty.”

  1. 01

    How might we make it simple for shippers to create and manage transport requests?

  2. 02

    How might we help transporters discover relevant shipments and manage the deliveries they accept?

  3. 03

    How might we make both sides feel like one connected transaction?

05 / The decision

Bid, bargain, accept.

The shipped flow mirrors itself on each side, so a bid always means the same thing to both people.

TransporterView shipmentPlace quoteMonitor bid statusBargain or accept
ShipperView shipmentReview active bidsAccept, bargain or reject
Create shipment: only what a transporter needs before bidding
Create shipment: only what a transporter needs before bidding
Payment successful: the agreed price closes the loop
Payment successful: the agreed price closes the loop

06 / Priority

What shipped, and what waited.

Shipped in the MVP

  • Shipment creation
  • Shipment marketplace for transporters
  • Bidding and negotiation
  • Status tracking, Booked to Delivered
  • Transaction history on both sides

Next

  • Real-time tracking and route optimisation
  • AI shipment matching and pricing
  • In-app payments and escrow
  • Analytics and reporting
  • Support and dispute resolution

07 / Learnings

  1. 01

    Design systems, not screens.

    The same shipment looks different depending on who's holding it. A shipper creates, evaluates and monitors it; a transporter discovers, bids for and delivers it.

  2. 02

    States are the shared language.

    Booked, In transit and Delivered had to mean the same thing in both apps.

  3. 03

    Two interfaces, one product.

    The hard part wasn't designing two apps. It was making them behave as one.

More screens

Transporter dashboard: earnings, deliveries and recent shipments
Transporter dashboard: earnings, deliveries and recent shipments
My Bids: every quote a transporter has placed, ready to accept or bargain
My Bids: every quote a transporter has placed, ready to accept or bargain
Place your Quote: the transporter names a price against the shipper's offer
Place your Quote: the transporter names a price against the shipper's offer

Next case study

All work
TimeSwaprA time bank that lets neighbours trade an hour of help for an hour of help