The Family Tree Nobody Mapped

My first week at the company, I took the leadership team out for beers on a Thursday night. I was new. I wanted to listen more than talk. I wanted to understand who these people were, how they worked, what they cared about.... the standard playbook for walking into someone else's business and trying to earn your place in it. They were a lively group! Loud, funny, loyal to each other in the way that people get when they've worked together long enough to stop being coworkers and start being something else. Stories started coming out. Names. Histories. How long everyone had been there, how they'd ended up there, what the early days looked like. Somewhere around the third round I started doing the math. Chris Sr. had founded and built the company, one truck to ten over twenty years. His son, Chris Jr. was our lead estimator and master plumber. We operated under Jr.'s license, which meant we operated at his discretion. His brother, Marcus, ran the construction crew - four guys (and all were related...), major accounts, a Purple Heart on the wall of his office. Ray, our director of operations, was Sr.'s brother-in-law. Marcus's wife Dana worked the phones as our lead CSR and dispatcher, and Ray's daughter, Diane, was our second CSR. Lead estimator. Master license holder. Construction foreman. Director of ops. Two CSRs. One family. Different last names — marriages, divorces, the natural scatter of a family across a couple of decades. Nothing on the org chart connected the dots. Nothing in the CIM mentioned it. Nobody during diligence thought to ask. I sat there at that bar, beer in hand, starting to understand what I'd actually walked into. These weren't people who simply worked together. Ray had watched Sr.'s kids grow up. It was Marcus who came home from one of his tours and stood by Dana when no one else did. That's the kind of thing that doesn't show up in an org chart. That's the kind of loyalty that doesn't transfer with a bill of sale. When the seller is the patriarch, you aren't inheriting employees. You're inheriting a community that was built around someone who just left. Everyone in that building had known Chris - through weddings, funerals, deployments, and decades of small-town life. I'd known him for about thirty days. I remember thinking I could still make it work. I wasn't wrong that it was possible. I was wrong about how hard it was going to be. Here's what no spreadsheet shows you: in a family business, the seller isn't just selling a company. He's stepping back from a world he built around people he loves. When he leaves, everyone left behind is navigating that loss while also figuring out whether to trust the person who replaced him. Some of the most important diligence you'll ever do happens over a beer, not in a data room. Ask about tenure. Ask how people ended up there. Ask who knew who before the business existed. And if you're looking at a family business - map the org chart against the family tree. Different last names don't mean different families. Some Facebook stalking could have vetted this out. That's not a problem you can spreadsheet your way out of.