ROI Analysis: Everything you need to know as an Odoo Partner

hello everyone so we are all here to discuss a bit on how to perform and what everything you need to know about the new era analysis so my name is greg and i'm a business service manager at odoo responsible for all the pre-sales activities and all the the corporate project activities as well so today we will focus on different elements around the era analysis so why did we should switch from the gap analysis to the ri what is exactly an error analysis when to sell it how to sell it and why doing it and then

to conclude we will go over different tools we have to define how to perform those kind of analysis so first why did we decide to change from the old gap analysis to the new era analysis so we wanted to change the client perception of the document we gave them about their project with the gap analysis what we had inside this document was i can say mainly negative in the way that we only focus on the money they need to put on the table to get their project delivered knowing that so the output of this document

was only a list of requirements detailed estimated and to define the cost of the project and the planning and we were feeling that we were missing a big part uh of this process to highlight what odoo can bring to the company that's why here we add on top of the gap analysis a new layer focusing on the return part of the of the audu project where we list the inefficiencies that we can identify during the different workshops and provide some ways to solve them we also define some saving and performance optimization and we redefine what

audu can bring to the company so here we really focus on what odoo can bring to the company so we provide a more positive i can say aspect of this phase where people might feel that we only invest some time just to define the final budget so here with this phase we will go into much more detail in the way we can improve the day-to-day life and the day-to-day job of every worker within a company so the i would say one possible definition of the analysis it's a pre-sale phase where we analyze every process of

a company and we also analyze the day-to-day work of every worker or every key worker within the company so we have two main focuses the first is what odoo can bring to the company so the rsi the return we measure all the impact odu can have on the company and uh the other focus is the endless investment that the client needs to do to have his project deliver so the all that can say file you all uh all know so all the cost aspects of the eye side of the return of on investment analysis here

also depending on the size of the potential project and the size of the company we can go for a dedicated phase or we can include this array phase within the first call or the kickoff call where we have i can see a small project where we will i can say mainly stick to the standard feature of odoo so for a bigger project or a bigger implementation in company we really dedicate an entire phase where we go over every detail every aspect of this uh this phase to deliver a good document and a good output to

the company speaking of the output so what we will deliver with this era analysis document is the list of inefficiencies and their solution of course the estimate of the possible time allocation optimization that we can bring with audio of course the project definition the planning and the budget so next question when to sell an error analysis of course here every project should include at least one part of this error analysis at least the feasibility analysis to redefine if the project is feasible based on what we agreed uh like on the phone or during the negotiation

phase when we decided to go with a dedicated phase we want to sell this uh our analysis to show and convince that audu can bring a lot to the company so it's the opportunity to make several demonstrations to illustrate that audu can fit with the different needs of the client and also to take the chance to study a bit more the different process and the way the the worker are working inside the company to see how we can improve this way of working we're also advise to sell it and to have a dedicated phase when

the projects have a complex scope or when the pro the project might have a high volume of development so just with after a small discussion with a client who might already anticipate that we might need several uh days of our of development so that's where it's important to get this pre-sales phase where we'll detail all these requirements and see how we can challenge them and make them as standard as possible it's also important to sell this kind of analysis when you have to communic to commit or to communicate on a planning and on a budget

because here you will go over every request of the client you will put some number behind every request so you will be able to define a proper planning and then a proper budget without that it's like yeah making it a difficult promise to maintain in the time so it's important to have this good face to give some right information to the end client an important topic is that the time required for such analysis compared to the gap analysis is not significantly longer to take some example we had recently we had a gap an error analysis

that length for more than two months and we add one day or two just to focus and to review the the return part and make this additional layer out of the the old gap analysis just to refocus on this so we only add a small percentage of the on the budget to tackle this new phase so how to sell it so here what we discuss with the client where when selling uh neural analysis is that we will want we want to have two consultants to perform all the workshops just to ease the communication flow to

be able to ask all the right questions and having the ability to take some notes and to challenge all the time every request made by the client so having two consultants he's the the conduction of the workshops and you have a better quality at the end you can you have also to adapt the budget to pro to the client based on the workshops uh output as by the client meaning that you can decide to go for meeting minutes just a summary of the note you have taken during the workshops or to have detailed report to

redesign and explain how you will implement the solution at the end and to explain every complex topic i would say in detailed documents or simply saying that there is no intermediate output or intermediate document except the final roi file and you have also to include in this budget the internal peer reviews where you will challenge yourself against colleagues just to reduce the implementation budget but then you have to include that phase and those elements within the initial budget of this error analysis so to estimate a bit the time required for such an analysis we have

built a small excel file where we defined the number of consultants we have to put on the the analysis the number of days of for each functional workshops so here you just count the number of department and you split a bit the different workshops you wanted to tackle during this phase some technical workshops as well if you need to make some integration with external software if you need to assess the environment the platform and so on you can define that as well if you need some light medium or uh heavy preparation meaning that maybe the

client already sent you a lot of document you need to ask a lot of questions to the client to help him to prepare the the workshops so all this time can be taken into account to provide a good estimate of the entire uh process and so you can define the proper budget for the this dedicated phase as well so here yes you just compile everything in one table and then you have the budget information so here why doing this ri analysis so depending on the role you you are so here even if you are the

partner or the client you might have different insight in doing the error analysis on the partner side this tool can help you a lot to convince your client meaning that you have it will be a good tool to show him that audio can fit to the company it will also help you to sell the audio project as an investment and not only a cost because you will not only focus on estimating the requirement to put inside odo but you will also insist on what odu can bring to the overall company and across the different department

it's also the opportunity to explain and set up the audio methodology and the audio mindset so that's where you will explain how you can conduct a project you can also apply this mindset of challenging every request to make them as standard as possible during this phase so to put them into the into the mood directly from the initial stage that's where also you can define and propose and suggest the right planning and the right budget and knowing all those constraints you can also make some trade-offs between what has been requested and the final deadline it

will also help you to measure and to estimate your margin you can make on a project knowing that you might have to take this amount of time in the developments plus including some functional analysis time so you will be able to really measure how profitable you can be on a project on the client side so here it's also important for him to have this kind of phase so he can make sure that his project scope is correctly understood because he might have written a document but your perception might be different during this phase make sure

that you are all aligned and you all share the same view on the process to be put in place you also get an idea on how to better allocate the time spent by the employee because here when you will do the workshop you will focus on how the different people are working on their day-to-day life you will see where they can where they lose i can see some time and where they can benefit from using odoo they will also understand how the an iit project will go because some companies do not know how to implement

such i can say such a software within their company so doing this might help them to see what resource they need to involve and what would be the next phase and how the pro the project will go they will receive a budget for the project and so they will directly see if they can afford those kind of project or if they need to review their expectation or adapt to be the way they work just to adapt the budget to their capabilities they will also identify the most impactful feature from odoo that will i guess impact

the most the company and they also measure the cost and benefit from a customized feature knowing that they will be able to compare the the budget they need to put on table to get one requirement but they will also see the impact on the day-to-day life of their uh employees so they will be able to measure this and say okay i will go for that development or i will not go for a development because the added value of it will not be sufficient and in general so this phase can help on a more general level

to keep the cost and the risk under control because everything will be written on a paper and you can always refer to it based on uh later on when there is discussion and you will be able to give to this budget so the client and you can measure the the cost of a project it also help you to define and to meet the project deadline if the client has a hard deadline to to meet it will be easier to have some discussion about making some trade-offs and get rid of some requirement just to meet the

project deadline it will also help you to onboard and commit the key users because here we involve them since the beginning of the project so odoo will not be you can say pushed by the top management to the to the company they will not discover the final product at the end of the phase but there will be onboard it and they will try to convert them and make them as an ambassador of audi within the company it's also the place where you initiate the change management to make sure that audu will come smoothly within the

company directly and it's also the best tool to convince the client that odoo is the best tool they can get by measuring the cost versus the return audio can bring one important key key here is that this switch from the gap analysis to the error analysis had a big impact on the client decision so here to give you some number so we are almost on the ratio of eight roi analysis out of 10 converted to a to a project so here we really had this uh this change and it really is the way to convince

the client that odu is a good product for a different company so here most important topic so how to perform the error analysis of course the first topic is to be prepared and to prepare the workshops but not only on your side but also asking the key user to be involved in the preparation so they can have all the information gathered before coming to the workshop this preparation is important because you need to be able to have the ability to ask all your questions and to ask all documentation um during those those discussions to really

be able to understand and to cover every topic and every process applicable inside a company you also have to structure your workshop to ensure that you do not miss any topic and the most important one you have to let the client talk because he will explain you how he's currently working he will explain you what are his pain points that you need to tackle or need to take a a look at so it's really important to make i can see the client at the center of the discussion and let him speak to listen to his

needs and to perform it of course you have to use our error tools that i will show you right now first how to structure the workshop so here we have build a different mind map so here we have one for the kickoff where you have all the topic the most important topic to be covered during the the kickoff small introduction identifying all the sponsors all the stakeholders of the project to identify who is the responsible person for each or for a given topic who is the guy who will decide at the end to go for

a project you define a company structure to re-understand all the the hierarchy in the the company to understand which i can say department is the most important within the company or which has the most impact on the the company you also identify all the risk all the success factors really understand the project context or the ri context in this case and you also define with the client all the high level objective that we have to to tackle with the potential audio project for example if we need to reduce the number of uh different software if

we have to put some effort on the usability if we need to go uh in one or the other the direction just to make sure that we correctly understand the objective of this phase and we also have for each workshop another mind map where we'll go into much more detail and we'll fill this document for at each workshop to really go into each process and will help you to structure your discussion you will have with the client to heal for each department or each process you will create one mind map where you will identify all

the key user and their role within the company you will also define the time allocation of each person this part will be very important for the to make the right and to fill correctly the return side of the error analysis so here just to go into more detail so time location the the way to tackle that is to re ask the key user to explain what are the main activities are doing regularly and how long do they spend on those kind of of activities directly just to understand the amount of time spent on each activity

to really put some priority on the discussion you will have knowing that if one activity occupies 50 of the time the the worker it might be important to dig into this one first to really see if odoo can improve and bring some added value in this process knowing that it's the main activity of the department you will define also all the use cases all the uh the process to tackle into this department you will go into all the details to really receive every information you need to of course get the requirement from the the company

but also identifying all the pain points or or all the inefficiencies uh they face on their day-to-day job example if if i take an account in the on the invoicing process let's uh for example a sales guys wants to issue an invoice they might have to print it on a pdf version go to the to the accounting department give it to the account and we'll look at it maybe rescan it to re-encode it in its accounting software and so here looking at all those topics that might not be actually written in some document by the

the customer might be relevant to put inside this ri because odoo can of course bring a lot of added value on this by all the integration of the different application so going into every use cases will help you of course to get the big picture and every and get every details as well on the way the company is operating you also write all the terminologies because it's important to speak the customer language so we can imagine the solution or the final product you will get when the project will be over you will also have a

dedicated session for all the pain points that we have to tackle or at least to take a look at just to be sure that we can solve most of them the volumes just to understand a bit what they're doing and how frequently they are doing it because here it might be important important to have on the discussion for the performance for example i have a description of what they have at the moment in terms of software how what they work with like every document template if they work with word or excel and so on so

really to get the current picture of the way they are operating at the moment and then here's more where you will identify where are the the gaps so every requirement will be written in this section so by doing this for each workshops here you will get all the main information of course you can add some more uh document on top of it like some word document where you will write really with full text here but this kind of mind map it's really helpful to structure your discussion and structure your note because every time you need

to focus on one part you can directly find it back in this document so when you have performed all your workshops then is a time to switch to the to the filling of the excel so this lri analysis where you will summarize all the information you have received from the pain points to the list of requirements you will have to estimate or to define as development standard feature integration data import and so on so let's take let's have a look at the file so the file is structured in a different sheet where you have first

a dashboard then you have the r part with the two sheets here then the i side here where we list all the requirements and then you have to hit here to define the conclude uh the conclusion of the array plus the planning and then the pricing of the implementation so let's start maybe by the gap the gap side so the uh investment side you all know where we really list all the uh elements all the requirements given by the client where you can put some reference you identify which department is impacted by this requirement if

it's coming from an rfq or not it will help you maybe to explain why the budget between the aura analysis and the rfq analysis is different because you might have much more element in the uri analysis than what has been written during the rfq you have then the business needs and the solution so here the business did so it's really the request in the words of the clients and the solution is the translation in or do or you plan to uh implement this request within odo you define the scope so mainly in what application you

will put the the answer of this needs you define the critical level so if it's a must-have an optional or a phase two requirement or if you simply drop the requirement so here it's important to play the role and to take some decision to make some decision for the client it's important that you decide which requirement is really a must have because of course here for the client every request will be a must-have so that's where you have a big an important role to play to postpone as much as possible all the development requests in

a second phase of a project because we all know that when the client will go live some or most of the requirements will drop because they will see that they can continue to work without having those requirements developed because they are just used to have it in their current software then you have all the types so here standard developments integration and data import plus the estimation of the developments to hear and send some technical comments so with this file you have all the investment and you can measure the cost required to get the product here

if i go now to the details here on the return side which is the new the new part we added with the error analysis we list here all the inefficiencies all the pain points the cla the client is facing and we'll group them per department i will measure the frequency when we have it or we can measure it here and we also provide a solution so in the template we we made a available for you we already have built a list of the most i can say common issues or the most common inefficiencies we saw

in different era analysis we have done in the past group per department so you already have a beginning to fill the this sheet but of course looking at the way the people are working by going at their desk going in the in the warehouse going at the production zone etc will help you to build this list and to identify where audu can bring some added value or can reduce the time they spend for a single element for example if i take an example here in the sales department so here the quotes are made in words

so every series has its own layout the computer of the price might be wrong they have old products so it's hard to maintain them and they are doing 120 quarts per month and the solution here with the we need to do is to use the quotation template the price list and having the integration with the product catalog in the inventory and so you have this for every department another important element is for for example the pines in the wasting time in their inter inter-department communication to get information because most of the time the accounting department

might have to ask the sales department to to get some info about the client they might have to call the purchase department to get some information about the the vendor etc so here with everything inside odoo with the chat or with the the integration between the different applications we might reduce the time the accounting department is spending just by asking questions or asking for more information so here this list will really help you also to move to the saving sides where you will really measure what odoo can bring to the company to really put some

numbers and some percentage and maybe and even some money on top of this details analysis so the way to fill this sheet is to go for each department and to study what they are doing so here that's where that's why here i we added this this part in the mind map to go over the time they spend on each of their activity so if i take the example here of the inventory we know that we have eight people working on the inventory department and they are spending their time in this way so here we see

that 25 of the time is spent on the picking packing and delivery process and we have here one full time also just to store and to scrap the product in the in the warehouse so here building this will really help you to get the big picture of the main activities the department is doing and you will put some efficiency number here to really measure the how audu will improve the time they're spend of course it's okay to put a zero percent because here in the the inventory if the time uh the most time spent by

the inventory worker is to move box from point a to point b in this case audio will not improve the time spent on it because here the time from the point a to point b will still stay the same with or without odo so it's okay to have a zero person but at least we we show to the client that we have taken that into account and that's what we can say we we play the game entirely and we also uh so where all you will not bring some uh i could say added value but

for the rest here we can put some number and here those number should be based on what you have saw in the r details sheet for example you know that uh the system is always down for example the the server always has to be reboot or we have to restart the computer 10 times a day because it crashed because the software is too old blah blah then we can explain why we put this 80 percent number for example because we have some arguments on the r detail sheet so having this three will compute some number

some amount to show how how much money they i could say waste on the uh on those activity and what odoo can bring to uh to the company in terms of time allocation here we have also put some numbers here based on our experience those numbers will be reviewed from time to time based on i can say our experience and on the case we are facing here but they are here to i can say guide you to define the the number here but up to you to see and to measure based on what you have

so uh what you have seen during the the workshops and your feeling as well on what odoo can bring in terms of efficiency to the company and then of course you have some uh graph visualization for the final presentation that i will speak about later then you have the conclusion where you put everything into one place where you will define so all the planning all the standards the time need to need it to implement the standard features so all the configuration and so on you will get all the information the timing required for the data

migration using csv import the development the customization integration and all the main i can say type of interaction might have with a for the project then a split per profile and here a split per department and the phasing of the project here to help you to measure the standard time to so the time required to implement the standard feature we have built this matrix so here under the standard estimation tool so here the way to build this so we have conducted on a survey internally and we ask every consultant at udu to give to give

us the time they would need to implement one application with the complexity level here so easy average and complex so we ask them to give us the time they would take for each application and then we leave here the responsibility of the the person who is doing the analysis to really put the time he estimates for such a application because here of course depending on the case you might not be in the right number but you might be somewhere in the middle because some elements are quite easy to implement but we have one complex there

so we don't know exactly in which case we were at the end so that's why here we put here and we leave the responsibility to the person doing the error analysis to fill those information then we have here a small planner tool quite simple but at least gives you a rough idea of how long it will take to deliver the the project by having the first project initiation phase and then the phase one phase two phase three and you of course can add some additional phase here you can also include some buffer week or days

in this uh in this tool to really show and give a first planning estimation of the project and the last sheet here is just to give you and to estimate the budget required for the the project here so you just define the rate of every profile you get information with the the budget next to it and you have also all the subscription information so how many user all the uh the application required and all the maintenance and the hosting fee at the end when everything is uh filled in you have the the first year also

here the dashboard uh i would say where you will get really the comparison between the return sign and the investment that needs to be done so here you have a summary of the return part the subscription sorry invest uh investment and the implementation investment and then you get the return investment graph where you see after how long the project would be in positive and then some project distribution to identify if the project has a lot of development or if the project is quite standard so it also help you to maybe as a client to make

some trade-off or review uh his request to reduce as much as possible the development part to be on on the right i can see ratio where you have actually most standard feature here so after having build the file internally and having reviewed them with another colleague who has a fresh view of the on the project it's time to continue to present your result to the client so here we use the excel file to feed and to create one presentation to the client where we'll show him the all the results knowing that we have all the

energies on the return side plus of course the price and the budget and the planning needed for the project and so we have this kind of presentation where we go over the different topics so we have the context of the project we have the url results where we also when it's required define what has been removed from the scope because after during the era analysis we might have uh decided that this scope will now be off out of the the project for some reason so it might be important to repeat that in this document and

then for each department study during the our analysis we will have this section where we'll have the the graph shown here per main activity how uh how long they spent and what time they spent in each of those activities with some details here on the issue we face so here recording quotes take too much time the serious pipeline pipeline is not efficient because they are spread into a different document they are used on the excel file lost in the email etc so you will get directly the picture of the the time spent by the different

person within the department and the main issue i mean paying points or main inefficiencies we have spot during discussion and then we have i can see all the uh numbers so here what are the saving or we can bring to the company in terms of time and money allocation here with here the solution uh we'll have here and so here for example having the product configurator to fasten the recording of quotation with no do and so we can say that we reduce to five percent of the recording three for each department we have the same

structure so first the time span and the and the pain points and then here the savings and the solution of the will bring well then we will have the target architecture we have the organization where we'll emphasize explain uh what is the audio methodology all the roles and responsibility the eye level planning all the risks and then we'll focus so on the offer so all the so the pricing required and the budget required for the the project first on the implementation but also on the subscription level so with the license the application and the hosting

so here what's important is really to use what we have uh written and and put inside the spreadsheet to really to feed this presentation to a faculty the player has a summary of the excel so we have really the same information in two documents but it would be easier for the client to navigate in the powerpoint than in the excel you know so really important to have the same i can say base of information in those two documents so for the two so that that's it but few tips and tricks that we have seen and

taken from our experience is that during this phase you need to be a source per a person sorry because the project is not already sold so it's important to act uh and to promote and to sell or do to reconvince the the client that you are the right person to deliver a project and that audu is the right tool as well to for the company you also need to ask to see how people work because here you will not notice everything by just simply sitting in a room with the manager or the key person the

key users from each department it's important to ask for a visit of the company just read to see how an accountant is working our a person from the inventory or a person from the manufacturing the production line is working to really see where they're uh and it will help you to spot all the inefficiencies that audu can tack on or you can solve you must find a solution to each pain point they have because here it's not a good signal to leave i can say pain points uh an answer so it's important to show to

the client that you have think uh of every pain point and find a solution for each pain point they have it's also important to take decision for a successful project not to focus i can say on the satisfaction of the client at the first phase because here it's really important for you to take a decision on which request should be mandatory should be a must have for the first goal life and which one should be optional or maybe even drop of course when you have taken the decision it's open for discussion with the client it's

important that you have made the first round of decision on this kind of of information of classification of a request and it's also important to not present different option to the to the customer if you have different alternative select one and drop the other leave it for a later or leave it for discussion afterwards it's important to not let the client design option a or plan b select which one is the best for the success of the project so so that was for the tricks we we have seen and we have identified during the our

analysis we have done in the past but here important information is that we share every tool i've presented today and you can find every link in the audio implementation methodology book and also on the partner knowledge base as well so every link will be available so feel free to use every document i've shown and feel free to send us feedback to share your experience with us so we can also improve the way we are working and the way we build those documents so now it's time to go to the q a session so we'll take

a look at the the youtube chat and identify the different questions and try to answer most of them here okay let me maybe scroll up a little bit let me see will the cl will the client receive the full scoping document all the client requirements and will the the risk begin is within the report so yes at the end so you're supposed to also send the excel file to the client so he can play around decide if he can drop additional requests or if he has to switch from request you have postponed or drop to

a must have to just to see and to measure the impact it will have on the on the budget and on the planning so yes so here the file should be shared so you will have the full scoping document as well so we get also the big picture and the full picture of what has been analyzed so all the for the risk mitigation so we have other i can say side documents that we don't have like it's a template to share yet where we list all the risk and so we have it also in the

templates and the powerpoints all the risk listed so the client is also aware of the risk we have identified and the point to pay attention to so is this improvement calculator estimated so here all the improvement rate and element are estimated because it depends on every company every industry every case so we cannot really measure uh i guess they will give this real percentage that we you can base uh directly but we have some guidelines then for uh you when you are doing the your analysis of course you can go a little bit further in

the way to measure that and put some i can say some more maths behind that but here we more rely on i can see the feeling of the consultant doing the their analysis to measure and to estimate the the savings in terms of timing or you can bring to the company yeah so here i see a comment so the saving time of t in each department do not mean that it's a direct saving because the people stay in the company so you have to fire your employee so here the idea is not to reduce the

number of employees within this phase the idea behind that is to optimize the way people are spending their time within the company because we consider that it's a waste of time to ask questions to every department every time we need to do something if we can directly find the answer uh within one single software so here really the idea behind that and it's uh important to have this kind of speech is not to say that at the end of the project you will not get the i can see the amount of money we have uh

so in the in the spreadsheet in your pocket uh what you have to explain to the client is that the time spent by his employee will be better allocated so in term instead of spending two hours to book i don't know 100 invoices for example he will spend 30 minutes because he will not have to wait for other person to answer different questions the person will be able to find this information directly okay so where you indicate the training for each app so here we have an educated section on the the planning element uh right

where is it there where we have here the end user training support and the customer documentation here in the audu implementation methodology the the approach we follow and we have for the training is the train the trainer approach where you train the the key user and the key user is responsible to train all the end users but we have here a place where we can estimate the time required to write or to help the client to write some documentation because we all we we think that it's [Music] better that the client is writing his own

documentation because he know how to speak the company language he knows how to speak to the uh to his colleagues etc so it would be in terms of quality and in terms of ease it's better to to let them write the documentation i see so you said that you we can use an arrive for small project and we can use it uh in gap pace at this time the break is sell so here we can always use this file uh regard as a side of project but here we what we think is that for a

small project it might be a bit too heavy in terms of time and budget to allocate to a product for a small project the time required to go over each of this process and each of its requirements and measure all the time in our discussion it might not be worth to spend this much time in this phase or by feeding this document if we compare to the final budget required to make the implementation that's why here for the standard implementation that we have so the quick start approach we include this ri phase and we summarize

it into the kickoff call so the project is already sold but then we just ensure that everything has been correctly understood and that the project is really feasible and so to avoid any surprise and if at the end of the first call we see that no this project is it's not feasible or we require a much bigger budget we can directly explain that to the client and then do the right move either increasing the budget or saying it's a no-go and then we we stop the project right now [Music] let me see where we have

uh let me see if i find some other question but you have some issue to scroll in the list of questions how to calculate an engineer service with maybe 100 position in the proposal they did by excel before pdf and excel files list yeah there's not a real question let me see [Music] okay could you define a small project for you so yeah here difficult question because here there is no cancer it's not rocket science to define if the project is big or if it's a small one it's not even defined in terms of users

or periscope it's really a combination of different factors such as like i said the name of the company and of course the side of the company but also the complexity of this process because you can have a company with i say 10 percent 10 people working in the company but having really complex process or really hard hard constraint due to the industry in place and you have can have like really big company that can work with a pretty standard approach so here depending on that you can define if it's a big or a small project

more in terms of feature to put in place uh inside audio because you can have like a big company with more than one thousand employee but they're only requesting a small application so here we can identify this as a small project and we can have for example another company with 10 people but asking for a full scope deployment then we can take this pla as a big one and take some time to make this our analysis as well so really hard to define which one is big which one is small so it should be a

i can say up to your common sense to define if it's worse to spend and to invest some time on this arri phase okay [Music] what is the different point of view between r and i sheet so here the here that there are two active totally different but they're responding to each other so the r side is really the return part where you will focus on what odoo can bring to the company and in this part you do not only look at the customer request but you will also look at all the workers are working

within the company and all the people are collaborating uh across each department and all together meanwhile in the eye side you will really focus on the requests and the topic important with important to be put in place inside audu of course each part should be more or less the same because here most of the details isolated and written in the r side should be found in the items as well because all the papers should have a solution and the solution should be included in the project scope so they are quite similar but still a bit

different in terms of the the objective followed so error analysis is more suitable for large companies and real standard things to do can we agree on this of course doing a proper and another dedicated case for the analysis is more suitable for big companies because they have a more significant budget available for such project so yeah this kind of phase re isolated for delicate phase is more stable to the big companies and here even if they are complex it's important to it's even more important to have this kind of report when there is a lot

of development request because we really need to challenge every development request to find workarounds and to stay as standard as possible to not have a too much development and make the technical depth explode within time because you all know that then you will have difficulties to upgrade to newer version you will have difficulties to maintain the solution within the time so it's really important for that's a large development project to get this file and this phase done and to challenge every development request so so okay so here i see that we are running out of

time so i would like to thank all of you for your time and your presence during this webinar and so if you have a if you need some more information so don't hesitate to contact your account manager so i wish you a pleasant day and see you soon thank you bye you