Founder of Padusi standing in an office reviewing logistics documents

Why we started

We got tired of hearing "the carrier was late" as if that explained anything.

Padusi started as a reaction to a specific, recurring frustration inside logistics operations: reports that could say a shipment was late, but couldn't say why. This page is our honest account of what led to that, and what we've built around it since.

Founder of Padusi standing in an office reviewing logistics documents

What we noticed

Delay reports were full of categories. None of them pointed anywhere useful.

Before Padusi existed, one of us worked inside a mid-sized freight brokerage, the kind that moves a few hundred loads a week without the budget for an enterprise visibility platform. Every month, there was a report. On-time percentage, exceptions logged, causes tagged as "carrier delay," "weather," or "customer not ready."

The categories weren't wrong, exactly. They just weren't specific enough to act on. A shipment tagged "carrier delay" could mean the driver hit traffic, or it could mean the load sat at a cross-dock for six hours because nobody updated the handoff record. Those are two completely different problems, and the report treated them the same.

Fixing the second kind of problem meant looking at actual timestamps, actual paperwork, actual conversations between dispatch and the warehouse floor. That work rarely happened, mostly because nobody had the time to do it shipment by shipment.

What "carrier delay" often hides

  • Extended dock wait times
  • Paperwork lagging the physical move
  • Route changes not logged anywhere
  • Handoffs with no clear owner

What we believe

A few things we hold to, plainly

Root cause work is slow and manual, and that's fine

There's no shortcut that replaces going shipment by shipment through the actual records. We don't pretend otherwise, and we don't try to automate around it before understanding it.

Small operations deserve this too

Enterprise visibility platforms are usually built and priced for companies moving thousands of shipments a day, not the ones moving a few hundred a week.

Plain language over dashboards

A findings document written in normal sentences is more useful to most teams than another chart nobody has time to interpret.

  • We don't sell tracking or TMS software
  • We don't manage freight or book loads
  • We don't offer ongoing retainer monitoring
  • We don't replace your existing systems

What we don't do

It's worth saying clearly what this consultancy is not.

We don't sell software, and we're not an alternative to your transportation management system. We don't manage day-to-day freight, and we don't run ongoing monitoring contracts. What we do is a bounded piece of work: tracing a set of delays back to where they started, and handing over what we found.

If, during a consultation, it becomes clear your situation needs something else entirely, such as a new TMS or a dedicated operations hire, we'll say that directly instead of stretching the engagement to fit.