We notice that an idea at it’s core always can be reduced into the following 2 categories:

• The simplification of processes or a working method to make it more efficient.

It always falls into at least one category, but sometimes an idea does both. What is important here is that you know the fundamental reason behind your idea.

Sometimes there is also a need for software to update an existing software product, because it no longer meets today's standards or because security risks arise. We don't really see this as an idea. At least, not if it has to be taken over 1 on 1. However, we have never experienced a software renewal process in which no improvements are proposed. So then the question is, what is the underlying question of the idea relevant again.

Why is it important to know your idea's background?

1. You want to be able to estimate/calculate whether the costs you incur for software are in line with what you expect to be able to save or earn.
2. It helps you estimate what you are willing to spend for a solution.
3. The underlying idea, we lay the foundation for the prototyping part, so that it is clear for the user experience what we are trying to achieve.
4. It ensures a common approach in which you as a customer and we as a software development partner are on the same page because we understanding the approach.
5. It generally provides greater clarity on what you are trying to achieve.

Answering the above points is important, but we understand that you may need a helping hand with this. Fortunately, we have experience with this and we help you with our feasibility phase (step 2) to get this clear.