The nature of the relation
I would like to start writing about the most important topic, which is the nature of the relation between PeGon and our customers
Your code, and the documentation of the process around it reflects your company culture and essence. Our methodology assures that these two key elements remains present and always on your disposal. To do consultations, to review and improve it over the time, to use it with your own IT personal, ... always available for you.
Keep in mind that Odoo comes from a 100% open source solution even if now is slightly changed to an open-core solution. In essence accessing the code becomes crucial for you as customer
Employee and personal changes
We do understand that when you are choosing Odoo, you are not doing this for a short term decision. Definitive you are thinking in a long term relation and trust me, once you start using the product and get the benefits of it, then there is no roll back :)
But unfortunately and fortunately, people change, company changes, we as Odoo providers also evolve. It means our personal, your personal and our personal will change
Our methodology assures that the knowledge is not kept in a single person, or depends on a single role. Definitely this situation sometimes can be kept for a while, but when we are thinking in a long term relation, then we need to take action on it. Yes, but how do we do that?
Mentors
Now tell me if these topics or quotes does not sound to you :)
“This damned ERP is that big that sometimes I feel like I don’t know my own solution”
If your Odoo provider just acts as a software provider you probably are in a very big trouble, something that will not be noticed in the first 6 months of the project, but what about after three years?. Who is going to explain you how you are really working
"Oh damn it! John from Finance is on holidays and he is the only one who knows how to ...."
More of the same ...
"We have a brilliant developer who is taking care of everything. This guy is a monster!. You know, he even works on weekends"
Then feed him, and feed him and feed him, with more requests and without protecting yourself. Brace yourself and see how your project is about to die
"Python code is documentation"
The one who says these magic words inside the office, or even in the friendly Christmas company dinner, I promise he will be automatically fired iso-facto :)
Python code is not documentation, behind each python code portion there is an intention. Somebody will have to come after you and quickly understand what you have written... please, document the process behind that code. But not what the for loop does, but the human sense behind it!!!
We internally have strong rules to assure that the knowledge created flows so easily in between the contributors and from them to you
Summarizing
In PeGon we have created a methodology based on almost ten years of experience in Odoo that we believe is the key to satisfy the business necessities. Coming to the conclusion that your customer satisfaction is our main goal, your satisfaction with our services related to Odoo and once more, your satisfaction with our team.
Would you like to know more about who we are and how we can improve your business?
Just contact us!
Why PeGon is different?