You have a data project that makes complete sense — but the board asks "how much does it cost and what do we gain?" and the conversation stalls. Knowing how to justify the budget of a data project in business language is what separates good ideas that move forward from good ideas that die in a drawer.
Why data projects are hard to sell
Unlike buying a machine, the return of a data project is often indirect and future: better decisions, fewer errors, more agility. That is real, but it sounds vague to whoever controls the budget. The challenge is not the value — it is communicating it in terms the board recognizes.
Speak the language of decision-makers
The board thinks in revenue, cost and risk. Translate your project into those terms: not "we will have a data warehouse", but "we will cut the monthly close by X hours and recover Y in billing lost to errors". The same project, told in business impact, gains a different force.
Structure a convincing proposal
- The problem in euros: how much doing nothing costs today (wasted time, errors, opportunities).
- The solution and the cost: what you propose and the total investment, including maintenance.
- The expected return: concrete gain and when it appears, with conservative gains.
- The risk of not doing it: what happens if everything stays the same.
Start small to prove value
It is easier to approve 20k for a pilot with a return in three months than 200k for a two-year transformation. A first case with a measurable result builds the credibility — and the budget — for the next steps. Show value early, and the rest follows.
Promise what you can measure
Nothing kills trust like a project that promised revolution and could not show a result. Promise gains you can measure and then show you hit them. A proven win is worth more for the next budget than ten ambitious promises.
In practice
Before asking for budget, write the problem in euros, the expected return and how you will measure it — on one page the board understands without knowing technology. That translation is half the approval. Is your next data project described in business impact, or in technical jargon?
