IT requirements
How do you manage security ?
Find out here our security framework.
How do you manage scalability ?
Find out here how we ensure system scalability.
How do you manage availability ? What is the average uptime of the system ?
Find out here how we ensure system availability.
Doubts about choosing a ready-made solution rather than developing a proprietary solution
We want to own the source code
What really counts is the intellectual ownership of the part of your application that generates added value, such as data processing rules, algorithms, analytical functions, action recommendations.
This represents only a small part of the source code. Everything else is just a huge burden to maintain.
Servitly leaves you the owner of those parts.
We want to differentiate ourselves from our competitors
What makes the difference between you and your competitors is not how you write the source code of the application, but the impact it has on its users.
Does it give them useful information?
Does it save them time or resources?
Does it help them in their daily operations?
Does it support them in achieving the desired outcomes?
Servitly helps you focus exactly on those aspects.
We don't want lock-in with a supplier
In reality, even the source code does not free you from lock-in.
Instead of having a lock-in with the system supplier, you have it with the people who developed it. At the first staff turnover, you will have to manage the same kind of risk.
Servitly supports you in portability and handover.
We think the job is manageable, it's all about ‘making dashboards’
In reality, a DPS system supporting a winning product-service strategy is much more than ’making dashboards’.
You will have to build an enterprise application, with support for business workflows, multiple interfaces, demanding security, scalability and regulatory requirements, integration with information systems (CRM, ERP, ticketing).
If you think only about 'making dashboards', you are surely underestimating the effort.
We have already invested millions and it doesn’t make sense for us to change the approach
This is the most dangerous reason, and a well known cognitive bias: sunk cost fallacy.
Having invested millions in an ineffective solution is not at all a good reason to continue doing so.