Getting Internal Buy-In: Sell the Problem, Not the Solution
Most proposals for new initiatives die not because they’re bad ideas, but because the person pitching them leads with the answer before anyone in the room feels the question. Internal buy-in is genuinely harder to get than external sign-off, partly because colleagues don’t have the politeness incentive that a vendor conversation creates, and partly because they already know where the bodies are buried.
The fundamental mistake: pitching the solution first
When you walk into a meeting with a fully formed proposal, a slide deck, and a recommended vendor, you’ve already lost a significant portion of the room. People who haven’t been on your journey through the problem don’t yet feel its weight, so your solution lands as an imposition rather than a relief. They’ll push back on the cost, the timing, the complexity, and they’re not fundamentally wrong to do so, because you haven’t given them a reason to care.
The more effective sequence is almost embarrassingly simple: spend the first part of any internal conversation establishing that the problem is real, quantifiable, and getting worse. Not by lecturing, but by asking questions you already know the answers to. A CFO who says aloud that the current reporting process wastes twelve hours a month has now said it, which is categorically different from you saying it on their behalf.
Who actually needs to say yes
One of the most reliable ways to stall an internal initiative is to pitch it to the wrong person first. Seniority on an org chart and actual decision-making authority over a specific budget are not always the same thing, and presenting to someone who can’t approve it but can quietly shelve it is a common and avoidable error.
Before you put anything in writing, map out not just who has formal sign-off but who has informal veto power, because in most organisations those are different people entirely. If a head of department is enthusiastic but the finance director sees the number and goes quiet, you haven’t got buy-in, you’ve got a hostage situation. Talk to finance early, even informally, and preferably before the cost appears in a document with your name on it.
What a credible internal case actually needs
It doesn’t need to be long. A twenty-slide deck is not more convincing than a clear two-page summary; it’s just more places to hide weak thinking. A business case that gets approved tends to answer four questions in plain language: what is the problem and how do we know it’s real, what happens if we do nothing, what are we proposing and roughly what will it cost, and what does success look like in measurable terms.
The costs and risks deserve their own honest paragraph. Not because you want to talk yourself out of approval, but because naming the downsides makes the benefits more believable. A proposal that acknowledges change management friction or a six-month bedding-in period reads as something a thoughtful person wrote, rather than something a hopeful one did.
The timing problem nobody talks about
Even a well-constructed case will fail if it arrives at the wrong moment in the budget cycle, immediately after a restructure, or when the person approving it is already committed to three other priorities that quarter. Internal timing is political in the least glamorous sense: it’s about knowing when the organisation has appetite, and that knowledge comes from conversation, not from analysis.
The most effective approach is to float the problem informally several weeks before you formalise anything, so that by the time you present a proposal, the people in the room have already been thinking about the issue and have partially arrived at the conclusion themselves. That’s not manipulation. It’s just how decisions actually get made in organisations, and pretending otherwise tends to produce a lot of beautiful documents that nobody acts on.