Small, unsexy, with inherited defects
This trade did not choose the wrong software. It borrowed its idea of what software is from the industry next door, and the industry next door sells houses
A piece about a category error. Why the software this industry runs on looks like an estate agent's CRM, what a CRM is actually built to do, and why an operational business - the survey, the crew, the vehicles, the day - was never going to be well served by a sales tool with things bolted onto the side of it.
Ask a layman what a removals firm does and they'll tell you a van turns up, the boxes go in, and your house arrives somewhere else. Ask someone who actually knows the trade and you get a different answer entirely. Export packing. LTL and FTL. Multimodal. The variables you weigh on every job, the risk assessments, the compliance stack sitting underneath all of it. Same firm, same van. One person sees a man moving boxes. The other sees an intricate logistics operation that happens to end with a box in a hallway. The gap between those two answers is the whole problem with the software this industry runs on.
No picture of its own
Because here's the thing about an industry that hasn't digitised: it has no picture of its own of what good software should be. Why?
Could it be that no application was ever written for this industry from the ground up by an actual technologist? Could it be that the people who understood removals built the software, but they weren't technologists? Could it be that the technologists simply never came and did the work?
Whatever the reason, nobody ever sat in a room from first principles and asked "what would a system actually shaped around our work do?"
Nobody brought the origami
It's the same as if you handed me a sheet of paper and asked me to make something. I'd make you a paper aeroplane, because a paper aeroplane is the only thing I know how to make. It isn't that I didn't try, or that I'm not capable. It's that the aeroplane is the entire limit of what I know paper can become. Hand that same sheet to someone trained in origami and you get a swan. Same paper. Completely different idea of what's possible. The people who built software for this industry were handed the same technology everyone else has, and they made the paper aeroplane, because the CRM was the shape they knew software to take. Nobody had brought the origami.
We borrowed the picture from next door
So which industry sits closest to removals, whose picture did we borrow? Housing. It's where most of our domestic demand comes from. It's the world we live alongside, quote into, take our leads from. So when removals imagined what its software should be, it imagined the estate agent's software. And the estate agent's software is a CRM, customer relationship management, for a business whose primary objective is managing relationships.
That's not a stupid mistake, but from a technologist's perspective, it's an obvious one. If the nearest example of a business that runs on software is the estate agency down the chain from you, and that business lives inside a CRM, then a CRM is what software looks like. So the industry got handed CRMs, told "this is removals software," and then spent two decades bolting on what we actually need to a base that was never designed for it. And rather than running your business with the software equivalent of a Rolls Royce, you're running your livelihood, comparably, on an Astra with a body kit.
What a CRM is actually for
Look at what a CRM is actually for. A CRM exists to manage relationships and a sales pipeline. It's built for a business whose core problem is winning the sale: track the lead, nurture the contact, work the pipeline, convert. That is the estate agent's entire job. It is a sales business, and a CRM is a sales tool, and the two fit perfectly.
Removals is an operational one. The work isn't the selling. The work is the doing. The survey, the volume, the crew, the vehicles, the materials, the storage, the containers, the day itself, and the delivery at the other end. That's the business. The selling is a significant part at the front of a process that is otherwise entirely operational, and even the sales process in the software isn't designed from the ground up for how our sales process actually works, because our biggest moment of influence isn't when we follow up on a quote. For us it's the survey, and most of the time we get one shot.
The first fold
CRM was never the wrong answer. It was about 10% of the answer to the right question, how do I run my business digitally, mistaken for the whole of it. And to be clear, this isn't me saying customer relationship management doesn't matter. Of course it does. You need to manage enquiries, follow up, keep track of who's who and what was promised. But in the view of the wider operation, the CRM is folding the paper once. It's the first fold, and it's a real one. The mistake was stopping there and calling a single fold the finished object. The rest of the application, the survey, the resource, the plan, the day, the margin, the whole operation, that's the rest of the swan.
Most removals software made the first fold, handed you a flat sheet with one crease in it, and called it a bird.
An operation is not a relationship
Sales and administration are important but they are not operations. An operation is intricate, moving pieces, people and targets. This is an area with logistics, with so many moving parts and dependencies all interwoven. Get the survey wrong and the crew's wrong and the vehicle's wrong and the margin's gone before anyone is out of bed, and we still have to fight to manage the operation on the day. Agility, logistics, reliability. That's what this industry actually is. And none of it is a relationship-management problem.
The relationship is won on the floor, not in the inbox
And here's the part that I think matters most. In this industry, you do not manage your customer relationships by contacting people a hundred times. This is a trade that lives and dies on reviews, and reviews are earned on service. You don't nurture your way to a five-star review with an email sequence. You earn it by turning up, doing the move properly, and leaving a customer whose most vulnerable day of the year you made survivable. The relationship isn't managed in an inbox. It's managed on the floor, on the day, with the job.
Think about what that means for the software. A CRM's entire premise is that the relationship is won through contact, so it gives you the tools to contact, track, nurture, sequence. But if in your industry the relationship is won through the quality of the service, then a tool built around managing contact is solving a problem you don't have, while doing nothing about the problem you do have, which is delivering the service well.
The way you manage a customer in this industry is you give them a good move. And a good move starts by digitising and optimising what's actually in front of you: the survey, the resources, the plan, the day. That's the thing worth building software around. Not the pipeline. The operation.
Two bad options
For a long time there was no way out of this, and I understand why. If you're an operator and the software on offer doesn't fit, you've only got two options, both bad. You shoehorn yourself into a CRM built for a different industry and spend your life fighting it and bolting spreadsheets onto the gaps. Rekeying, retyping, transferring information, time, admin, hours.
Or you try to build your own, which means becoming a software company on the side, understanding security, infrastructure, engineering, network, managing cloud spend, APIs, data residency, carrying the risk, the what if it goes down Monday morning, the what if we lose data, the what if we have a breach, and learning every nuance of a discipline that isn't your trade. Taking all the valuable time and resource away from the thing we've just established this industry should be doing, running a logistics operation. And even then, you'd likely rebuild the same shape you were trying to escape, because an operator building software still starts from the only picture of software he's ever seen.
The first route leaves you with a system that fights you. The second leaves you with a six figure build bill, plus wages, plus compute costs that exceed what modern software costs anyway, and all for the pleasure of carrying the risk. Then the thing still doesn't do what you needed, because building software properly is genuinely hard, and it isn't your job.
What changed
What's changed is that someone from inside this industry is building it as a technologist would. Someone who knows what export packing is, and what the survey really decides, and where the margin leaks, and also knows the art of the possible, how to take a real operational problem, the stuff you deal with every day on the vans and in the yard, and translate it into stable architecture instead of a workaround. How to secure it so your customers' data isn't exposed and your company information is safe. Someone who understands infrastructure, data residency, and importantly what technology can actually do when it's assembled for this industry specifically. That's the unlock. Not that software arrived, software's been here for years. The unlock is that the translation now exists, between what this industry actually does and what technology is actually capable of, and it translates into something that helps you run your operation, stay compliant, save money and cut hours. Not just a digital filing cabinet, a rolodex and a calendar.
And it means the choice in front of an operator is no longer "fight a CRM or build your own." It's just: pay a subscription for software built for what you actually do. No engineering team. No infrastructure team. No security review. No cloud costs. No carrying the risk. No becoming a software developer whilst trying to run a removals firm. You pay a monthly fee, and the burden of building it, maintaining it, securing it, improving it, sits with someone whose job that is.
A category error
So this is really a piece about a category error. This industry didn't choose the wrong software. It inherited its idea of software from the industry next door, and the industry next door sells houses, so we got a tool for selling. We are operators. And the software that serves this industry is the software built around the operation, because the operation is the business, the operation is the service, and the service is the relationship.
You don't manage a customer in this trade by talking to them a hundred times. You manage them by moving them well. Everything worth building starts there.
Published by Moovi, the operating platform for the removals industry. Declaration of interest: this is an argument about the shape software for this trade should take, written by the people building one, and it should be weighed in that light. If you want the same distinction set out neutrally rather than as an essay, we have written it up as removals CRM vs operating platform and, at more length, removals CRM vs ERP. Related reading: Digitised, or Optimised? and The Wrong Way Up.