Odoo Implementation isn’t a one size matches all process. There are many variables that you need to think about and a good quantity of difficult questions you must ask earlier than implementing. In the previous few years I’ve built most likely 40–50 Odoo implementation quotes. Each estimate is just a little totally different based mostly on the project however I’ll try to define the metrics that I use.
Odoo Implementation is very very like constructing a house. You can hand the same set of necessities to totally different partners and get back vastly totally different estimates. The query you have to ask, is would you like the spec home or the customized home when the projects over? The fact is, even a number of the wildly low implementation quotes I’ve seen are given in good religion, nevertheless it’s as much as you to know what you’re getting when one partner quotes 50 hours and the other quotes 300 hours for a similar project. The distinction in these is the quantity of discovery, training, and care you’ll receive along the way. Both of the tasks will seemingly find yourself with a “working” model of Odoo together with your data and usually working ideas. The distinction is within the finishes.
Our Estimation Method
I’ve developed an estimating device in excel that enables me to plugin a few items of data and it helps me to provide you with a starting point. From there, the maths needs to be interpreted right into a quote based mostly on conversations with the prospect and their necessities which might be much less easy to estimate. These items are actually the finishes that I discussed in my home development analogy.
Here is the data I take advantage of to construct a quote:
1. The Apps List
2. Number of Users
3. Number of Systems Replacing
4. Known Gaps / Customizations
5. Go-Live Date
6. Gut (Experience)
The Apps List
The very first thing we need to know when constructing an implementation estimate is the apps that you simply intend to use in Odoo. This easy piece of data in fact opens a world of different questions however its a vital first step. By simply seeing this record, I’m able to understand the level of complexity of your small business.
In my quote device, I’ve an inventory of practically each out of the field setting in every app. I’ve some pre-assigned values based mostly on historic outcomes for every setting within the system and we set hours for documentation & training as a % of the invention and configuration.
I can then pivot the variety of hours for every module / function right into a master estimated variety of hours per module that’s the foundation for our estimate.
Number of Users
After we know the record of apps, one other vital piece of knowledge is the variety of customers. There is little distinction in Odoo Implementation for 20 users versus 30; however there’s a huge distinction between implementing for 20 vs. 100. Some of the extra implementation expense on a 100 user system could be offset by the clients internal resources. For instance, a client who adopts a “train the trainer” mentality can usually implement Odoo for a lot less than one which expects their partner to do all training.
Number of Systems Replacing
Due to Odoo’s breadth of functionality, we usually change a minimum of two, and as many as six systems throughout implementation. This might be things like core accounting, project administration, expense reporting, entry databases, enterprise chat, quoting techniques, and so forth.
If we’re changing a number of techniques, you’ll be able to typically anticipate the information conversion to be more advanced. On a current undertaking we got buyer knowledge from two techniques and needed to manually merge it earlier than importing to Odoo. This shouldn’t be an un-common scenario and we’re happy to do it however if you don’t have the group to do the data cleanup before handing it to us, expect to pay further for that effort. Contrast that example with another current undertaking the place the client left SAP for Odoo. This buyer, whereas considered one of our bigger tasks, was very environment friendly as a result of the customers anticipated a single data supply and understood ERP ideas. This made the project easier and the information migration was all from a single location to a single location.
Known Gaps
During our initial conversations about how you plan to make use of Odoo, I can usually ask enough questions to know where the gaps might come into the project. This can reveal itself in demos and in depth conversations through the pre-sale. When offering an estimate for implementation we at all times define and estimate the identified gaps up entrance. Obviously, issues can come up through the undertaking that weren’t identified in advance nevertheless it’s useful to put as a lot on paper up front as possible.
Go-Live Date
Setting a date on the calendar is an efficient technique to generate a good estimate, because time can typically be a fantastic motivator. We have completed implementations in only a few weeks when shoppers had been up towards a software program renewal, sale of a enterprise, or different circumstances. In these circumstances, the period of time accessible is a big driver in the price. Clients which might be non-committal to a go-live date are likely to spend extra as a result of they need to maintain out on going stay till they get everything simply excellent, which is certainly the “custom home” route.
Gut (Experience)
In the end, the final number is subjective to my total impression of the clients readiness for change, willingness to take recommendation or take no for a solution, and their capability to do a few of the heavy lifting. No two projects are the same, and you must reject any partner who gives that impression through the quoting process.
Every client has their strengths and weaknesses that they bring to the project. In some circumstances we will leverage specialists on their employees to export, format, or normalize knowledge. In different circumstances, we all know from the primary assembly that there are key players on their employees which are going to fight the project from day one. These variables simply go into the expertise column when quoting an implementation.
Business solution-centric Odoo Consultant and IT professional with about 11+ years of experience spanning Odoo delivery, Sales, pre-sales, Odoo product development, Odoo business consulting, outsourcing & ADM services in leadership positions.
• Has headed Practices for Enterprise Solutions ( SAP, Baan & Odoo )
• Experience across domains likeSales and Marketing, Logistics, Manufacturing, Retail, Chemical, Automotive maped to Odoo
• Extensive experience in large program delivery & business process transformation consulting (Odoo Consultant) for multiple programs
• Demonstrated experience in designing new product & service offerings and executing global Go-To-Market strategies for new offerings for new market penetration
• Proven leadership skills with balanced focus on people, processes & technology
• Pioneered the use of ERP systems in various Processing Industry
• Worked as Process Heads of Marketing, Sales, Purchase, HR, ERP Project deliveries and also worked as Business Heads for many companies like IBM, JKT, Denave India, FCS and presently at Apagen
Post new comment
Please Register or Login to post new comment.