How to Get a Zero-to-One Initiative Funded in a Large Org

My first big proposal at a major company was a beautifully written strategy document. Thorough research. Clean formatting. Compelling vision. It sat in review for four months. Got deprioritized. Died quietly.

The next proposal I wrote — for a knowledge platform that had defeated every attempt for seven years — blazed through review in weeks. Not because the writing was better. Because everything that mattered happened before I wrote the first word.

What to Do Before Writing the Proposal

Here’s what the review committee saw: a strategy doc that was clearly grounded in real customer problems, had specific technical architecture, and already had buy-in from every stakeholder in the room. What they didn’t see: three weeks of me sitting with content authors at their desks. A dozen one-on-one conversations with directors and VPs where I said “here’s what I’m hearing — what am I missing?” A prototype I built that turned abstract concepts into something people could react to.

The document was the formality. The real work was the weeks before it existed.

Step 1: Listen Until You Find the Pain Nobody’s Articulated

Not the pain in the brief. The brief will say something like “we need a unified platform” or “we need better data governance.” That’s a symptom. The real pain is underneath.

On the risk data platform, the brief said “data governance.” The real pain was that a team had spent three years trying to land datasets by forcing upstream systems to change — and the business was making decisions across an $18 billion risk portfolio essentially blind. When I described that specific image to the VP — billions in risk exposure with no consolidated view — the conversation changed immediately. She didn’t need a market analysis. She needed someone to name what everyone already knew.

The real pain is always specific, always human, and almost never in the brief.

Step 2: Align People Individually Before the Group Review

This is the step that would have saved my first proposal. I walked into that review meeting cold. Half the room had concerns I didn’t know about. Territorial objections I hadn’t addressed. Questions I could have easily answered if anyone had asked them beforehand.

Now I never walk into a review meeting cold. Every stakeholder who matters gets a conversation first. Not the full document — just the kernel. “Here’s what I’m hearing from the teams. Here’s the direction I’m thinking. What am I missing?”

This isn’t politics. It’s respect. People support things they helped shape. When a VP sees their input reflected in the final proposal, they’re not just approving your idea — they’re approving their own contribution.

For the knowledge platform, I aligned 2 VPs and 8+ senior stakeholders individually before the formal review. The strategy doc went through “numerous reviews with leaders across multiple senior levels” without getting stuck. Not because it was a perfect document — because every person in the room had already seen their fingerprints on it.

Step 3: Build Something Before You Ask for Anything

This is the part where most people think I’m crazy. Before seeking full funding, I build a prototype. Not wireframes — working code with real design system components that engineers can start from.

The prototype eliminates the biggest objection to any new initiative: “we don’t know if this is possible.” When the room can see it working, the conversation shifts from “should we do this?” to “when can we start?”

But there’s a subtler benefit: prototypes expose your own wrong assumptions before you’ve committed budget to them. I’ve built things that proved my initial approach was wrong — and that was the most valuable thing they could have done.

Step 4: Make the Ask Small

The proposal that got stuck for four months? I asked for a full team for a year. The one that blazed through? I asked for a small tiger team for eight weeks.

Large asks trigger review committees, risk assessments, and competing-priority debates. Small asks get approved by the person in the room who can say yes.

Frame it as a time-boxed experiment: “Give me a small team for eight weeks. Here’s what we’ll deliver. Here’s how we’ll know if it worked. If it doesn’t, we stop.” That’s psychologically easy for a decision-maker. They’re not committing to a multi-year platform. They’re approving a sprint with a clear exit ramp.

Every large initiative I’ve launched started exactly this way. The results from the first sprint make the case for the next one better than any proposal ever could.

The Mistake I Keep Seeing: Cold Proposals

Teams write a proposal, present it to a room of people who’ve never seen it, and then wonder why it gets stuck. The proposal isn’t the problem. The process is.

If your proposals keep dying in review, the fix probably isn’t better writing. It’s more listening, more individual alignment, and a prototype that makes the abstract concrete.

I learned that lesson the hard way with my first proposal. The strategy doc that gets funded isn’t the best one. It’s the one where a VP looks at it and sees her own words reflected back — because you listened before you wrote.