Many digital projects start as good ideas but end up in long discussions, postponed decisions, and frustration. Not because the project does not make sense, but because decision-makers lack a clear, business-oriented foundation for saying yes. And this is actually where many digital initiatives lose momentum. You probably recognise the challenge.
When budgets need approval, it is rarely the technology itself that stops the process. It is the doubt. Uncertainty about impact, scope, risk, and financial implications. In some cases, it is also habits, culture, and organisational patterns where it simply feels easier to stick with what already exists.
We see it often. Projects can remain stalled for months because no one can clearly explain why the initiative matters, what it costs, and when the investment will generate returns.
A strategic decision foundation solves exactly that. Here is our guide to building a business case that makes decision-making easier.
Get from idea to decision (without writing 40 pages)
You might imagine that you need to produce a long and comprehensive report to convince management. But a decision foundation doesn't have to be heavy or academic. Quite the opposite.
The best approach is often the most practical. A document of 3–6 pages that describes:
- Why the project is necessary
- What business impact it will create
- How it will be realized
- How the company will achieve financial value
You can think of it as an internal business case that connects strategy, finance, and technology.
Start with the problem rather than the solution
The most important step is to describe the current problem or limitation. What does it cost the company to do nothing? This is where many people are surprised. Digital projects become much stronger when we start with the business - not the technology.
When we clearly articulate the problem, the challenge becomes visible to everyone involved. In many companies, for example, manual processes and long case-handling times mean that employees spend valuable time searching for information across multiple systems. This leads to delays, errors and a fragmented overview - and it makes scaling difficult because every new task requires additional handling and coordination.
Formulations like these create a shared starting point for leadership, IT and the business because the consequences become concrete and directly linked to operations and growth. At the same time, it helps make it clear that the status quo also has a cost - both financially and organizationally.
What do you want to achieve?
Once the problem is defined, you need to explain what the project is meant to improve. Not from a technical perspective, but from a business perspective. It could be faster response times, fewer manual processes, better compliance, or the ability to scale without adding more employees.
If the solution, for example, is a digital customer portal, the goal might be to create a central digital hub where both customers and employees can access data, status updates, and documents themselves. The effect is less manual handling and more consistent processes.
Four perspectives that strengthen your argument
When describing the impact, it helps to frame it through four perspectives. This gives decision-makers a more complete picture of the benefits:
People: Who is affected and which tasks become easier in practice? This could mean less manual work, fewer errors, better knowledge sharing, and more time for advisory work.
Processes: Which workflows will change or become standardised? Here, we can document processes, introduce automation and create a more stable operational foundation.
Customers: What difference will the customer experience? This could mean faster responses, greater transparency, better service experiences and a stronger digital customer experience overall.
Costs: What does it cost - and what does it cost to do nothing?
Investments should be evaluated not only against development costs, but also against lost hours, inefficient operations, and growing technical debt.
When we describe the project through these four lenses, the business case becomes more balanced and easier to understand for IT, business stakeholders, and finance alike.
How to make a business case concrete
A business case does not have to be complicated to be strong. We recommend making it highly concrete and, ideally, based on time and capacity - for example, how many hours can be saved, how many additional cases can be handled, or how much error handling can be reduced.
When we translate the impact into numbers, the value becomes easier to understand and compare with other investments. If manual processing is reduced by 20-40 percent, the company can in practice handle more cases with the same staffing level or free up the equivalent of 2-6 full-time positions over time.
This leads to lower costs, higher capacity and a more scalable operation - exactly the kind of argument that makes a business case convincing in an executive setting.
It can also be useful to address common objections. Often, they are not about the project itself but about uncertainty related to risk, implementation, and cost. A clear and concrete decision foundation helps reduce that uncertainty and brings the decision closer to action.
Start small and scale
Another important element is defining an MVP - in other words, the minimum the project needs to deliver in order to create value. In many cases, it can be beneficial to start even earlier with a Proof of Concept to test the most important assumptions before developing a full MVP. This reduces risk and makes the project easier to manage.
A typical roadmap might therefore include a short analysis phase, followed by a POC, an MVP, pilot operations, full implementation and later automation. This approach makes both the decision and the budget easier to approve and creates progress at a pace the organisation can realistically follow.
When ideas turn into action
Ultimately, it is not only about describing what we want to build - but why it creates value. When we help companies with this process, we often see that projects become less expensive over time once the decision foundation becomes clear. Uncertainty disappears, organisational habits are challenged and decisions are made faster.
A strong decision foundation is therefore not just internal documentation. It is the difference between projects that get implemented and projects that remain in PowerPoint.
How to write a decision foundation
If you want to start writing a decision foundation, you can use the structure below as a starting point. It is simple, direct and easy to adapt - which makes it effective.
The idea is that you can fill in the text almost as it stands and quickly create a coherent document that describes the problem, the solution, the investment, and the expected impact.
Below you will find an example where the sections are already formulated so they can be copied and adapted to your own situation. You can use it as a Word template, a presentation, or as an appendix to a budget request.
The most important thing is not whether you have all the answers right away, but that you create a clear narrative your decision-makers can relate to.
1. Background
The company currently experiences manual processes across multiple systems, making it difficult to maintain oversight, ensure efficient operations, and deliver a consistent customer experience. This creates a risk of errors, longer processing times and higher operational costs.
2. Purpose
The purpose of the project is to consolidate workflows, data, and customer access into a single solution. This will enable higher efficiency, faster response times, more consistent processes and provide a foundation for automation and self-service.
3. The Solution
The solution consists of a digital platform that gives customers and employees access to key information and documents. The platform will be built in a modular way, allowing functionality to expand over time, including self-service and automation capabilities.
4. Impact and benefits
The project is expected to reduce manual processing by 20-40%, free up resources, and improve scalability. It will also increase customer satisfaction, strengthen compliance, and create a stronger data foundation for decision-making.
5. Financials
The project will require investment in development and implementation. However, the costs are expected to be partially or fully offset
by reduced operational expenses, faster processes, and fewer errors.
6. Roadmap
The project will be carried out in phases, starting with analysis, followed by development of a minimum solution, pilot operation, and full implementation. The solution will then be evaluated and expanded.
7. Decision point
We are seeking approval of the budget and the development of a minimum solution in the first phase, with a planned expansion afterwards.
Ready to turn your idea into something concrete?
If you are working with a digital initiative where the purpose, financial case, or scope is still somewhat unclear, we are happy to help structure the decision foundation and build the business narrative needed to move the project forward.
We regularly work with companies looking to strengthen efficiency, customer value, and digital maturity. We are always happy to share methods, examples, and tools that help secure both budget and internal support for the next steps. Feel free to reach out if you would like to discuss your case or need help moving forward.