24 things you stop doing by hand.

Written for an operation running on a spreadsheet, a phone that never stops, and a map of fifty-odd containers that exists only in one person’s head.

  • The whiteboard
  • The legal pad
  • The group chat
  • The spreadsheet
  • The shoebox of scale tickets
  • The glovebox notebook
  • Your memory
01

Every container, live

Today the only complete map of which bin is where is in one person's head, and it is wrong the moment a driver moves one.

  • Status, customer, site and day count on every container — the whole yard in one read.
  • Past its included month, the row lights up and stays lit.
  • Delivery photo and GPS fix attached, so “is it still on Riverside?” is not a phone call.
  • Condition and out-of-service are fields, not a sticky note.
See the live board

The dispatch board with real rows in it is on the front page — one read of the whole yard, day counts and all.

Open
02

Tomorrow, organised the night before

Today it is a legal pad only one person can read, and a job with no driver looks exactly like a job with one.

  • A run sheet per driver, built in advance, visible to everyone who needs it.
  • The strip up top counts the four things that actually go wrong. Empty means the day is under control.
  • Reassign in one tap — the driver's sheet is the same record, so there is no second version.
  • Customer requests land in one inbox and stay there until they are scheduled.
▲ 2 jobs today with no driver▲ 1 pickup requested 4 days ago▲ 3 bins past their included month▲ 5 ready to invoice
On site3152
Unassigned today2NEEDS A DRIVER
03

Drivers, scheduled and accounted for

Today the day arrives by text message, and proof of delivery is a photo in somebody's camera roll — if it was taken at all.

  • Today's runs in route order, built for one thumb with gloves on.
  • Photo, GPS and notes captured at the point of work. Nothing closes without the minimum proof.
  • Each step commits on its own; a job interrupted halfway stays halfway.
  • Clock on and off against the truck actually taken — which is what raises its due work.
30 ydRB-014En route8:00–10:00
DeliveryGPS
23 JUL 2026 · 08:1230.2672, −97.7431 ±6 mD. Ramirez

Set on gravel pad, gate code 4417.

04

The workshop, built in

Today service intervals live in a glovebox notebook, and you learn a truck is unroadworthy after it has left.

  • Miles, days and runs — whichever trips first. An idle truck still gets its annual.
  • Due status is derived on every read: change an interval and the fleet re-evaluates, no backfill.
  • Defects sit on the board, worst first, until someone closes them.
  • A grounded truck says so before it goes out, not after.
Trucks grounded1CANNOT GO OUT
Open truck jobs2
Bins out of service1BLOCKED
Service due soon5
05

The phone stops ringing

Today every request and every “where is it?” arrives by call, text or email, on whichever number the customer saved years ago.

  • One portal: request a bin, drop a pin, photograph exactly where it goes.
  • Sites are saved with their access notes, and the driver reads them on the job.
  • The customer watches the status and the day counter themselves.
  • Pickup is a button, timestamped, ageing on the dispatch board.
  1. Requested02 JUN 202609:41
  2. Scheduled02 JUN 202614:20
  3. Delivered03 JUN 202608:12
  4. Picked up25 JUL 202611:02Billable — 52 d
  5. At disposal
  6. Invoiced
06

Billing that writes itself

Today overages are worked out by hand at month end, from a spreadsheet and a stack of scale tickets.

  • Drafted the moment the dump is recorded, from real days and real weight.
  • The billable clock runs delivery-confirmed to pickup-confirmed. Never estimated.
  • Every order freezes the rate card it was created under.
  • Ticket number and rounding printed on the line, so a disputed ton ends there.
The other comparison

And over the software you have already been quoted for

Three surfaces, built three ways

A desk, a cab and a contractor's phone need opposite things. Not one responsive table shrunk to three widths.

Post-paid, and honest

The rate card is on screen before the customer commits, and the invoice is written from what actually happened.

The arithmetic is shown

Ceiling rounding and the scale ticket number are printed on the line. Hiding the maths generates the disputes.

It re-skins from one file

Every colour, typeface and radius is a token — and on a three-year term we do the fit to your brand for you.

24 of them, and none of it is a spreadsheet

A walkthrough of the console and the in-cab driver view is being put together. Until it lands, the worked invoice on the front page is the closest look at what the product does.