You have a great idea. You know it’s great because it solves the actual problem, it’s based on real insight, and three people on your team who are not usually easy to impress told you so. Now all you have to do is convince the people inside your organization who technically don’t need convincing — they hired you for this — but who will, nonetheless, require convincing before a single pixel moves forward.
Welcome to the internal pitch. The meeting where democracy goes to die and hierarchy reveals its true face. The room where your job is not to present an idea but to reverse-engineer what the people in that room have already decided and dress your idea in those clothes.
The Pre-Meeting Before the Meeting
Every veteran of corporate creative life knows that the actual meeting is not where decisions get made. Decisions get made in the hallway conversations, the Slack threads that happened the day before, the lunch that you weren’t invited to, and the brief bilateral with the CMO that occurred at 8:45 AM and set the temperature for everything that followed.
The pre-meeting before the meeting is not an optional exercise. It is the real meeting. The calendar event with fifteen people and a projector is a formality — a ceremony to ratify what has already been decided informally, with occasional detours into chaos when someone in finance decides they have opinions about color palettes.
If you’ve ever walked into an internal pitch cold — without having checked the temperature, aligned with at least one ally in the room, or understood what the key stakeholders are worried about this week — you have experienced the specific agony of presenting excellent work into a vacuum. The work lands. Nothing happens. There is polite applause. The MD says “let’s discuss.” Three weeks pass. The idea dies in an email thread.
This isn’t because the idea was bad. It’s because ideas, inside organizations, don’t succeed on merit. They succeed on relationships, timing, and the careful pre-alignment work that nobody puts on the project timeline but everyone does if they know what they’re doing.
Reading the Room (It’s Already Empty)
Here’s the other thing nobody tells you about internal pitches: by the time you’re presenting, most of the people in the room have already mentally allocated one of three responses to your idea. The Enthusiast — usually someone who hasn’t done the work and has no skin in the game — will love it unconditionally. The Skeptic — usually someone who was involved in the last project that went wrong — will find structural problems that are really political problems in disguise. And the Decider — usually the most senior person in the room — will wait to see which way the wind blows before delivering a verdict calibrated to minimize their own exposure.
Reading these dynamics is not cynicism. It’s survival. If you know who the Skeptic is before you enter the room, you can address their objection in the presentation itself — which is far more elegant than being ambushed by it during Q&A. If you know the Decider’s current anxieties (budget? board pressure? the campaign that blew up last quarter?), you can frame your idea in terms that speak directly to those anxieties.
Great internal pitches are not about the idea. They’re about the idea as it appears to each person in the room. You’re not presenting once. You’re presenting four times simultaneously, each version slightly different, to four people with different needs. This sounds exhausting because it is. It’s also the only way to actually get good work approved.
It’s related, in its own way, to presenting creative work without apologizing for it — except the internal pitch has the added difficulty that the people you’re presenting to are colleagues who will see you in the coffee queue on Monday, which creates a social complexity that external client relationships don’t carry.
The HiPPO in the Room
HiPPO stands for Highest Paid Person’s Opinion, and it is the single most reliable predictor of what will and will not be approved in any internal meeting in any organization in the world.
It doesn’t matter how many junior stakeholders love the idea. It doesn’t matter if the data supports it, if the creative team is unanimously behind it, or if the work is demonstrably better than anything the company has done in the last three years. What matters is whether the person with the most seniority in the room has a positive gut reaction to it. And that gut reaction is, more often than not, shaped by factors that have nothing to do with the quality of the work: their morning, their risk appetite, what their boss said last week, and whether the idea makes them feel clever for approving it or nervous that it might fail.
Managing the HiPPO is a skill that nobody teaches in any school or training program, and yet it is among the most valuable skills a creative professional can develop. The core principle is simple: give the HiPPO a way to make the idea their own. Not by changing the idea — by framing it in language that allows them to feel like they contributed to the strategic thinking. “This builds on the direction you outlined in Q3.” “You mentioned in the all-hands that you wanted us to take more creative risks — this is that.” “I know budget is tight, but this approach actually gives us more efficiency than the traditional route.”
Is this manipulation? Technically, no. Functionally, it depends on your tolerance for the word. Either way, it works. Good ideas need champions, and champions need to feel ownership. Give them that ownership and they’ll fight for the work. Don’t give it to them and they’ll find a reason to send you back to round two.
The “Devil’s Advocate” Moment
Every internal pitch has one. There will be a person — usually someone who has been in the company long enough to have opinions about everything but not long enough to have accountability for anything — who will clear their throat at approximately the two-thirds mark and say: “I just want to play devil’s advocate for a second.”
This is not devil’s advocacy. Devil’s advocacy requires genuine engagement with the idea on its own terms, followed by a specific, constructive objection. What follows “let me play devil’s advocate” is almost always one of the following: a reframing of the entire brief based on their personal preferences, a concern about a risk that has already been accounted for, a reference to a previous project that failed for reasons entirely unrelated to this one, or a question about budget that they already know the answer to.
The function of the devil’s advocate is not to improve the idea. It is to demonstrate independent thinking in front of the senior stakeholders, to signal that they are not just going along with the crowd, and — occasionally — to torpedo something they personally don’t like under the cover of legitimate skepticism.
Your job when the devil’s advocate appears is not to argue. It’s to listen, acknowledge, and neutralize. “That’s a fair point — here’s how we’ve thought about that risk.” “You’re right that the previous campaign had challenges in that area. Here’s what’s different this time.” Confronting the devil’s advocate directly makes them more entrenched. Absorbing their objection and showing it’s already been considered makes them seem redundant. One of these outcomes serves you better than the other.
Why Internal Pitches Kill Good Work — and What to Do About It
The brutal truth about internal pitches is that the process is structurally designed to produce mediocre outcomes. By the time a decision is made by consensus — which is what most internal pitches arrive at, because consensus feels safe — the original idea has usually been softened, hedged, or reframed to the point where the edge that made it good has been removed.
The organizations that consistently produce good creative work are the ones that have redesigned the approval process to protect the work from the process. Strong creative direction with real authority. Clear decision-makers who don’t require consensus from fifteen people. Pre-agreed criteria for what success looks like before anyone sees a concept. And a culture where “this makes me uncomfortable” is not treated as a veto — it’s treated as a sign that something interesting might be happening.
These organizations are rare. If you work in one, you know it and you’re grateful. If you don’t, you spend a portion of your professional life in exactly the kind of room we’ve been describing — presenting good work to people who have already decided, managing HiPPOs, translating devil’s advocacy into constructive feedback, and trying to keep the idea alive through rounds of attrition designed to make it harmless.
The workshop that produced forty-seven post-its and zero decisions is the internal pitch’s spiritual cousin. Both are symptoms of organizations that have confused process with progress. The difference is that the internal pitch has a moment of judgment at the end. That moment is an opportunity — but only if you’ve done the work before you walked in the room.
If you’re building something worth pitching — internally or externally — you might need tools that make the value of your work legible to people who think in spreadsheets and quarterly reports. That’s what KPI Shark is for. Because sometimes the best way to win an internal pitch is to speak the language of the room, even when the room doesn’t deserve it.
