The problem
Where the hours go
Logistics runs on portals. Every carrier and every customer has one, and someone logs in to book, check and download. The more lanes you run, the more portals there are.
We take the portal work on and check it as it goes. A person still approves the spend and anything that goes to a customer.
What we run
The work we take off your team
Portal bookings
Bookings and updates made on carrier and customer portals, including those with no API.
- Your rules, applied every time
- Approval on the spend
Delivery checks
Delivery status and proof of delivery collected and checked against what was booked.
- Gaps flagged in Slack
- Customers updated where you want
Freight invoices
Carrier invoices matched against the booking and the rate, with the mismatches flagged.
- Collected from portals and email
- Synced into your accounting system
Examples
How the work runs
These show how we'd run the work. The portal result is from a customer in hospitality software.
Carrier booking
- Bookings placed without a person.
Delivery check
- Missing deliveries flagged early.
Freight invoices
- Only the mismatches need a person.
Results
What one customer got back
A B2B software platform serving hospitality had supplier invoices and orders landing on one desk. We've run that work for about a year.
a month
Handed back to their ops team.
orders a month
Placed without a person.
"The team is fantastic. We use the software daily for automating complex workflows which the team helped us get set up, these now save us time daily."
Head of Operations, hospitality software platform (G2, 5.0)
- Carrier bookings
Made on portals with no API.
- Proof of delivery
Collected and filed against each job.
- Freight invoice checks
Matched against the booking and the rate.
- Status updates
Copied into your own systems and to customers.
- Reconciliation
Carrier and bank lines reconciled.
- Driver and staff questions
Answers from your own procedures, in Slack.