Unicorn CEO Playbook: Lessons from Pentera's Amitai Ratzon

Your First Job as CEO is to Translate, Not Just Lead

Most leadership advice is generic. It tells you to have vision, be resilient, and build a great culture. But it doesn't tell you how . When you're leading a company like Pentera—a cybersecurity firm valued at over $1 billion with backing from investors like Awz Ventures, Delta-v Capital, and Blackstone—you don't need platitudes. You need a playbook.

Amitai Ratzon, CEO of Pentera, has a background that includes military service, sales leadership, and even lessons from basketball. Many founders have diverse backgrounds, but few are systematic about translating that experience into concrete leadership frameworks. This is your first job as a leader: don't just accumulate experience, decode it and turn it into a system your team can understand and use. Let's break down how to do that.

From Battlefield to Boardroom: Install a "Commander's Intent"

Military experience is often cited for teaching discipline. That's true, but generic. The more potent lesson is the concept of "Commander's Intent." In a chaotic environment, you can't micromanage every decision. Instead, a leader provides two things:

The ultimate objective: What does a successful mission look like? (e.g., "Secure the bridge to allow our forces to cross.") · The operational constraints: What are the hard boundaries? (e.g., "Don't cause civilian casualties," or "You have one platoon and air support on 15-minute call.")

With a clear Commander's Intent, a sergeant in the field can adapt to unforeseen circumstances (the bridge is damaged, the enemy is in a different location) without needing to ask for permission at every step. They know the goal, and they know the rules. This is exactly how you should be managing your team.

How to Apply Commander's Intent to Your Startup

For Product: Instead of dictating features, define the intent. "Our goal for this quarter is to reduce user onboarding friction so that 75% of new signups successfully complete a core action within their first session. You have two engineers and one designer. You cannot touch the core database schema." · For Sales: Instead of just assigning a quota, provide intent. "Our Q3 objective is to land 5 new logos in the Fortune 500. We must maintain a 70% gross margin on deals and cannot promise any features not on the public 6-month roadmap."

Your team is now empowered to solve problems creatively within a defined strategic space. They don't need to ask you for permission on every small decision. This builds autonomy, speed, and ownership.

Stop "Building Culture." Start Rewarding Performance.

Every founder wants a "strong, positive culture." The mistake is thinking this comes from free lunches, ping pong tables, or saying "we're a family." A high-performance culture, the kind that survives hypergrowth and market downturns, is built on a different foundation: clarity and consequences.

A strong culture is not a vibe. It's a clear set of principles, consistently enforced, about how you hire, fire, and promote.

Your culture is defined by the worst behavior you are willing to tolerate. If you tolerate a brilliant salesperson who is toxic to the support team, your culture is not "customer-centric." If you promote someone who hits their numbers by cutting corners, your culture is not "built on integrity."

A Tactical Framework for a High-Performance Culture

Define 3-5 non-negotiable principles. Not aspirations like "Excellence" or "Innovation," but specific behaviors. E.g., "We debate openly, then commit fully." "We measure everything." "We respond to customer tickets in under 60 minutes." · Integrate these into your core processes. Add a section to your interview scorecard: "Rate the candidate on their ability to 'Debate Openly, Commit Fully'." Make it a mandatory topic in performance reviews. · Reward it publicly. In your All-Hands, don't just praise the person who closed the big deal. Praise the engineer who stayed late to fix a bug that honored your "customer-first" principle. This shows what you truly value.

The CEO as Point Guard, Not Star Player

Ratzon draws lessons from basketball, which is a powerful analogy for CEO performance. Many early-stage founders are the star player—the best salesperson, the visionary product mind. But as you scale, your role must shift from "player" to "point guard." A point guard's job is not always to score the most points. Their job is to make the entire team better.

Know when to pass the ball. Your job is to hire executives who are better at their functions than you ever were. Your Head of Sales should be a better salesperson than you. Your Head of Product should have deeper product sense. Your role is to get them the ball (resources, clear goals) in a position where they can succeed. · See the whole court. You are the only person who can see how a decision in marketing will affect product, and how a new hire in engineering will impact the sales roadmap. Your job is to run the plays and ensure the team isn't running into each other. · Control the tempo. Are you in a "blitzscale" phase where you need to burn cash for growth? Or are you in a "conserve and build" phase during a market downturn? You set the pace of the game.

Common Mistake: The "Player-Coach" CEO

Too many CEOs try to be both a player and a coach for too long. If you are still taking sales calls, coding features, or designing marketing assets after you have 50 employees, you are failing at your real job: building and enabling your executive team.

Resilience Is a System, Not a Trait

Cybersecurity is a high-stakes, high-pressure industry. One breach, one major incident, can have massive consequences. Ratzon’s emphasis on resilience is key, but "be resilient" is useless advice. Resilience isn't about having thick skin; it's about having a system to process adversity.

A System for Resilience: The OODA Loop

A concept from military strategy, the OODA loop (Observe, Orient, Decide, Act) is a powerful framework for making good decisions under pressure.

Observe: What is happening? Get the raw, unbiased data. (e.g., "Customer churn is up 15% this month.") · Orient: Why is this happening? This is the most important step. Analyze the data in the context of your situation, your team's capabilities, and the market. (e.g., "Our biggest competitor launched a new feature, and our pricing is 20% higher. Our onboarding is also buggy.") · Decide: What is the single most important thing we can do right now? Choose one path. (e.g., "We will form a tiger team to fix the onboarding bugs in the next 7 days.") · Act: Execute the decision with speed and focus.

The key is to cycle through this loop faster than your competitors and faster than the situation can deteriorate. Resilience comes from trusting your process for handling chaos, not from being emotionless.

How to Apply This This Week

Draft a Commander's Intent for your most important Q3 goal. Write it down and share it with the relevant team. See if it clarifies their work and reduces the number of questions they ask you. · Review your company values. Are they generic aspirations or specific, enforceable behaviors? Pick one value and identify a concrete way to reward someone for living it in your next All-Hands meeting. · Audit your own calendar for last week. How much time did you spend as a "player" (doing functional work) versus a "coach" (hiring, unblocking your team, setting strategy)? If the ratio is wrong, what is the one "player" task you can delegate this week? · Identify one recurring, stressful problem. Apply the OODA loop to it on paper. Observe the facts, Orient yourself with the context, make one clear Decision, and define a single Action to take. This deliberate process can break the cycle of reactive firefighting.