Implementing ERPNext in Practice
Every business is unique, at least in the sense that they play this game for profit. While there are differences between countries, industries, and enterprises, the fundamental processes are generally very similar. That's why it's advisable to review our own processes when implementing ERP, as they may not be optimal. Moreover, from different ERP systems like ERPNext, we can learn and apply best practices that have worked elsewhere.
If we can align with existing frameworks, it makes our job much easier. However, customizing ERPNext further allows us to better support the daily operations of businesses.
How We Work
The Monolithon team follows industry rules and best practices not only during development but also in the support process for implementation. To get the full picture, we examine how the business currently operates for those who want to use the ERPNext system. We also coordinate how they want to work in the future because this is an opportunity to refine their operations, not just digitize existing ones.
Based on this, it becomes apparent whether ERPNext is the right software for the organization. If not, we explore which other supported software might be suitable or one that we can provide support for. Once these decisions are made, we create a specific demo with the jointly selected potential dealbreaker functionality to see how it will work in practice, addressing any potential system-specific or challenging issues. This is not the full implementation, just a way to reduce both of our risks and determine if handling potential system-specific/difficult problems is possible.
Usually, the demonstrated solution is suitable, and we aim to allow the business to start using the software as quickly as possible, not with the complete implementation. This typically involves importing basic data and making basic settings, while parallelly configuring parameters, possible development, and training/documentation. After basic data, we focus on specific areas, often separate apps within ERPNext, such as project management, procurement, sales, CRM, etc. We usually deliver a new feature every week, making the system useful for the business quickly and getting closer to the final solution. This also allows us to make changes together along the way, as it is often necessary.
This implies that we don't prepare a complete specification in advance and don't price it because there are too many invisible factors better handled together flexibly. The risks are also financially managed by the monthly fee structure we provide, as there is no large upfront investment, but there is continuous progress. The agreed-upon hours are typically spent more in the first implementation phase, and then in the operational phase, if it's balanced, we reduce the hours, with daily and monthly reports. If the client needs more support, we can collectively adjust the hours upward, making it predictable for everyone. It doesn't get lost and can be used for a later upgrade, typically needed annually.
Guarantees
Regarding ERPNext, it's worth mentioning that besides being free and open-source, professional partners can assist in the introduction, and there are product guarantees available. Furthermore, Monolithon collaborates with several partners for the acquisition of existing solutions, avoiding the need to develop them from scratch. Additionally, we use this network for providing extra development capacity and quality assurance, both for our benefit and our clients.