I met Rajan in a factory outside Ahmedabad. Not his real name. But you know him.
Eighteen years with the company. Purchases, vendor terms, pricing, inventory — all of it lived in his head. The owner introduced him to me the way founders always introduce their Rajan: with pride. "He handles everything. I don't have to worry about that side of the business at all."
That sentence is the problem. The owner just told me the most valuable knowledge in his company was stored in a place he didn't control and couldn't back up.
I've been doing this eighteen years. Every single business has a Rajan. Sometimes it's a purchase manager. Sometimes it's the founder's cousin who runs collections. Sometimes it's the founder himself. The name changes. The risk doesn't.
Why nobody sees it
Here's what makes Rajan dangerous: he never lets anything break.
Vendors get paid on time. Stock never runs out at the wrong moment. The pricing is always right. Because he's good — genuinely good — nothing ever goes wrong on his watch. So nobody worries about him. There's no alarm on the dashboard for "one human being holds six months of institutional memory."
The founder sleeps fine. Right up until the Tuesday Rajan hands in his resignation.
I've watched it happen. By Friday the owner didn't know which vendor to call for the next order. Didn't know the real credit terms — the ones agreed on a phone call, never written down. Didn't know where the dead stock was buried. The business didn't collapse. It's rarely that dramatic. It just shook, badly, for six months. Margins slipped. Two good customers left. The founder aged a year in a quarter.
Eighteen years of knowledge walked out in a cardboard box.
It's not a loyalty problem
Founders always tell me the same thing first: "But Rajan would never leave. He's loyal."
Maybe. But loyalty isn't a strategy, and it definitely isn't insurance. People leave for reasons that have nothing to do with you — a spouse's job in another city, a health scare, a better offer, a falling-out you didn't see coming. You cannot build a business on the assumption that your single point of failure will stay single and stay put forever.
And here's the part founders miss: this isn't about Rajan being replaceable. It's about the knowledge being owned by the business instead of rented from a person.
What actually fixes it
You don't fix a Rajan by firing him, cloning him, or watching him like a hawk. You fix it by moving what's in his head into the business. Three moves:
Name the function, not the person. "Rajan handles purchases" becomes "Procurement is an owned process, with a documented standard and a named backup." The work stops being a personality and starts being a system.
Make the knowledge visible. One tracker for vendors and real credit terms. One view of slow-moving stock, updated in the weekly rhythm — not stored in someone's memory and pulled out when asked. If it only exists in a conversation, it doesn't exist.
Build a shadow. Every critical function gets a second person who could run it on Monday morning if they had to. Not as a threat to Rajan. As insurance for the founder. Good people don't resent this — they respect a business that takes continuity seriously.
None of this needs expensive software. None of it needs a reorg. It needs a decision: the business will own its own operations, instead of renting them from whoever's been here longest.
The question worth sitting with
So here's what I'd ask you this week. Not rhetorically — actually answer it.
Who is your Rajan? And what specifically happens to your revenue the day he leaves?
If the answer comes fast and clear, good. You've already done the work. If it doesn't — if there's a knot in your stomach because you know exactly whose name it is and you know there's no plan — that's not a staffing gap.
That's the most expensive risk in your company, hiding in plain sight, dressed up as your most trusted employee. And it's fixable in ninety days.