Sovereignty and privacy start with the choice of software
Can I host it myself? That is the question you need to ask again.
Do you see this happening around you? Software is provided as a service (SaaS) hosted by the supplier. Initially, the price is reasonable and the supplier respects your wishes.
Do you see this happening around you? Software is provided as a service (SaaS) hosted by the supplier. Initially, the price is reasonable and the supplier respects your wishes.
Then the following happens:
- The hosting moves to a public cloud
- The company is taken over
- It becomes more expensive because it gets even better.
- Innovation stagnates or the product takes a completely different direction and is less efficient for your organisation.
- Vision and privacy disappear along with the old owners.
- You can hardly escape
- You switch to the next SaaS solution and go back to step 1
And that is why being able to host an application yourself is a good idea. And that does not automatically mean running the updates yourself. There are many ways in between.
This takes care of the privacy aspect and the hosting aspect. But not the risk of a changing vision and increasing prices. That can only be tackled when you own the software or it is Open Source. And also be aware that the software supplier actually prefers that you use the software in their cloud.
Do I have to have everything I use built?
No, I wouldn't do that. Let's primarily continue using accounting software for bookkeeping. The VAT return is quite complex, so it's not the place I would start. However, before an invoice is sent, there are numerous business processes that are either automated or could be. Perhaps even several standalone solutions that you may have adapted your business process to. And it's really not complicated to create an invoice in your accounting software from the built software. This could make the accounting software much simpler, which in turn saves costs.
Let yourself be helped in mapping your processes and start looking at where it can be automated. Start small but keep big ambitions.
Shouldn't you link software then?
Certainly. Fortunately, many software solutions offer an API (a data exchange interface), and even if that is not the case, we will find a way.
But isn't custom work a hassle?
The irony is that the custom work that is a hassle is usually built on a closed source environment and built as closed source. Sold as enterprise products with corresponding prices that also go through the steps mentioned above (better, more expensive, even better, even more expensive, lock). Exactly the reason why there are still computers running Windows XP.
Nowadays we use open source and open standards, and you simply get access to the code. The languages used are also important. Python, for example, is a language that is most commonly used and runs almost everywhere, and the same goes for the database. And we explain all of that in plain English.
I want custom work! How does that work with building?
There are a number of steps that we go through. We have, of course, written a nice document about that. Here it is in short:
First, we will discuss the ideal world. Imagine, there is nothing yet. What does your ideal software look like? Then we will divide it using the MoSCoW method into:
M- must haves: these requirements must be included in the final result; without these requirements, the product is not usable;
S- should haves: these requirements are highly desirable, but the product is still usable without them;
C- could haves: these requirements will only be addressed if there is enough time/budget;
W- won't haves (also known as Nice to haves): these requirements will not be addressed in this project but may be interesting in the future, in a follow-up project. How extensive this step is, of course, depends on how extensive the application becomes.
The next step is to create a graphic design. Indeed, we are still not making database designs and code choices. The end user is central. They need to work with it and have a pleasant flow. Then we will click through the final product, and only after approval will we start building. And that will go quite quickly because everything is clear.
And then you will have an application that fits your working methods, communicates with other applications, and is like a spider in your organisation and belongs to you. No one can raise the price or decide that it will run elsewhere.
You see, a lot has changed. Do you need help with your customisation? Don't hesitate toask us.