Skip the map and read the page

Enter →

The Situation

You bought good software. One decision at a time.

Freight brokers coordinate shippers and carriers. 3PLs do that and hold the freight too. Both answer to two parties who want opposite things — and every tool underneath was bought one at a time, to solve one problem, with none of the others in mind.

Freight Brokers

A load lives in four systems at once

The TMS holds the details, dispatch knows who is actually driving, HubSpot shows the shipper something from last night, and accounting invoices whatever they see in their inbox. When a load changes, someone updates the rest by hand.

3PLs

Two systems of record that disagree

The TMS says the load shipped. The WMS says the pallet is still on the floor. The client portal shows whichever synced last, and billing has to reconcile both — across several clients' inventory in one building.

This is fixable, and it's fixable without buying anything else. The systems are fine. It's the connections between them that need some love.

The Cartographer Journey

Map it, design it, build it — in that order.

Skipping a step is what creates the mess. You can't design a system you haven't watched running, and you can't build one you haven't designed.

  1. 01 Current Reality Where you are now
  2. 02 Orientation Discovery & audit
  3. 03 Cartography Mapping & design
  4. 04 Exploration Build & implement
  5. 05 Connected Operations Where you end up

Orientation

We document how work actually moves — the spreadsheet someone updates every morning, the call that has to happen before anything ships, the step that only works because one person remembers it. About four weeks.

Cartography

We draw the future state explicitly, incorporating both systems and process: every handoff, every data flow, and what the system should escalate to a person instead of deciding alone. Up to fourteen weeks, depending on scope.

Exploration

We build it with you, train your team on how it works, then hand over documentation detailed enough that a new hire can't immediately break it. About six weeks.

The Atlas

Your team owns the system after we leave.

Every engagement produces The Atlas — the documentation and training repository for the operation we built with you. Not a folder handed over on the last day, but the record of how everything works, written as we go, in the language your team already uses.

It is the difference between needing a retainer versus becoming self-sufficient.

What this looks like

A brokerage that stopped copying data between two sides

Fenichey, a freight brokerage moving 1,200–1,500 loads a month between a carrier network and a shipper base, needed to move work through a mix of in-house staff and contracted agents. Load changes were frequent, and that meant that every update needed several redundant steps on the same records.

  1. What we found. A HubSpot subscription doing a fraction of what it could, and a workflow set that had grown by accretion until nobody could say with confidence what most of it did.
  2. What we designed. Six purpose-built pipelines — Quoting, Logistics, Agent Sales, Accounting, Claims, and a master Operations router that decides where an inbound request belongs before a person has to.
  3. What we built. The pipelines, the routing, and automated handling for their full monthly volume of billing inquiries. Then we handed it over.
87 %
Reduction in workflows

"We had nothing before... We do now!" — Vin Carano, CEO of Fenichey, at engagement wrap-up

Find out where your operation is losing time.

Thirty minutes. No deck, and no discovery questionnaire to fill in first.

Schedule a Chat
  • We map how a load actually moves through your operation today
  • We name which systems conflict, and what that is costing you
  • We describe what an Orientation would cover for you specifically
  • We tell you if we are not a good fit, and refer you to someone who could be