I've Pitched DevEx Budgets 12 Times (8 Approved, 4 Rejected)—Here's the Playbook That Actually Works

[vp_eng_keisha]

Over the past six years at three different companies, I’ve pitched engineering budgets to CFOs 12 times. Eight got approved. Four got rejected.

The four rejections taught me more than the eight successes.

Let me share the framework that’s worked to secure $7.2M in DevEx funding—and the mistakes that cost me $2.8M in rejected proposals.

The Framework That Works

Step 1: Establish Baseline (Before Asking for Money)

Don’t: Walk into the CFO’s office and ask for $500K based on “we need better tools”

Do: Measure current state for 2-3 months, then show up with data

What I track in the baseline phase:

• Deployment frequency (current: 2.1/week)
• Lead time for changes (current: 8.3 days)
• Developer time allocation (coding vs meetings vs waiting)
• Employee satisfaction (current NPS: 32)
• Incident rate and MTTR

Without baseline data, you can’t prove impact later.

Failed Pitch #2: I asked for $500K with no baseline. CFO said, “Come back when you can show me where we are today and where this investment will take us.”

She was right. I had no way to measure success without knowing the starting point.

Step 2: Find Your Business Case Anchor

Choose ONE primary argument:

• Hiring avoidance
• Retention improvement
• Time-to-market advantage
• Competitive positioning

All four are valid. But leading with multiple confuses the narrative.

Successful Pitch #5: Led with “hiring avoidance”

• Current team: 40 engineers, 15% below productivity benchmark
• Option A: Hire 6 more engineers ($1.2M/year ongoing)
• Option B: DevEx investment ($400K one-time + $80K/year)
• Payback: 8 months

CFO approved in 48 hours because the choice was obvious.

Failed Pitch #3: Led with 4 different arguments (productivity, retention, morale, quality). CFO asked, “Which one actually matters?” I didn’t have a clear answer.

Step 3: Size the Opportunity in Finance Terms

Show:

• Total investment (one-time + annual recurring)
• Annual benefit (cost avoidance + revenue acceleration)
• Payback period (months until break-even)

Payback timing matters:

• <18 months: Focus on execution risk mitigation
• 18-24 months: Sweet spot, focus on realistic plan

• 24 months: Need strategic justification (“competitive survival”)

My most successful pitches: 12-18 month payback with quarterly checkpoints.

Step 4: Build the Three-Tier Business Case

Present three scenarios:

Tier 1 (Conservative): 50% of expected benefits, still shows positive ROI

• Deployment frequency improves 15% (not 30%)
• Cost avoidance: $600K (not $1.2M)
• Payback: 20 months

Tier 2 (Expected): Realistic based on industry benchmarks

• Deployment frequency improves 30%
• Cost avoidance: $1.2M
• Payback: 12 months

Tier 3 (Optimistic): Best case if everything goes right

• Deployment frequency improves 50%
• Cost avoidance: $2M
• Payback: 6 months

Present all three. Commit to Tier 1. Get funded based on Tier 2.

This builds massive credibility. Shows you’ve thought through downside scenarios.

Step 5: Structure as Experiment, Not Commitment

Successful Pitch #7:
"I propose a 6-month pilot with clear kill criteria:

• If deployment frequency doesn’t improve 20% by month 6, we cancel
• If developer satisfaction doesn’t increase 25 points NPS, we cancel
• Quarterly OKRs with progress checkpoints"

CFO loved this. It gave her an “escape hatch”—not locked into multi-year commitment.

The pilot succeeded. Full rollout was approved immediately after.

Failed Pitch #4: Asked for $2M for company-wide rollout of unproven approach. Too risky. CFO wanted smaller pilot first.

Should have started with $200K pilot, then scaled based on results.

Step 6: Speak Their Language Throughout

Translation examples:

“Reduce cognitive load and improve flow state”
“Reduce context switching, saving 13 min/developer/week ($1.8M annually for our 40-person team)”

“Better developer experience”
“Reduce time-to-productivity for new hires from 6 weeks to 3 weeks ($400K saved across 30 annual hires)”

“Modern tooling”
“Competitive parity with tools that Big Tech offers—reduces compensation premium needed to attract talent ($450K saved across 30 hires)”

Same improvements. Finance-friendly language.

The Failures: What NOT to Do

Failed Pitch #1: Led With “Developer Happiness”

I opened with: “Our developers are frustrated with slow tools. This investment will improve developer happiness and morale.”

CFO shut it down immediately: “That sounds like happiness theater. Show me the business value.”

I didn’t have a good response. Pitch died in 10 minutes.

Lesson: Never lead with happiness. Lead with business outcomes. Happiness can be a secondary benefit, but it’s not the primary case.

Failed Pitch #3: Too Many Metrics

I showed 15 different KPIs: DORA metrics, SPACE framework, DXI scores, flow metrics, incident rates, etc.

CFO was overwhelmed: “Which of these 15 actually matters for our business?”

I tried to explain why they all mattered. Lost her completely.

Lesson: Show 3 metrics maximum. If they want more detail, have it ready. But lead with simplicity.

Failed Pitch #4: No Clear Ownership

CFO asked: “Who’s accountable for delivering this ROI?”

I said: “The platform team will build it, and all engineering teams will benefit.”

She pushed: “But who’s responsible if we don’t see the expected improvements?”

I didn’t have a good answer.

Lesson: Assign clear ownership and accountability. One person should be responsible for delivering the promised outcomes.

Failed Pitch #9: Asked for Too Much Too Soon

First DevEx pitch at a new company. Asked for $2M for a comprehensive platform engineering transformation.

CFO: “That’s a lot of money for something we haven’t proven here yet.”

Rejected.

Lesson: Start small. Win credibility with a $50K-200K pilot that delivers clear ROI. Then the $2M ask becomes easy.

Building Long-Term Credibility

Here’s what I wish I’d understood earlier: Your first DevEx pitch is about building credibility for your next pitch.

My strategy now:

First pitch: Small, certain, measurable win

• $50K for CI/CD improvement
• 4-month payback
• Clear metrics
• Massive credibility boost when it delivers

Second pitch: Medium investment, proven approach

• $300K for platform team formation
• Approved easily because first pitch delivered
• Credibility already established

Fifth pitch: Large strategic investment

• $2M approved with minimal scrutiny
• Track record speaks for itself

By the fifth pitch, the CFO trusts me. She knows I measure ROI rigorously. She knows I deliver on promises. The ask almost approves itself.

But if I’d started with the $2M ask? No credibility. Rejected.

Quarterly Business Reviews: Maintaining Credibility

Getting budget approved is Step 1. Delivering on promises is Step 2.

I report DevEx ROI in every quarterly business review:

Q1 Check-in:

• Deployment frequency: +18% (target was +20%, slightly behind)
• Developer NPS: +28 points (target was +25, ahead)
• Action: Investigating why deploy frequency behind target

Q2 Check-in:

• Deployment frequency: +32% (now ahead of target)
• Lead time: -41% (exceeded target of -30%)
• Business impact: Shipped Q2 roadmap 2 weeks early, launched revenue feature ahead of competitor

This consistent reporting builds trust. CFO knows I’m measuring rigorously and hitting targets.

If I missed targets without explanation, credibility would erode fast.

My Question to This Community

What’s worked for you in getting DevEx budgets approved? What mistakes did you make in your first pitch?

I’m always refining this playbook. Would love to hear your experiences—both successes and failures.

[cto_michelle]

Keisha, this playbook is exactly what I needed when I was struggling with DevEx budget approvals.

The “build credibility with small wins first” approach is brilliant. I learned this the hard way.

My Failed Big-Bang Approach

First DevEx pitch at my current company: Asked for $1.5M for platform engineering transformation.

Board response: “This is a lot of money for unproven ROI. What if it doesn’t work?”

Rejected immediately.

The Credibility-Building Approach That Worked

I reset my strategy. Started small:

First pitch: $80K for automated PR review tooling

• Clear problem: PR review time averaging 48 hours, blocking deployments
• Simple solution: Automated review, better templates, SLAs
• Measurable outcome: Reduce PR time to <6 hours
• Result: Achieved in 3 months, saved $240K/year in reduced cycle time

CFO noticed. I gained credibility.

Second pitch: $400K for CI/CD modernization

• Leveraged first success: “Remember PR automation delivered 3x ROI? This is similar scale.”
• Approved with minimal scrutiny because track record established

Third pitch: $2M for full platform team

• Referenced prior successes
• CFO: “You’ve delivered on previous investments. I trust you’ll deliver on this one.”
• Approved in first meeting

The lesson: First pitch buys credibility for subsequent pitches.

How to Maintain Credibility If Investment Doesn’t Deliver

You asked: “How do you maintain credibility if a DevEx investment doesn’t deliver expected ROI?”

I experienced this. One of my platform investments underdelivered:

• Expected: 30% improvement in deployment frequency
• Actual: 12% improvement
• Gap: 18 percentage points below target

Here’s how I maintained credibility:

1. Transparency: Report the miss immediately, don’t hide it

In QBR: “We missed target. Expected 30%, achieved 12%. Here’s why and what we’re doing about it.”

2. Root cause analysis: Show you understand WHY it underdelivered

“Analysis shows adoption was 60%, not 90% as planned. Teams needed more training and change management support than we anticipated.”

3. Corrective action: Present plan to close gap

“We’re implementing weekly training sessions and assigning platform advocates to each team. Expect adoption to reach 85% by Q3.”

4. Adjusted expectations: Revise forecast based on learnings

“Revised target: 25% improvement by Q4 (achievable with 85% adoption). Original 30% was based on 90% adoption assumption that proved optimistic.”

CFO appreciated the honesty and rigor. Credibility maintained because I didn’t try to spin a miss as a win.

The “Opportunity Cost” Dimension

One thing I’d add to your framework: Always address opportunity cost.

“What are we NOT doing if we invest in DevEx?”

CFOs think in trade-offs. Showing you’ve considered alternatives builds credibility.

Example:
"We could invest $500K in developer portal OR $500K in new product feature.

Feature revenue: $200K annually (uncertain, depends on market adoption)
Portal cost avoidance: $800K annually (predictable, based on ops time saved)

Portal has better ROI and lower risk."

When you proactively show trade-off analysis, CFO knows you’re thinking like a business leader, not just an engineering advocate.

[eng_director_luis]

The “experiment structure” approach is what unlocked DevEx funding for me.

At our Fortune 500, ALL engineering investments >$100K require pilot phase now. It’s company policy.

The Pilot-Then-Scale Playbook

My successful DevEx pitch:

"I propose a 3-month pilot with Teams A and B (20 engineers total):

Success criteria:

• Deploy frequency increases 40% (from 15 to 21+ deploys/month)
• Lead time decreases 30% (from 10 days to 7 days)
• Developer NPS increases 25 points

Investment for pilot: $60K

If we hit 2 of 3 success criteria, scale to full organization ($400K).

If we miss all 3, cancel investment and we’ve only spent $60K learning what doesn’t work."

CFO loved this structure. Low risk, clear criteria, escape hatch if it fails.

The Pilot Results

Month 3 results:

• Deploy frequency: +42%
• Lead time: -38%
• Developer NPS: +31 points

Exceeded all targets.

Full rollout approved in 24 hours after presenting results. No questions. Track record spoke for itself.

Contrast With Failed Approach

Previous failed pitch: Asked for company-wide rollout upfront ($800K), no pilot.

CFO: “What if this doesn’t work? We’re locked into a large investment with unclear ROI.”

Too risky. Rejected.

Same exact project, different structure. Pilot approach got approved, big-bang approach didn’t.

Executive Sponsorship Matters

One more critical factor: Get cross-functional executive support before going to CFO.

My successful pitches all had VP or C-level champions:

• VP Product supported platform investment (better velocity helps product goals)
• COO supported CI/CD modernization (operational efficiency)
• Head of Sales supported DevEx (faster shipping = win more deals)

When I walked into CFO meeting with 3 executives already aligned, pitch succeeded easily.

My failed pitch had only me (engineering director) supporting it. Not enough organizational weight.

Lesson: Build coalition across functions before formal pitch. If cross-functional leaders support it, CFO sees broader strategic value.

Template I Use

I created a one-page business case template:

Problem: [In business terms: revenue at risk, cost impact, competitive threat]

Solution: [Specific investment with timeline]

Investment: [Total cost: one-time + ongoing]

Return: [Annual value in cost avoidance + revenue acceleration]

Payback: [Months to break-even]

Risk: [What could go wrong + mitigation plan]

I lead with this one-pager in every meeting. Detailed analysis in appendix.

CFOs are busy. One-pager respects their time. If they want details, appendix is ready.

This format has gotten approved 8 times now. It works.

[product_david]

This framework applies to ANY investment pitch, not just DevEx.

I’ve used this same structure for product analytics, customer data platform, A/B testing infrastructure—all approved using similar approach.

The Comparative Framing That Works

What resonates with CFOs: Framing investments as choices, not requests.

Don’t say: “We need $500K for DevEx tools.”

Do say: “We can achieve X outcome through Option A (hire 5 people, $1M/year) OR Option B (invest in tools, $200K one-time + $50K/year). Which makes more sense financially?”

CFO always asks: “What’s the alternative to this investment?”

Bad answers:

• “Nothing” (then why is it needed?)
• “Just work harder” (not a real solution)

Good answers:

• “Hire more people” (tool is cheaper alternative)
• “Accept slower growth” (competitive risk)
• “Lose deals to faster competitors” (revenue impact)

When you frame the investment as “cheaper way to solve a real problem we have,” pitch succeeds.

When you frame it as “thing we want,” pitch fails.

Timing Matters More Than You Think

I pitched the SAME DevEx investment twice:

First pitch (September, during budget planning):
Rejected. “No budget available for new initiatives.”

Second pitch (January, after Q4 velocity became obvious problem):
Approved in 48 hours.

What changed? Nothing about the investment. What changed was TIMING.

In January, leadership was actively discussing “why did we miss Q4 roadmap commitments?” Velocity was top of mind.

My DevEx pitch directly addressed the pain point leadership was already feeling.

Creating Urgency

If things aren’t actively on fire, how do you create urgency?

Don’t: Manufacture artificial urgency (“We need this now or we’ll fall behind!”)

Do: Connect investment to existing strategic priority leadership already cares about

Examples:

• CEO frustrated about competitive velocity? Frame DevEx as “how we close speed gap”
• Board asking about engineering efficiency? Frame DevEx as “how we improve productivity metrics”
• Attrition becoming a problem? Frame DevEx as “retention investment”

Find the strategic priority. Connect your investment to it. Urgency is built-in.

The Question I Now Ask First

Before pitching ANY investment, I ask myself:

“What problem is leadership actively discussing this quarter?”

Then I frame my investment as solution to that problem.

This approach has 3x’d my approval rate.

[maya_builds]

Keisha, I’m saving this playbook permanently. The credibility-building approach is so smart.

Visual Demonstrations Change Everything

Let me add one tactic that’s worked surprisingly well: Show, don’t just tell.

For my design system pitch, I created side-by-side video:

• Left screen: Designer building feature with current tools (filmed over 12 hours, sped up)
• Right screen: Same feature with design system (filmed over 4 hours, sped up)

Watching the visual time difference made it tangible for our CFO in a way spreadsheets never could.

She said: “Oh, I actually SEE the 8 hours saved per feature now.”

Visual proof > Financial models (sometimes)

Anchor to Problems Leadership Already Cares About

David’s timing point is SO important. This was my biggest learning from my failed startup.

Failed startup pitch:
Tried to CREATE a new problem (“we need design consistency”).
Leadership didn’t care about that problem yet.
Rejected.

Successful company pitch:
ANCHORED to existing problem CEO was complaining about (“why do competitors ship faster?”).
Leadership already cared about this.
Approved immediately.

The lesson: Don’t create new problems. Solve existing ones that leadership is already losing sleep over.

Making DevEx Tangible for Non-Technical Executives

One challenge: CFOs don’t understand technical tools. They don’t know what CI/CD is. They don’t know why build times matter.

What worked: Use analogies they understand.

“Imagine if every time you wanted to update a financial model, you had to wait 2 hours for it to recalculate. That’s what our engineers experience with slow build times. This investment is like upgrading from dial-up internet to broadband for engineering.”

CFO got it immediately. Could relate to the pain point through analogy.

The Credibility Compounding Effect

Michelle mentioned this: First pitch builds credibility for next pitch.

I’ve seen this compound over time:

First pitch: Extensive scrutiny, lots of questions, conditional approval
Second pitch: Moderate scrutiny, approved after one meeting
Third pitch: Minimal scrutiny, “if you think it’s valuable, we trust you”
Fifth pitch: Basically auto-approved, CFO: “You’ve earned the trust”

But this ONLY works if you:

1. Deliver on previous promises
2. Report ROI rigorously in quarterly reviews
3. Are honest when something underdelivers
4. Adjust based on learnings

If you overpromise and underdeliver, credibility crashes fast and is hard to rebuild.

One More Thing: Make Measurement Part of the Initiative

Don’t treat measurement as afterthought.

When pitching DevEx investment, include in the proposal:

• 10% of budget allocated to measurement tooling
• 10% of timeline for baseline data collection
• Quarterly OKRs with specific numeric targets
• Clear success/failure criteria

This shows you’re serious about ROI, not just asking for money to try something.

CFOs appreciate the discipline. It shows you’re thinking like a business leader, not just an engineering enthusiast.