A funding playbook for VPs of Data who need a board to approve the next platform — cost of inaction, unit economics, phased ROI, and a legacy sunset plan the CFO can defend.
The board hasn't seen a platform proposal it would say yes to.
Boards do not approve technical projects. They approve a business case with unit economics, a payback period, and a number that gets sunset to help fund the new one. Architecture diagrams do not unlock the budget; finance does.
VPs of Data tend to overweight architecture and underweight finance in their proposals. The deck has more about Lakehouse vs. warehouse than about NPV, payback, and the cost of the next 18 months of inaction.
The first meeting is not a funding ask. It is a setup. The board sees the current cost of running the legacy, the revenue at risk, and the specific use cases the existing stack cannot serve. The ask comes next.
The second meeting is the proposal. It opens with the four numbers the board needs: total investment, payback period, NPV, and what gets sunset to fund part of it. Phased commitments lower the perceived risk and give the board genuine decision points along the way.
The proposal must tie investment to specific use cases that pay back. Three to five use cases is the sweet spot — enough to diversify the case, few enough that each one is real, sponsored, and signed off by the business owner who benefits.
The first meeting is not a funding ask. It is a setup.
The second meeting is the proposal. It opens with the four numbers the board needs: total investment, payback period, NPV, and what gets sunset to fund part of it.
The proposal must tie investment to specific use cases that pay back. Three to five use cases is the sweet spot.
If your data platform proposal has been parked for two budget cycles, the answer is not a longer deck.
Yes, when the phasing is real (genuine decision points, not ceremonial). We have not had a phased proposal declined when the first meeting earned the right to be heard.
Then the proposal honestly says so and asks for a different ROI hurdle. Boards respect honest framing more than optimistic claims.
The CFO is non-negotiable. The CIO or CTO co-presents. A business sponsor for each headline use case attends meeting two so the board hears the use-case math from the buyer, not the seller.
Joint sessions with the business sponsors before the second meeting. Each use case needs a sponsor who will sign off on the unit economics. Without sponsors, the case is hypothetical.
The phased structure absorbs the pushback. Phase 1 is a smaller commitment with a tight delivery window; phases 2 and 3 are gated by the results of phase 1.
