Salesforce for Equipment Hire / Key-Person Risk
Every hire business has a Dave.
The person who just knows. Which customers pay late and which ones are worth chasing harder. Why that account gets a different rate. Which yard has the spare part when the system says there isn't one. How the pricing really works, underneath the price list.
Nobody put that knowledge there on purpose. It just ended up there — because Dave's been doing it longest, or picked it up fastest, or was simply in the room enough times that it stuck. It works. Right up until the day it doesn't.
Key person risk is when a hire business depends on one or two people's memory — who to trust, which yard has spare stock, how pricing really works — rather than on a documented, shared process. It shows up the moment that person is off, promoted, or leaves. Fixing it means turning that unwritten knowledge into something anyone on the team can apply — not replacing your best people, protecting what makes them good.
Where you are now
Ask yourself honestly: if your best hire desk person was off for two weeks — not fired, not leaving, just unreachable — what would actually happen to a complex quote next week? For most hire businesses, the answer is some version of: someone else would manage, eventually, after a few calls and a bit of guesswork. That's not a criticism of the team. It's just where the knowledge currently lives — in people, not in the process.
Where you want to be
Not a business with no key people — every good business has people who are excellent at what they do, and that's worth protecting, not erasing. The goal is simpler: a business where Dave being brilliant is an asset, not a dependency, where a new starter can quote with the same confidence in month two instead of year two.
The gap in between
The distance between those two points isn't a training problem. It's a structural one. As a hire business grows, the amount of unwritten knowledge it depends on grows with it — more customers, more pricing exceptions, more edge cases — and none of it scales by hoping people remember more.
Left alone, that gap tends to widen quietly. You don't usually notice it until the day it matters — a busy period, an unexpected absence, someone leaving. By then it's not a hypothetical anymore.
“Failure is often caused by trying to force software onto poor processes. Start with understanding how the business should work, then build technology around that vision.”
— Jake Revell, Sales & Marketing Director, Celsius Hire
The team adopted the new way of working quickly, with little resistance — pricing logic that used to live in someone's head became something anyone could apply consistently, protecting what made their best people good at the job instead of trying to replace them.
Worth asking yourself
If your best person took two weeks off tomorrow, how confident are you that the business would run the same? If the honest answer is “not entirely” — that's not unusual, and it's not a people problem.
Links to the Business Case Builder — no pressure, no call required, just a way to see the shape of it for yourself.
Build the case for fixing itCommon questions
What people ask us about this
What is "key person risk" in a hire business?
Key person risk is when a hire business depends on one or two people’s memory — who to trust, which yard has spare stock, how pricing really works — rather than on a documented, shared process. It shows up the moment that person is off, promoted, or leaves. Fixing it means turning that unwritten knowledge into something anyone on the team can apply — not replacing your best people, protecting what makes them good.
How do I know if my hire business has key person risk?
Ask: if your best hire desk person was off for two weeks — not fired, not leaving, just unreachable — what would actually happen to a complex quote next week? If the honest answer is “someone would manage, eventually, after a few calls and some guesswork,” that’s key person risk, even if it’s never caused a real problem yet.
Does fixing this mean replacing good staff, or getting rid of "the person who knows everything"?
No. The goal isn’t a business with no key people, it’s one where that person being brilliant is an asset rather than a single point of failure — a new starter quoting with the same confidence in month two that used to take a year to build.
How does Salesforce actually help with this?
By turning pricing exceptions, customer history, and yard-level knowledge that currently lives in someone’s head into something structured the whole team can see and apply consistently — not a training document nobody reads, but the system the hire desk actually works from.
Is this only a problem for small hire businesses?
No — it tends to get worse as a business grows, not better: more customers, more pricing exceptions, more edge cases, all still depending on someone remembering them. Usually invisible until a busy period, an absence, or someone leaving makes it impossible to ignore.