For a recent episode of Revenue Mavericks, I sat down with Carl Borsody, Chief Revenue Officer at Uniphore, a company pivoting its go-to-market around a focused AI platform. Carl's career spans more than two decades of enterprise sales leadership at Cisco, Juniper Networks, and Palo Alto Networks, where he led the U.S. Major and Strategic Accounts business. But what stayed with me most wasn't the tenure or the logos. It was how consistently calm he is about everything, and how deliberately he's built that steadiness into a leadership philosophy.
Carl didn't point to a boardroom or a deal gone sideways when I asked about the experience that shaped him most as a leader. He pointed to a hospital room.
He was watching a doctor navigate a high-stakes moment. The situation was tense, the room was anxious, and this physician never once matched the energy around them. Not because they were detached or indifferent. Because they understood that the room already had more than enough urgency in it. What the moment needed wasn't someone to escalate the tension. It needed someone steady enough to think clearly while everyone else was reacting.
That image stuck with Carl, and it became the lens through which he approaches leadership. His heart might be racing. His brain might be cycling through scenarios. But his team doesn't see any of that, because they don't need more pressure pushed into the system. There's already plenty of it. What they need is someone who can absorb the tension rather than amplify it.
It's a subtle distinction, but it changes everything about how a team operates in high-stakes moments. Calm isn't passivity. It's not a lack of caring. It's the discipline to stay composed precisely because you care deeply about the outcome, and you know that panicking won't get you there any faster.
2. The Unconventional Move That Made Him a Better CRO
Carl's career path has a chapter in it that most CROs don't have, and it's arguably the one that matters most.
After spending eight years in management, he made the unusual decision to step back into an individual contributor role. On paper, it looked like a step backward. In practice, it was one of the smartest things he ever did.
Those years in leadership had given him what he calls "cheat notes," a mental library of patterns around deal strategy, executive engagement, objection handling, and negotiation. Most sellers spend an entire career accumulating that knowledge one deal at a time. Carl had spent eight years watching hundreds of deals unfold from a leader's vantage point, absorbing the patterns the way an online poker player sees more hands in a month than a live player sees in a year.
When he went back into a selling role, all of that pattern recognition came with him. He had the confidence to engage with senior executives because he'd been coaching others on those conversations for years. He gravitated toward new accounts, the ones most reps avoided because there was no existing relationship to lean on, because he knew how to build from scratch.
And when he eventually moved back into leadership, he brought something rare: a seller's instincts paired with a leader's peripheral vision. He understood what the job felt like from the inside, not as a memory from early in his career, but as a recent, lived experience. That combination of perspectives is what makes his coaching sharper and his empathy for his teams more grounded than most executives in his seat.
When I asked Carl about the framework that has driven the most outsized results in his career, he didn't point to a methodology or a process. He pointed to a mindset: meet the customer where they are, not where your pitch deck says they should be.
The concept sounds simple, but the execution is where most sellers and most organizations fall short. Carl described the moment it crystallized for him. Someone was trying to sell him a sales application, and the pitch was drowning in product names, technical acronyms, and jargon that meant nothing to him as a buyer. He realized his own teams were doing the exact same thing to their customers.
The instinct in enterprise sales is to demonstrate expertise by speaking the most technical language possible. But that instinct backfires with business buyers who don't live in your product's world. They start tuning out. They check their phone. They begin to feel like the conversation isn't for them. And once that happens, you've lost them.
One CIO crystallized it for Carl's team in a way no one forgot. He looked at one of Carl's architects and said, essentially: you're almost certainly smarter than I am when it comes to this technology. But if you want my business, explain it to me in terms I understand. Otherwise, I'll send you to my technical team, and they'll evaluate you on their terms, not mine.
Carl took that lesson and built it into how his teams operate. The framework is straightforward: understand what the buyer is trying to achieve, and talk about it in their language, without ever mentioning a product name. If you can describe the value you deliver without relying on your own terminology, you force yourself to think in the customer's context. And when you do that, the conversation shifts from a pitch to a partnership.
He applies the same principle to timelines. Most sales organizations plan around when they need the purchase order. The customer doesn't care about your PO date. Their value starts at go-live. So Carl has pushed his teams to anchor every timeline around the customer's moment of value, not the internal close date. When you frame urgency around when the customer starts benefiting, they care about the timeline as much as you do.
Carl said something during our conversation that stuck with me: you don't need to push your team over the edge. There's already enough urgency in the system. Your job is to help them think, not to add to the noise.
That philosophy runs through everything he does, from how he stays calm in a tense room, to how he coaches sellers to drop the jargon and actually listen, to how he hires for deal-finding capability over industry pedigree. He told me he'd take someone who knows how to find business use cases in every corner of an organization over someone with a perfect industry resume nine times out of ten. Because curiosity and resourcefulness transfer. Product knowledge can be taught.
As Carl rebuilds Uniphore's GTM organization around a focused AI platform, he's applying the same principles he's carried for two decades. Get the right people. Build repeatable process. And never lose sight of the fact that on the other side of every deal, there's a person trying to solve a problem in language that makes sense to them.
That's how you build something that holds up.
Listen to the full conversation on the Revenue Mavericks podcast.