CargoEZ · Mobile freight CRM

Bringing a freight CRM to mobile.

Designing a mobile workspace where freight-forwarding teams can capture contacts, build leads, manage quotations, and move opportunities toward shipment without being tied to a laptop.

Role

Sole Product Designer

Tools

Figma

Duration

3 Months

platofrm

Android & IOS

The Problem

The tool wasn’t missing. The desk was.

Freight-forwarding agents often work away from their laptops: meeting customers, collecting new opportunities, following up, and coordinating shipment details. But critical work still depended on the desktop.

Before

New contact → Notes / WhatsApp

New lead → Desktop

Lead updates → Desktop

Vendor estimates → Desktop

Documents → Desktop

After

Mobile workspace

Capture the important detail while the conversation is still happening and keep the opportunity moving.

The opportunity wasn’t simply to create another mobile app. It was to decide what needed to be accessible now, what could wait, and how to make a complex desktop workflow usable on a phone.

Bessie Cooper
SFO → LGP
call Mon?? check rate

Before: Manual notes / what's app notes

After: Save Contact, generate Lead Instantly.

Research

Finding what actually needed to move to mobile

I interviewed five freight forwarding agents, relationship managers, and operations staff using a predefined set of research questions. I documented their responses, synthesized recurring patterns, and used those insights to define the mobile CRM features.

Research → Patterns → Priorities

The research focused on what had to happen immediately, what information was needed to keep an opportunity moving, and what could be completed progressively later.

Key insight

Mobile should not reproduce the desktop workflow. It should preserve the critical path.

NOW

  • Capture Contact

  • Create Lead

  • Update Lead

LATER

  • Full contact profile

  • Additional parties

  • Detailed cargo information

  • Additional operational data

  • Review vendor estimates

  • Manage quotations

  • Follow up + share documents

  • convert lead to shipment

CHALLENGE 01

Create a contact without forcing users to finish the CRM record

Contacts come first because they become the parties used throughout the lead and shipment workflow.

Design decision

Capture the essentials now. Enrich the contact later.

Create Contact

Only the essential fields are required, so users can create a contact in seconds. The rest is organized into scrollable tabs, making it easy to complete later without leaving the page.

List of Contacts

Everything starts here. Users can scan every business contact in one place, search instantly, or narrow the list with advanced filters instead of scrolling through hundreds of records.

View Contact

Contact details stay at the top, followed by everything tied to that relationship leads, shipments, parties, documents, KYC, notes, and more. Sections appear only when they're relevant, reducing clutter.

CHALLENGE 02

Reduce lead creation from a desktop workflow to a mobile action

The mobile flow captures only what is necessary to create the lead, then lets the user continue completing the shipment information as the opportunity develops.

6

Complete desktop steps

20-25m

Approx. desktop completion

4

Focused
mobile steps

3-5m

Target quick-create window

Routing

Mode of transport, ports, service and shipment type, estimated ship date

Cargo

Nature of goods, hazardous or perishable flags, dimensions

Parties

Billing party only. Everything else is added later

Pickup / Drop

Addresses, with copy instead of retyping

Create lead

Record is ready to be enriched

Lead workspace

A lead is a shipment in progress

Once created, the lead becomes the central workspace where sales progress and shipment completeness are managed together.

Lead Won

Two kinds of progress, one workspace.

Sales progress

New → Contacted → Interested → Quoted → Negotiation → Approved → Won / Lost.

Shipment completeness

Section-level completion rings show how much information is ready to convert the opportunity into a shipment.

The distinction

Stage tells you where the opportunity is. Completion tells you how ready the shipment is.

Lead Lost

Complex lead

One lead. One workspace.

Instead of scattering work across different screens, the lead brings the major workflows together.

Routing

Internals

Commodity

Services

Quotation

Vendor Es..

Follow ups

Parties

Document

Routing

Internals

Commodity

Services

Quotation

Vendor Es..

Follow ups

Parties

Document

INFORMATION DENSITY

Enterprise complexity without information overload

Removing information wasn’t always the answer. The product needed to make detail available at the right moment.

  • Modular sections

    Routing, commodity, quotation, docs & other workflows have clear homes.

  • Contextual navigation

    Stay in the workflow while related modules remain close.

  • Stage & progress

    Separate opportunity status from shipment readiness.

  • Documents

    Three visibility levels: private, public to everyone on the shipment, or shared with parties you pick.

  • Services

    Optional extras like packing and insurance, each branching on a yes or no.

CONTACT AS A 360° VIEW

The contact continues beyond contact creation

The same contact could participate across multiple leads and shipments, keeping relationship data connected instead of recreated for every opportunity.

For companies, employee records become part of the relationship model; individual contacts don’t expose that layer.

Lead Won

Tasks

Tags

Design System Built on Atomic Design

To keep things scalable and consistent, I built the design system using the Atomic Design Methodology organizing everything into atoms, molecules, organisms, templates, and pages.

This structured approach helped in more ways than one:

  • It ensured visual consistency across screens

  • Made components reusable and easier to maintain

  • Helped the developer implement faster with clearly defined UI patterns

Written for the two people building it.

Two developers, no design QA, and no time for a meeting every time something was ambiguous. So the file had to answer questions before they got asked.

  • 4 point grid with spacing tokens, so spacing is something you look up, not something you eyeball

  • Auto layout and constraints everywhere, so resizing behaves instead of exploding

  • One component reused in every place it appears, so fixing it once fixes it everywhere

  • Figma organised by module, so nobody has to ask which page the quotation screens live on

AfterBefore
Final DesignDeveloper handover

Outcomes

From a desktop-dependent workflow to a mobile workspace

The biggest change wasn't simply faster data entry. It was making the workflow available when the work actually happened.

76%

Team adoption within two weeks after rollout

80%

Reported daily contact + lead workflow coverage

What Changed ?

Agents could capture contacts, create opportunities, manage the lead lifecycle, handle commercial workflows and keep customer activity moving without depending on a laptop for every critical step.

Team : Kumaran Karunakaran & Kathiresan S (Mobile Dev), Kishore (QA) · Thanks to the stakeholders for continuous feedback.

Ready to Elevate Your Product Experience ?

Whether you're launching a new product or refining an existing digital product, I'm here to help. Share the details about your project and I'll get back to you to work something out.