Stakeholder
CEO
How a conversation with this stakeholder actually goes
The CEO is the most valuable person to get in front of and often the hardest to keep engaged. They agreed to this call because someone on their team said it was worth their time, or because they have a specific problem that is costing them enough that they are willing to spend 30 minutes exploring solutions. Either way, their patience is limited and their filter for anything that sounds like a pitch is extremely sensitive.
Open by giving them the floor immediately. Do not spend the first five minutes explaining The North. They know who you are. Ask them what is going on in the business and what made them take this call. Then listen without interrupting. The detail they give you in the first few minutes tells you everything about what kind of decision-maker they are and how much internal pressure they are under.
The CEO will often start with a high-level problem and watch to see whether you understand its implications or whether you reach for a service before you have understood the full picture. The response that loses a CEO: "Great, that sounds like a CRM problem, we do CRM implementations." The response that keeps them engaged: "That is interesting. When you say the pipeline data is not reliable, what is the downstream effect of that? Are forecasts consistently off, or is it that leadership cannot make resource decisions with confidence?" One response is reaching for a solution. The other is deepening the diagnosis. CEOs can feel the difference immediately.
Close by connecting your proposed next step directly to something they care about. Not "I will send you a proposal." Instead: "Based on what you have described, I think the right starting point is a diagnostic that gives you a clear picture of exactly where the data is breaking down and what it would take to fix it. The output of that is something you could walk into a board meeting with. Would it make sense to talk about what that looks like?"
Priorities
The CEO's world is almost entirely focused on three things: whether the business is growing, whether it will keep growing, and whether it is building toward the outcome they originally set out to achieve — whether that is an exit, a sustainable private business, or a public company. Everything else is a lever toward one of those three outcomes. When you are in a conversation with a CEO, every recommendation you make needs to connect to one of those levers. If you cannot explain how a CRM implementation moves the needle on growth, efficiency, or exit readiness, you will not have the CEO's attention for long.
Fears
CEOs have one fundamental fear in any external engagement: investing in something that does not move the needle. They have seen vendors overpromise and underdeliver. They have approved initiatives that consumed their team's time and produced no measurable outcome. They have paid for strategy that never became execution. When a CEO is skeptical of a proposal, it is almost always rooted in one of these prior experiences. Your job is not to overcome their skepticism with better sales technique — it is to give them genuine reasons to believe that this engagement is different. That means being specific about outcomes, honest about timelines, and clear about what success looks like.
KPIs they are measured on
CEOs think in company-level metrics: revenue growth rate, gross margin, headcount relative to revenue, customer acquisition cost versus lifetime value, churn rate, and — if they are funded — runway and burn. When you talk about a service, connect it to one of these numbers. A CRM that nobody trusts is a forecast accuracy problem. Poor attribution is a capital efficiency problem. High churn is a lifetime value problem. These are the frames that land with a CEO.
What closes them
CEOs close when they feel three things: that the outcome is worth the investment, that the risk is manageable, and that you are the right partner to deliver it. The first requires connecting your proposal to a revenue or efficiency outcome they care about and quantifying the cost of inaction. The second requires a clear first step — an audit, a diagnostic, a fixed-scope engagement — that lets them see how you work before committing to something large. The third requires you to demonstrate that you understand their business, not just your services.
Language to use & to avoid
Use terms that CEOs use with their boards: revenue infrastructure, capital efficiency, operational leverage, compounding returns, cost of inaction. Frame every recommendation in terms of what it enables — not what it builds. "After this, you will be able to call your quarter before it ends" is CEO language. "We will configure your CRM with custom pipeline stages" is not.
Avoid deliverable-centric language: "we will deliver," "we will build," "the output will be." Avoid technical jargon without immediate business translation. Avoid vague ROI claims without supporting logic. And never, in a conversation with a CEO, ask questions that reveal you have not done your homework on their business.
Quick reference
Priorities
- Revenue growth
- Margin
- Team efficiency
- Building toward an outcome (exit, scale, or sustainability)
- Defensible business decisions
Fears
- Investing in something that doesn't move the needle
- A vendor who can't show ROI
- Implementation that distracts the team without results
- Looking uninformed in front of the board or investors
KPIs
- Revenue growth
- Gross margin
- Headcount efficiency
- CAC:LTV ratio
- Churn rate
- Runway / burn (if funded)
Buying motivators
- Connecting your engagement to revenue outcomes they can defend to a board
- Framing the cost of inaction (what does this problem cost per month if unsolved?)
- Making the decision feel low-risk with a clear first step
- Social proof from companies at their stage or in their vertical
Common objections
- How do I justify this to my board?
- What's the ROI timeline?
- Can my team handle this on top of everything else?
Language to use
- Revenue infrastructure
- Capital efficiency
- Operational leverage
- Compound over time
- Cost of inaction
- What this unlocks
Language to avoid
- Deliverables
- Features
- Best practices
- Industry standard
- Technical jargon without business framing
You are reading a detail page within Stakeholders. This page is part of Module 8 of 12 in the New Account Manager Track. Back to Stakeholders