Choosing skip hire software: the questions that actually matter

Every system looks good in a demo. The person showing it has driven that route a hundred times, the data is tidy, and nothing goes wrong. You learn almost nothing about how it behaves on a wet Monday when a driver is stuck, a customer is shouting, and the office is two people down.

So the demo is not where you make the decision. The questions are. Here are the ones worth asking, and what a straight answer sounds like.

What does it cost when we grow?

Ask for the price of the thing you will have in two years, not the thing you are buying today. Per-seat pricing looks reasonable at three users and punishes you at ten — and it quietly discourages you from giving a login to the people who would benefit most, which is usually the drivers.

Ask directly: what happens to the bill when we add a vehicle, a user, a depot, or double the orders? If the answer needs a meeting, that is the answer.

What is the contract, and what happens if we leave?

Two separate questions, and the second one matters more.

A twelve-month tie-in on software you have not lived with yet is a bet placed by the vendor with your money. But the sharper question is exit: can you get your orders, customers, invoices and documents out, in a usable format, whenever you want, without asking permission or paying for the privilege? Your operating history is your asset. If it can be held hostage, it will be — if not deliberately, then by a vendor who has stopped developing the product and has no incentive to help you go.

The right time to find out how you leave a system is before you join it.

Can we switch off what we do not need?

Skip hire businesses are not identical. Some run a transfer station, some tip elsewhere. Some do a lot of permits, some almost none. Some are half grab hire. Software that insists you take all of it, configured its way, will spend the first month teaching you a workflow you did not ask for.

Ask whether modules can be turned off, and whether turning one off actually removes it from the screens or merely hides a menu item. Clutter is a real cost — every field a person has to skip is a small tax on every job, paid several hundred times a week.

What does the driver actually see?

This is the question that most reliably separates systems built for the trade from systems adapted to it.

Ask to see the driver's screen on a phone — an actual phone, not a tablet emulator on a laptop. Then ask:

• Does it work with a bad signal halfway down a lane, and what happens to a photo taken while it is offline?
• How many taps from opening the app to navigating to the next address?
• Can they capture a photo and a signature at drop and at collection?
• Is there an app-store install to manage on twelve phones, or does it just open in the browser?

A driver view that requires training is a driver view that will be worked around. The measure of it is whether a new driver can be handed a phone and get through the day without ringing the office.

What happens to the phone calls?

A large share of the calls into a skip hire office are not orders. They are people asking where their skip is, when it is being collected, and whether they can have their invoice again. Every one of those is a person in your office not doing the thing you actually pay them for.

Ask what the customer gets. Can they see their own order, ask for a collection, place a repeat order and download an invoice without ringing you? Does that require them to create an account and remember a password — because if it does, they will ring you instead. This is the single change most likely to give you your afternoons back, and it is worth weighting heavily.

Where does it stand on digital waste tracking?

As of 1 October 2026, permitted sites in England and Wales must report the waste they receive digitally. If you hold a permit, this is not optional and it is not far away — we covered the detail in what skip hire operators must do by 1 October.

So ask any vendor: are you on Defra's published list of compatible software providers? If not, where are you in the production approval tests, and when do you expect to be listed? Get the answer in writing. A vendor who is vague about a dated regulatory requirement will be vague about the next one too.

Who answers the phone when it breaks?

Not "is there support" — there is always support. Ask who picks up, what hours, and whether the person who answers knows what a wait-and-load is. There is a large difference between a helpdesk that logs your ticket and someone who understands why a missed collection on a Friday is urgent.

Ask for a reference customer who has had something go wrong. How the vendor behaved on a bad day tells you more than a page of testimonials.

How do we get our existing work into it?

You have a customer list, live hires, and a set of prices. Ask exactly how those arrive in the new system, who does the work, and what it costs. "We will help you with that" is not a plan. A specific answer sounds like: send us your customers as a spreadsheet in this shape, we will load them, you check them, and we go live on a Monday with the previous week's live hires entered.

Run the trial properly

When you do test something, do not test it on invented data. Take a real day — ideally a bad one — and put it through the system exactly as it happened. The Tuesday with fourteen deliveries, two permit jobs, a breakdown and a customer who changed the address twice. If a system survives your worst ordinary day, it will handle the rest.

And time it. Not the demo — the tenth order you enter yourself, once you know where the fields are. That number, multiplied by the orders you take in a year, is the real price of the software.

If you want to run that exercise against SkipHub, that is precisely what our demo is: half an hour, your workflow, your skip sizes, a real address. The pricing page has no tiers to decode, and the features pages spell out what is in each module.