Short answer
Describe a specific problem and the business benefit, prepare a technical description and scope of the solution, a cost estimate with justified items, a timeline and measurable results. A well-prepared project fits any programme — when one opens, you only need to adapt it to the specific rules.
What you need
1. Problem and goal. What doesn’t work today, what it costs and what the project will change. For example: “invoice entry takes N hours a month; the goal is to automate most of it”.
2. Solution description. What will be developed or introduced, which features and which integrations.
3. Technical specification. Detailed enough to justify the costs — see how to write a technical specification.
4. Cost estimate. By item: analysis, development, licences, rollout, training.
5. Timeline. Phases with results.
6. Results and indicators. Hours saved, fewer errors, faster service. See how to calculate the return.
The most common mistakes
- A description that’s too general (“we will introduce digitalisation”).
- Costs without justification.
- The project doesn’t match the programme’s goal or eligible costs.
How we help
We prepare the business case, the technical specification and the cost estimate, build the solution according to the approved project and prepare the documentation for reporting.