CRM / SUPPLY_CHAIN// United Kingdom / Middle East

NEXUS_LOGISTICS — Supply Chain CRM for an International Freight Forwarder

An enterprise-grade inventory and shipment orchestration engine that replaced spreadsheets and three disconnected tools with a single source of truth for global supply nodes.

Next.jsPostgreSQLRedisNode.jsDocker

Mission_Outcomes

  • Replaced three disconnected tools and a wall of spreadsheets with one system
  • Shipment status lookups went from minutes of phone calls to a two-second search
  • Operations team processes roughly 3x the shipment volume with the same headcount

//The Challenge

Freight forwarding runs on reference numbers: booking numbers from shipping lines, container numbers, internal job IDs, customs documentation. Our client — a logistics provider moving cargo between Asia, the Gulf, and Europe — was tracking all of it across spreadsheets, a legacy desktop tool, and WhatsApp threads. Every customer status request triggered a chain of phone calls. Billing leaked revenue because completed jobs were invoiced late or not at all.

Off-the-shelf CRMs don't understand this domain. Logistics operations need multi-reference search, per-shipment cost tracking, and workflows that mirror how cargo actually moves — which is exactly the kind of problem custom software exists to solve.

//What We Built

We designed a custom CRM around the shipment as the central entity. Any team member can pull up a job by internal ID, carrier booking number, or container number in a single search box. Each job carries its full lifecycle — booking, customs, transport, invoicing — with role-based access so operations, finance, and management each see exactly what they need.

Under the hood: a Next.js application backed by PostgreSQL for transactional integrity and Redis for real-time status caching, deployed in Docker for painless updates. Financial events flow through a double-entry style ledger so per-shipment profitability is computed, not guessed. The system was built to be operable by non-technical staff from day one — the fastest data-entry path always wins.

//Why a Custom Build Won

The client had evaluated Salesforce and two logistics SaaS products. Licensing for their team size cost more annually than our entire build, and none of the products handled multi-reference search or their invoicing rules without consultants and compromise. A custom system built by a team that took the time to learn freight forwarding's actual workflow paid for itself within the first year — a pattern we see repeatedly with UK and European SMEs that have outgrown spreadsheets but can't justify enterprise licensing.

For the first time I can see every shipment, every balance, and every job's profit on one screen. We stopped running the business from memory.
Managing Director, logistics provider — UK / Gulf

Have a similar mission?

We work with clients across the US, UK, Canada, Europe & the Gulf.

Initiate_Connection