Executive Careers with Fexingo · 2026-06-30 · 9 min
Key moments - from our scoring
Substance score
57 / 100
Five dimensions, 20 points each
Most senior leaders fail to secure internal budget and headcount not because their ideas are weak, but because they frame requests as personal asks rather than investment opportunities. Lucas and Luna explore how borrowing the venture capital deal memo structure transforms these conversations. A deal thesis replaces feature lists and Gantt charts with five core sections: Strategic Context (anchoring to an external or internal change the organisation already recognises), Investment Thesis (3-5 specific, data-backed reasons this solution beats alternatives), Financial Model (investment required, operating costs, projected returns, payback period, and sensitivity analysis), Execution Plan (milestones and decision gates, not timelines), and a phased Ask. The framework is illustrated through James, a VP of Data who secured $2.3 million by presenting three options - do nothing (costing $800K annually in inefficiencies), a half-million stopgap, or the full build - rather than requesting a single path. The structure depoliticises the pitch, lowers perceived risk through staged gates, and forces clarity during the writing process itself. Organisations of any culture - family business, non-profit, or startup - can adapt the language without abandoning the logic.
Start with Strategic Context (anchoring to CEO priorities or external change), then Investment Thesis (3-5 specific, data-backed reasons this solution wins), Financial Model (investment, costs, savings, payback period, sensitivity), Execution Plan (milestones and decision gates), and a clear phased Ask - all on one page with appendices for detail.
Instead of listing technologies and timelines, James presented three options: Option A (do nothing, costing $800K yearly in inefficiencies), Option B (a half-million quick fix lasting 18 months), and Option C (the full $2.3 million build delivering ROI in under 3 years and enabling personalised marketing, the CEO's priority). The structure showed he'd thought through trade-offs and made it hard to reject.
Three options make the decision feel analytical rather than political, give executives permission to say yes by allowing early gates and kill switches, and quantify the cost of inaction - making it harder to reject the proposal without also rejecting the measured consequences of doing nothing.
One page maximum for the executive summary that circulates; appendices can provide backup detail, but the core argument must fit on a single page, which forces you to prioritise the three benefits that matter most.
Yes - adapt the language (call it 'One-Page Opportunity Summary' in a family business or use 'mission impact per dollar' instead of ROI in a non-profit) but keep the logic structure of context, thesis, financials, plan, and ask.
Our reviewer’s read on each dimension, with quotes from the episode.
The episode delivers a clear, structured framework (Strategic Context, Investment Thesis, Financial Model, Execution Plan, Ask) with specific tactical advice on deal thesis framing for internal pitches. However, much of the content is moderately predictable application of VC concepts to internal corporate contexts, and there is filler including a coffee donation pitch and some repetitive reinforcement of points already made.
you need to answer: what is the external or internal change that makes this the right moment?
reduces data processing time from three hours to fifteen minutes, enabling same-day campaign adjustments
The core idea of applying VC deal memo structure to internal corporate pitches is somewhat fresh, but the execution relies heavily on well-known principles (depoliticizing asks, quantifying trade-offs, risk sensitivity). The framework itself is borrowed directly from venture capital with minimal novel insight into how it specifically surfaces breakdowns in organizational decision-making.
you're not asking for a favour, you're presenting an investment opportunity with a clear risk-return profile
The writing process itself is a vetting process
The episode features only two hosts (Lucas and Luna) with no identified external guests. While they appear to have some professional experience, their credibility is not established and they rely on a single anecdotal example (James at a retailer) without demonstrating direct operational scale or recognized expertise in organizational decision-making.
A few years ago, a colleague of mine - let's call him James - was a VP of Data at a mid-sized retailer
Honestly, if an episode like this helps you save weeks of back and forth in your next budget cycle, that's exactly the kind of value we try to deliver
The episode provides one concrete example (James seeking $2.3M for data infrastructure, with specific numbers like $800k annual inefficiency and 18-month quick-fix option) and specific tactical details (three-hour to fifteen-minute processing improvement). However, it lacks multiple named case studies, industry benchmarks, or evidence of how frequently this approach succeeds across different organizational contexts.
He needed two point three million dollars to build a new data infrastructure layer
losing around eight hundred thousand dollars a year in inefficiencies
The dialogue is well-structured with Luna offering thoughtful pushbacks and extensions (e.g., questioning Wall Street jargon in non-profits, suggesting sensitivity analysis, noting the hidden benefit of the writing process). However, there is limited genuine challenge to Lucas's assertions, and the conversation remains largely confirmatory rather than exploratory, with no moment where a claim is seriously disputed.
but isn't there a risk of sounding too Wall Street when you're talking about, say, a new CRM system?
I'd add: include a sensitivity analysis. Show what happens if the projections are off by twenty percent
Computed from the transcript - who did the talking, and the words that came up most.
Episode 84 of Executive Careers with Fexingo: How Senior Leaders Use Deal Thesis Framing in Internal Pitches. Lucas and Luna explore how experienced executives borrow the venture capital 'deal thesis' structure to make internal resource requests more compelling and less political. Lucas shares a specific example: a former colleague who secured $2.3 million for a data infrastructure project by framing it as a three-option investment memo with clear payoff timelines. Luna challenges whether this works in non-profit or government settings. Lucas offers a concrete adaptation: replace 'ROI' with 'mission impact per dollar.' The hosts also briefly discuss how listener support through buy me a coffee dot com slash fexingo keeps the show ad-free. This episode is for senior leaders who want to depersonalise budget negotiations and make their next big ask feel like an opportunity, not a favour.
Transcribed and scored by The B2B Podcast Index.
Lucas: You know, I've been thinking a lot about how senior leaders ask for resources internally - whether it's budget, headcount, or a strategic pivot - and how often they get a 'no' not because the idea is bad, but because the framing is weak. Luna: Yeah, I see that all the time. People show up with a deck full of features and timelines, but they never answer the one question the CFO actually cares about: why this, why now, and what's the expected return? Lucas: Exactly.
And that's where I think senior leaders can borrow a tool from venture capital: the deal thesis. In VC, you never pitch a startup by just listing its features. You write a thesis that explains the market gap, the unique solution, the unit economics, and the exit path. Luna: So you're saying executives should treat an internal proposal like a VC deal memo?
That's interesting - but isn't there a risk of sounding too Wall Street when you're talking about, say, a new CRM system? Lucas: That's the right pushback, and I think the key is to adapt the structure, not the jargon. You don't call it 'exit path' in a non-profit boardroom. But the logic still works: what's the problem, why is this the best solution, what's the investment required, and what's the measurable outcome in twelve months?
Luna: Okay, so give me a concrete example from your own experience - when did you see someone nail this? Lucas: A few years ago, a colleague of mine - let's call him James - was a VP of Data at a mid-sized retailer. He needed two point three million dollars to build a new data infrastructure layer. His first version of the pitch was a list of technologies and a Gantt chart.
It went nowhere. Luna: Classic. So what did he do differently? Lucas: He went back and wrote a one-page investment memo.
He framed it as three options: Option A was doing nothing - which he quantified as losing around eight hundred thousand dollars a year in inefficiencies. Option B was a half-million quick fix that would only last eighteen months. Option C was the full two point three million build that would pay for itself in under three years and enable the company to launch personalised marketing, which was the CEO's top initiative. Luna: So he gave them a choice, not a request.
That's smart - it makes the decision feel analytical rather than political. Lucas: Exactly. And that's the core of deal thesis framing: you're not asking for a favour, you're presenting an investment opportunity with a clear risk-return profile. The CFO later told James that the three-option structure was what sold it, because it showed he'd thought through the trade-offs.
Luna: That kind of framing also protects you if someone says no - because you've already laid out the cost of inaction. It's harder to reject a proposal when you're also rejecting the quantified consequences of doing nothing. Lucas: Right. And that's one of the reasons I find this approach so useful for senior leaders.
When you're at the VP or C-suite level, your political capital is finite. Every pitch that gets framed as a personal ask chips away at that capital. But a well-structured deal thesis - it depersonalises the whole thing. Luna: Honestly, if an episode like this helps you save weeks of back and forth in your next budget cycle, that's exactly the kind of value we try to deliver.
And if it's worth a coffee to you, you know where to find it - buy me a coffee dot com slash fexingo. Lucas: Yeah, listener support is what keeps this show ad-free and allows us to spend time on these deep dives. So thank you to anyone who's already contributed. Now, let's get into the nuts and bolts of how you actually write a deal thesis for an internal proposal.
Luna: Good. So what's the first section? Because I imagine it's not 'Executive Summary.' Lucas: No.
The first section should be the 'Strategic Context.' You need to answer: what is the external or internal change that makes this the right moment? Is it a competitor move, a regulation change, a customer behaviour shift, or a new strategic priority from the board? Without that context, your proposal feels like a solution in search of a problem.
Luna: So you're anchoring it in something everyone already agrees is important. That's clever - you're not fighting for attention, you're riding a wave that's already moving. Lucas: Exactly. For James, the strategic context was the CEO's public commitment to personalisation at the last all-hands.
He literally quoted the CEO's own slide. That made it almost impossible for anyone to argue against the project without contradicting the CEO. Luna: That's a pro move. Okay, so after strategic context, what's next?
Lucas: The second section is the 'Investment Thesis' - three to five bullet points that explain why this specific solution is better than alternatives. Here you want to be specific: not 'improves efficiency,' but 'reduces data processing time from three hours to fifteen minutes, enabling same-day campaign adjustments.' Luna: And you need to back that up with data, not vendor promises. Lucas: Right.
If you can't bring at least one credible data point - a pilot result, an industry benchmark, a reference from a peer company - then you're not ready to pitch. The third section is the 'Financial Model.' This doesn't need to be a hundred-row spreadsheet. It can be a simple table: investment required, annual operating cost, projected savings or revenue lift, and payback period.
Luna: And I'd add: include a sensitivity analysis. Show what happens if the projections are off by twenty percent. That signals that you've considered risk, which builds trust. Lucas: Great point.
The fourth section is the 'Execution Plan' - not a Gantt chart, but a timeline with milestones and decision gates. The CEO wants to know: when will we know if this is working? What's the first test? What's the fail-fast trigger?
Luna: That also gives the executive team permission to say yes - because they can always pull the plug at Gate Two if the early results aren't there. It reduces the perceived risk. Lucas: Exactly. And the final section is the 'Ask and Next Steps.'
This should be one clear sentence: 'I'm requesting approval to proceed with a ninety-day discovery phase for two hundred thousand dollars, followed by a full proposal for the remaining two point one million.' That way, you're not asking for everything at once. Luna: So it's a phased ask. That's a great way to lower the barrier.
Now, what about people who say, 'My organisation doesn't work that way - we're a family-owned business or a non-profit, and they'd laugh at a deal thesis.' How do you respond? Lucas: I'd say the format adapts, but the logic is universal. In a family business, you might call it a 'One-Page Opportunity Summary.'
For a non-profit, you replace ROI with 'mission impact per dollar.' But the structure stays: context, thesis, financials, plan, ask. The language changes, not the thinking. Luna: I like that.
And I'd add that even if your culture is very relationship-driven, a written deal thesis forces you to clarify your own thinking. It's as much a tool for you as for your audience. Lucas: Yeah, I think that's the hidden benefit. When you sit down to write a deal thesis, you quickly discover which parts of your argument are thin.
Maybe you don't actually know the payback period. Maybe you haven't thought about what happens if the vendor goes out of business. The writing process itself is a vetting process. Luna: So let's talk about a common mistake: people write a deal thesis that's too long.
What's the right length? Lucas: One page. If you can't get the core argument on one page, you don't understand it well enough. That doesn't mean you can't have appendices - but the executive summary that circulates should be one page.
James's one-page memo was the document that got circulated before the meeting. The rest was backup. Luna: And one page forces you to prioritise. You can't list seven benefits; you have to pick the three that matter most.
That discipline alone improves the quality of the pitch. Lucas: Totally. So to wrap this part, I'd say: if you're a senior leader preparing a major resource request, spend the time to frame it as a deal thesis. It will make you sound more strategic, depoliticise the conversation, and increase your odds of getting a yes.
And if you get a no, at least you'll know exactly why - because the thesis lays out every assumption, and the decision maker has to show you which assumption they don't buy. Luna: And that's valuable feedback even if you don't get the budget this time. It tells you what to work on for next quarter. Lucas: Exactly.
So, next time you're about to build a forty-slide deck, stop. Write one page. Frame it as a deal. See what happens.
Luna: I love that. And for those of you who want to see a template, we'll link to a sample deal thesis framework in the show notes. Until next time, keep thinking like an investor in your own career.
Other episodes covering the same guests and topics, from across The B2B Podcast Index.