SayDigital has developed over the years an approach to software implementation, and odooin particular, in contrast with what typically happens on this market. Mostly we see our competitors offer a tailored approach, often comparing it to a dress or building house.
In these cases, most of the costs lying in lines of code with implementation projects lasting for months.
We identified 3 motivations that lead to this kind of approach,
A process should not by principle, be built based on the software used, but it is also true that it is necessary to be pragmatic. If you make shoes, does it really make sense to invest time and money in implementing your specific invoicing process investing weeks of development to adapt the software to your custom method?
Is it really the way you make invoices that creates your competitive advantage?
We have seen many companies using time, effort and money to customize processes with very low value leaving behind (or run out money for) what made them actually competitive.
Often there is the belief that in order to digitalize business processes, whatever the reason is (optimize resources, a better view of the company performance, integrate your service with external ones), it is necessary to buy a software.
Having usually more experience in the purchase of commonly used products (and not software), there is the tendency to follow some behaviours:
- at the same price, we want to get many features as possible (“Maybe someday, they will be useful!”)
- people want to pay one-off price ("So I don’t have to think about it anymore!")
- people tend to consider the software purchased as an investment in the future, like they were buying a house.
In our opinion, nothing is more wrong. You don’t need the software in itself.
What are you looking for is something that solve your current problems, possibly without creating new ones.
It is fundamental to understand that you are not paying a software, you are paying solutions to your problems. The difference might seem subtle, but it’s indeed crucial.
The world is changing at a speed never seen before. How many times have you heard sentences like this? Unfortunately or not it is true, even more in the IT world.
People know that, but sometimes there is the tendency to think that it concerns the rest of the world and not them. For this reason, one could tend to give high value to the software lifetime (sometimes endless), and words like “migration” scare most people.
"We bought this few time ago, why we have to change it?"
And it is known that often migrations cost more than the initial project.
After years and several implementation projects, we have learned that what it is really valuable for the client is not to have a costumed software. Our implementation method is very easy and is based on few principles fully embraced also by the Odoo philosophy.
As we all know, companies don’t have unlimited budget and quality software development has a cost. For this reason, our approach is to develop less and only when is really needed (for example, for features that create real competitive advantage)
Using a software like Odoo, with Apps covering every business activity, this principle is perfectly integrated.
We want to release value and not lines of code.
It is often underestimated that the project to implement new software in a company is not simply composed of software development activities. The introduction of a new tool generates opposition forces caused by the natural resistance to change. Aware of this, there is the tendency to replicate exactly the current activities in the new software, believing that the more alike the activities are, the lower the resistance will be.
However, often the system that we want to change is made of countless of unstructured tools (documents, excel sheets, emails, etc.). So we try to create a tool that allows to replicate the same activities, evidently not performing because based on unfit tools, in a software with different features form the tools used so far.
This implicate a considerable expenditure of energy on the development of unnecessary features because they emerged in a context in which the new software was not present.
We are aware that a new software inevitably affects operability, leading to the resolution of existing problems but generating also new challenges to face. For this reason, we try to guide the client in focusing the attention to the key activities, asking him/her in the initial stages to adapt to the ways adopted by Odoo that, with millions of installations, has gained experience to do it in the best of ways.
Even a perfectly developed software, with high quality and technologically advanced tools, has a limited life.
It is normal that this is so..
Technology evolves continuously and versions of framework or software that yesterday was secure, today are not anymore. Moreover, the software houses have started to apply fast deployment methodologies by continuously releasing new features at exceptional speed. For this reason, the market is requiring from software companies the release of main version more and more quickly, typically once a year, declaring to maintain support up to a maximum of two previous versions to make the maintenance sustainable.
Therefore, adopting a new software today means having a product in your hands that will be out of market, out of maintenance, and so obsolete, in two years. On the other hand, migrations to more recent versions often result in projects with higher costs than initial implementation project.
Many are not aware of this; we are. For this reason, when we project a new implementation we think also about the future impacts of any eventual migration to more recent versions. Odoo has fully embraced this principle and offers the possibility to automatically migrating to new versions (released every year) at a very low prize.
An Odoo customer will not run anymore the risk of having an obsolete version and will always benefit from the security, completeness and technology of the latest version released.
What is ODOO?