Every rental company I know has tried to modernise. They've bought the software, sat through the demos, migrated their data. And most of them are still fighting with systems that don't quite fit how they actually work.
The problem isn't that we're all stuck in the past. The problem is that "modern" gets defined by software vendors instead of by the people loading trucks at 5am.
The mismatch between features and reality
Here's what typically happens: you sign up for a rental management system. It has all the features on the checklist - inventory, projects, quotes, invoices. Demo looked great. Import goes smoothly (mostly).
Then you actually try to use it.
The workflow that made perfect sense in the demo doesn't match your workflow. You need three clicks to do something you do fifty times a day. The mobile app is technically mobile-compatible but practically unusable. And the bits you really need - real integration with your other systems, decent reporting, flexibility in how you price things - those are either missing or locked behind enterprise pricing.
So what do you do? You adapt. You work around the system instead of with it. You end up with data in the RMS, supplementary spreadsheets for the things it doesn't handle, crew schedules in WhatsApp, and a process that only works because someone remembers to update four different places.
That's not modern. That's just digital duct tape.
What "modern" should actually mean
Modern rental management isn't about having the newest software. It's about having systems that match how rental companies actually operate in 2025.
The industry has changed massively. Jobs are bigger, more complex, tighter turnarounds. Clients expect Amazon-level tracking and instant communication. Margins are squeezed. Good crew are spread thin across multiple companies.
Modern means keeping up with that reality. Here's what it looks like in practice:
Real-time inventory (actually real-time)
Every system claims real-time inventory. Few deliver it.
Real-time should mean: I check my phone right now and see exactly what's available for Tuesday. Not "available according to last night's sync" or "available unless someone forgot to check it back in".
It means knowing which specific items are on which jobs. Not just "we have 10 moving heads" but "serial 4487 is at the festival, 4488 is being prepped, and 4489 needs the bulb replaced before it goes anywhere".
It means status that updates when things actually happen - when the item gets scanned, not when someone remembers to click a button.
Every decision you make depends on inventory. Every quote, every schedule, every "can we squeeze one more in?" If that information is stale or scattered, you're guessing.
Crew coordination that works
Ask any rental company how they actually manage crew, and you'll get some version of: the RMS has scheduling, but we also use WhatsApp, a shared calendar, phone calls, and Dave who just knows where everyone is.
The RMS feature exists. It just doesn't fit the workflow. So people route around it.
Real crew coordination: one place where people can see their schedule, accept or decline jobs, get call sheets, and know immediately when something changes. On their phones. Without downloading some clunky app that drains battery and needs constant updates.
Your techs are already juggling multiple companies. They'll work with whoever makes their life easiest. If your system adds friction, they'll just call the office instead - and now you're back to phone tag.
Mobile that's actually designed for mobile
"Mobile compatible" usually means "doesn't crash on a phone screen". That's not the same as mobile-first.
The people who need rental software most are rarely at desks. Warehouse staff. Techs on site. Project managers in a van. If the system only works properly on desktop, you're excluding half your users.
Mobile-first means big buttons for people wearing gloves. Workflows designed for vertical screens. Offline capability for sites with rubbish signal. Speed that doesn't make people give up and write it on paper instead.
If your warehouse team prints paper checklists because the app is too slow, you don't have mobile. You have a problem with a mobile-shaped sticker on it.
Client portals that get used
Client portals should fix the email-print-scribble-scan-email dance. View quotes, request changes, approve digitally, see job status, pay invoices. All tracked. All in one place.
But here's the thing: if it's slow, clunky, or requires your clients to remember another password, they won't use it. They'll just call you. And you're back to manual everything.
The test of a good client portal is whether clients prefer it to picking up the phone. That's the bar.
Integration that doesn't break
This one's personal. We spent years trying to build integrations with rental management systems. Get something working, it's perfect for six months, then an API update breaks everything. Documentation that doesn't match reality. Field names that only make sense to whoever wrote them.
Modern systems should be built with integration as a first-class concern. Open, documented APIs. Webhooks. Standard formats. Not "you can technically pull data out if you figure out our endpoint structure".
Your RMS shouldn't be an island. It should play nicely with your accounting software, your calendars, your communication tools. Without needing a custom development project every time something updates.
Why we're building NexusRMS
We're not neutral observers here. We built NexusRMS because we couldn't find software that matched these principles.
We run a rental company. We've used the major systems. They work, kind of. But we kept hitting the same gaps - workflows that didn't fit, mobile that wasn't really mobile, integrations that broke, reporting that required exports and spreadsheets to make sense of.
So we're building what we wish existed. It's in open beta right now - not finished, but usable. We're building it alongside running actual jobs, which means every pain point gets felt immediately.
If any of this resonates, have a look: nexusrms.io/register. We're not looking for commitment. We're looking for feedback from people who've hit the same frustrations.