we can create.
So, um, our total starting will begin, and within that starting, what we will do is, we have received some documents, we have received some CVs of the employees. But the CVs are not up-to-date. So what I was wanting is that, in this, your people information has not been shared yet. We were probably waiting for the agreement signing. Since the agreement has been signed, if you would kindly, I mean, if I got the details of the employees, then what I would do is, with each individual, I would have a session to understand their current situation. Like, how they are currently with JarP or the company, and I could map out when they started the job, and what their situation is now. and how important they are for this total project.

So, Arif bhai, will you kindly request this?
Okay, the employee information that you have, this CV, I have given the CV, along with the CV, another file, the 'people information'. Yes. In this excel file, you will see that all the employee's information is there.
Wait. Is yours...
I see that the People Information form is empty, but let me check first if any other form has been created.
No... You see, there is another file there. Full information of Mononsoft.
Okay, employee information. Let me see... JarP documentation...

This has a feature list. I am, I am sharing the thing, okay?
Sure. I am sharing the screen.

In our Mononsoft, one, what I have done is, one of them contains the employee assessment. Another one contains the record of the meetings we are having. Another is the agreement. The agreement we have is kept there. If we go into the employee assessment, inside the employee assessment, there is a folder for CVs and a JarP documentation folder.
No, outside, look outside, there's 'employee information of Mononsoft'. Second one. Yes, this one.
Okay. Okay, you have given it like this. Okay, sorry. I couldn't see it. Okay. Okay.

Okay, everyone's information is given. Okay, that's, that's, this is what I was wanting.
Okay. Okay, people, okay, Mononsoft people information.
Okay. Now if we go to the thing... I will close this then.

If I go here... You have shared a documentation of JarP. In it is the total JarP development issue and solution plan. So, in this, the 'not started' ones are still pending, right?
Yes, yes, yes.
What I... The 'in progress' ones are also actually pending, not finished.
The in progress ones? The in progress ones?
Yes, the work is ongoing. It's not finished.
The work is ongoing, it's not finished. Okay. And the 'closed' ones are completely finished.
The 'closed' ones are finished and after checking, it has been deployed. The user has started using it.
Okay. What I will do is that I will create a document. that will be with 'completed', 'in progress', 'not started'. Okay? Then we will understand that actually, the feature list that we have added here,
This is the same document. Sorry.
Right here, in this very sheet, you have a summary. Look, there's a summary sheet. In this... The thing you... In this very sheet of yours... JarP issues and solutions. Summary... Look here, there's a thing called 'summary'. Here you can see a summary. Below these colors, you can see how many new issues there are. Among them, how many we have fixed, how many have been closed, how many enhancements, how many bugs, how many others. This is a status. And below it, if you go down a little, you will see the full list of pending issues is being automatically populated here. It gets updated automatically from the previous sheet.
Okay. Okay. Now, there's one thing I was asking you, which is your feature list, Okay? Within this feature list, plus the continuous development you are doing now, have you made an admin panel here, where users or various modules can be controlled?
Not yet, we haven't gone into admin panel development yet. The entire admin panel is actually being controlled from the backend. Meaning, database design plus implementation, everything is done. We just haven't brought it to the front-end. So far, some front-end designs have been made, and some designs are not done either. Some are in development, we haven't released them.
Okay. That's good. Admin panel. Meaning role navigation or feature, when a new feature will be enrolled, or navigation, a new menu, a new role, these things. The designs for these are all done. We are still, on an urgent basis, having to give importance to the operation, for which reason we are not getting the slot, a free slot, to start these developments.
Okay. Then we... Sorry, Zakir, did you want to ask something?
Yes. Yes, yes, a little sorry, I am interrupting a bit. That is, how are the tasks of the administration panel done now? How are these managed now? For example, the matters of roles?
We manage it from the backend. We manage it from the backend. Roles, meaning, which role has what data.
Hard code. Through hard coding, right?
We manage from the backend. Meaning, we manage through scripts.
Yes, yes, yes, I understand. Okay.
Okay. Okay. What we will do, is that, this database schema that you have, that database schema's... this feature list you have made, okay, let me come to it one by one. This feature list you have made here, is this feature list locked, or do you continuously update it?
Meaning, in this sheet? Yes, yes. No, it's not locked. Actually, since the whole thing is under development, if a new feature is needed now, we immediately update it here, plus we do whatever corresponding development is needed.
Okay. So, we haven't fully locked it yet.
So what we, what we want to do is that now, this, you don't have to do it, if we get the total back-end, meaning if a copy of the database schema is given to us, what we will do is, we will update this document along with your database. Okay? What has been done in the database so far, and along with that, this document, which we call the feature list, if we say that, we will update that feature list and put a lock on it here. By 'put a lock', I mean for example, you have made the SD module, or if a new feature needs to be made there, that will come, that's not a problem. But what we will do is that from here, let's say the additional work we will do, plus with the old one, we will lock it and start from a certain stage. That we have received this thing, and after receiving this, we will match it with this. We will match your total, sorry, we will match this total to see its connection with it, or how much has been done. Then what we will do is, we won't use that, what do you call it, we won't use Oracle, we will use a different database, where the work you have done, you have done. And the work that hasn't been done, we will make a total list of it. After making the list, we will copy the database. After copying, let's say we will make a development plan using Agile or waterfall, we will use both processes. Some things we will do using Agile, where we will lock it completely, and nothing new will come until it is finished. And even if it comes, it will come through a relational database, because the database we create, we will never touch that. in our total thinking. If anything additional needs to be added, we will add it through a relational database. So that our development is not affected, not harmed. Do you have any suggestions here?
No, I didn't understand this. Could you please clarify this once more?
For example, the database that you have, you have to give us a copy of it. If you give us a copy, what we will do is, we will reverse engineer it and check the total functionality you are saying is there, and then finalize it. That this functionality...
From the database schema.
Meaning, let me say something, that is, suppose, the Oracle database, if we want to handle big data in the Oracle database, our costing will increase. Like, Oracle has a payment part, the cost will increase a lot, yes. So what we want to do now is, what Sahab bhai is saying, is that we will take your database and convert it to another, I mean a high-performance database. Then everything will be handled from there. That's what he's explaining.
Meaning, if we now... So, the database, are you only wanting the structure of the database or with the data?
I want it with the data. Because... If you want it with the data, the current size is in and around 300 GB.
Yes, yes. Now, what we can do for you is, we can make an Oracle PDB, meaning an Oracle... our current production schema, we can make a copy of this schema, upload it to a PDB on my end, and give you access to that schema. From there, you can do as you please.
Yes, yes, yes, if you give us access, we can go in and see that thing. Then if we can start an engine and forward it to another database, we will try that.
Because to transfer this schema and upload it there again, you will need an Oracle. Instead of that, I have Oracle here, I can put a schema in a PDB and give you access to it.
Okay. That's why I said that okay, that's not a problem.
When we get this, what we will do is, you have given us some logins and things. What we will do is, along with this feature list, whatever you have done and what has been done, we will review that.
So, okay, in that case, the credentials I have given you are for our test environment. We synchronize our test environment from production every 2-3 months or so. Okay? So, it is more or less synchronized now, meaning the data is close to production. But it's test. There, the database I will give you, will it be okay if the access is in read-only mode?
If it's in write mode, if we do some work, then I think write mode would be convenient.
Meaning, will you write? I mean, is there actually a need to write anything?
No, we won't write anything. We won't write anything. We will...
So, in that case, I mean, if I give you credentials for the test environment, database login credentials for the test schema, then your work should be done.
Yes, yes, yes, I won't need to copy it anymore. Yes, yes, yes, give that. Then if anything is needed further, we can discuss and say so.
Sure. I am sending it.
Yes, yes. And if we need to write, sorry, excuse me. We will first analyze the whole thing, and after analyzing, we will update this entire feature list, that this is the feature list and if you think you want to add something here, like we think that next year we will bring this functionality, but it hasn't happened yet. Add that, there's no problem with that. That won't be a problem. So what we will do is, our main feature for the total project now is, let me tell you how we will proceed. That is, to take this application as a SaaS platform. Now, the development you have done, since you haven't done the user and this admin part, this is a good thing. Why? Because then we can now shape it in a way that if we do it company-wise, user-wise, and the users will be under the company and how it will be controlled. And each company's users are separate and different. And for each company, if they make a copy, if they register, the registration things are separate, the database schema is separate, we will plan those things. Then we will take it to execution.
But we cannot do it then without your consent. But the documentation parts, we will finalize now. Plus, the documentation that we need from reverse engineering, on those things, we will analyze and propose these things, for example, we have to do SRS. So how will we do the SRS, or we have to do wireframing, how will we do the wireframing. Then the other things that are in this application, we will do those slowly. When the documentation is finished, we will lock the whole thing, then we will go into development. Before that, we will not go into development. And if you have any suggestions... this is our thinking. But do you have any thoughts here?
Meaning this admin, the admin's part?
No no, the admin's part plus however much you have developed overall, we have to do the documentation of the total of that first. Specifically why we have to do it is because for us to see, the parts you have developed, if we now go to SaaS-based, if we go to SaaS-based, will it need any modification or will it need to be extended, or what you have developed, that is okay, to analyze these things, we need an analysis of the whole thing.
Yes, for further, further AI implementation, we will need that analysis. So that if AI can be implemented in any part, then we can discuss among ourselves and say that no, in this place, if we implement AI...
Let me interrupt a bit. Is Russel bhai on the line?
Russel bhai was there. Russel bhai is there.
Yes, yes, yes, I am here. In various directions... Have you taken the server down?
Has the server been taken down? No, not down. Network problem. I sent a message in the group.
Okay, okay. Alright. Neshar bhai, tell me, you were looking for me.
Okay. No, what I mean is, you are listening to the discussion, the whole thing.
I can't listen very attentively, Neshar bhai. Our server end has a bit of a network problem, you understand. Calls are coming from everywhere, it's a bit unsound.
I understand. Yes, yes, this is a big issue.
What I am, this, what we are discussing, is that, we will take a copy, a copy of your database schema, and from there, your current build, and this feature list, by feature list I mean what we call your wishlist.
Neshar bhai, what copy will you take? What copy?
We will take a copy of the database.
Okay, okay. Okay. Along with the copy of the database, your current build, that current build and your documentation, the gap in the documentation, what we will do is, along with the total JarP application, with your feature list, what documentation needs to be done, we will finalize that, and lock this entire application. That we, let's say, will launch this as SaaS, software as a service, so to launch it as software as a service, our administration panel, which has not been built yet, how will we do the administration? For example, you are in pharmaceuticals, now if a garments company wants to use this, how will the garments company do it? How will they work with this schema or these things, or we want to post this to another pharmaceutical company, then how will they use it, these analyses. Plus, if we want to add AI or other things here, in the case of reporting, how will we do that, we have to do the documentation and everything for these things first. Then we will go to execution, that yes, we have received this thing, this thing exists, and if we want to implement AI in this, then this has to be done. If we want to make this SaaS, then this has to be done. If we want to extend this further to finish the modules, then this has to be done.
Okay, okay, I understand. I understand. Meaning our...
Here my, my concern is, you will probably take a backup, you will implement it in your own system and work. My thing is that you don't know the system well. In our SD module alone, about 2000 users are always connected with the system. Yes. They are always placing orders, invoices are being made, meaning very rash transactions. Our pharmaceuticals... No, in your live system we are not... touching it. You probably know the behavior. The value of the invoice is not that high but... the number of invoices is a lot.

Russel bhai, your voice is breaking up. But if I, I understand this, we are not touching your live system or your system. What we are doing is, we are taking the copy, taking the copy to your test one, on that we are analyzing. We are not changing or modifying anything.
Yes, yes, yes, I understand, I understand.
Okay? We will only analyze, and after analyzing and doing the proper documentation, then we will go to the next stage. Why? Because if we want to sell this to some other company, since it's an extensive work, it's not possible without documentation. And also, if someone wants to buy it, they will want to know what it actually has, and without developing it 100%, we cannot sell it. Why? Because people don't want to buy an unfinished product, they don't want to buy an unfinished product.

Okay, okay.
So, for this reason, the work we will do first is your analyzation, documentation, identifying what work is left, and after identifying, solving our main problem. That actually we are in a, I mean, a right state. Okay. Then is what Jabeed sir said, which is cost cut down. Then we will see how we can cut costs. One can be resource cost cut down, another can be employee cost cut down. Another can be many other types of cost down. So then we will analyze and say that one work's cost, for example, we don't have any admin panel. Now, here you have several, quite a few employees who are directly working from the database and giving you results. Now if we can reinstate the admin panel, after doing so, if I can then say that if I reinstate this, we won't need your three employees. Okay? These things we will propose later, that if we do this, the cost will be cut like this, if we do this, the cost will be cut like this. Then Jabeed sir can make a decision that yes, then do this or do this or do this. Have I been able to explain?
Yes.
And about the reporting matter, we... For example, if we copy the entire application, after copying, the problems that exist, we will solve those problems from a separate database. Then, here, in testing, your test users, if we perhaps change the tunnel, if we change the tunnel, then it can be seen if the users are actually getting what they are looking for, what they want. Later, the tunnel can be reverted back to that application, that's not a problem, that won't be a problem.

This needs to be understood. This isn't happening right now, this needs to be understood.
It's much later. Much later.
Okay. This is much later. These are for what we can do in the future. Not now. First, we have to do the documentation, reverse engineer the whole thing and do the documentation, then, locking the entire application. Then, for manufacturing, sorry, we have made this ready for pharmaceuticals. Meaning, making pharmaceuticals version 0.1 ready. What functionalities are in version 0.1, what it has, locking the total, then going to the market with it. In the worldwide market, that for our pharmaceuticals, our 0.1 SaaS application has been built. Then after that, we can slowly bring in other modules, that okay, we are doing pharmaceuticals now, we will now enter some other market. Where we have done the whole thing module-wise, so which modules can we bring, for different applications. Then we will work on that again. Meaning, the coordinations, plus its depth, these things we can decide on only when we have proper documentation.
And for the documentation, we will embed an AI engine within the documentation so that specifically, within a few seconds, the things we have done and the things that exist, those things come up. That what we want, it exists. Okay, fine. So we want to do this, this thing does not exist. So that we can make decisions in that way.

Okay. Okay, in these tasks, can we be involved in any way?
You will definitely be involved. Definitely. You will definitely be involved. Now what I will do is, as I said, I have received this document, I will analyze it. After analyzing, your employees, the total employees who are there, their, their, from you here, we want a list, or whoever is here, who think that they want to do their, what do you call it, in their career development, the kind of work we will do, like Artificial Intelligence or these types of things. Some things will come within this. Number one will be, here we will bring full stack development, we will bring micro development, which we call DevOps. Now, if we can prepare someone from your team for those things, that is well enough. And if we cannot prepare them, then we will have to bring a new team member for cost cutting. You also have to be prepared for that. Because if I can get three tasks done by one person, then I will keep him. And if I cannot get three tasks done by one person, if one person only does one task and that task is not very critical, then there is no benefit for the business in keeping him.
Right.
You my, if I am speaking very clearly here. Your employees might not like it. But we have to cut the business's cost, to be frank. Now, however we can achieve that, through the joint efforts of our business and employees, that is what we will achieve.
No, fully agreed. This, we don't disagree on this.
We want this.
So in that case, since I have received the information more or less, I will start this initial work. I have a meeting with Ross tomorrow about all these things, on how we will handle it. Plus, I want to talk individually with all of your employees. Russel bhai and Arif bhai, you will be there, no problem with that. But bringing them into an interview process, to actually understand, the position they are in now, are they happy with this position or they wanted to learn more. Now, maybe you selected someone, that we are selecting these five people. Those five might be appropriate, or they might not be, or someone else whom you did not select, they have better talent. We want to bring that out, that those who have better talent here, they should come into this process. Otherwise, the resources and everything we try, that will be seen to be prolonged. I this... Now, we can only do this then, Arif bhai and Russel bhai, if you say that it's okay. Then bring everyone for an interview. We will create a score for them on what they actually are now, what they have, what they were, what they want to be. And how that will support our business in the long run.
Yes.
Okay.
When do you want to start this? From tomorrow itself?
Tomorrow, I want to start from tomorrow, yes.
Then it would be better if you create a schedule like that, if you can give me a schedule, I will make them available in that way. Interview, how long can each interview be, per discussion, instead of interview I will say discussion.
Discussion. Because the word 'interview' actually sounds a bit bad... I mean, I don't know how it is there, here even a journalist takes an interview, but the word 'interview' itself is a bit...
No, not interview. We will call it a career development discussion.
Okay.
So, it will be 20 minutes with one person, so what I will do is, for 20 minutes, I mean, it will take us one week. Since you have many employees, I will create a schedule and share it tomorrow that we will sit with each and every one for 20 minutes, to discuss what they want to do in their career development and if they are actually ready. Because there is a huge learning curve here, which includes knowing technology, learning technology and implementing it. And to do this, it will take us six months to a year if we want to develop the existing employees, and you have to be prepared for that as well. That yes, we have chosen these employees, these few, and we will invest time in them, so that they will be a better option for us. And if those we selected, we selected them, and those we didn't select, we will see how we can slowly eliminate them from your current workflow. By implementing the right process. Right process and right system. What you are doing now is time-consuming, plus many people have to be gathered. And if we develop a process specifically and the system, if we develop that, then what will happen is, that what we will do, you can implement that within a few weeks. When you do that, you yourselves will see how we can slowly eliminate these resources. Because we have to reduce costs. That's one thing. Another thing is that here we had said that we will divide it into three groups. One group is the current workflow, which will work on your current workflow. One team will work on taking external work and doing external work. Another team will work on innovation. So, in that case, after these interviews, we can sit together and get this process ready. And internally now, the country's, the work that exists now, for example, we went to the police, how we can bring that work and how we can carry it out, that's one thing. Plus, in another company, the other companies that exist, making a list of them. I will request from Arif bhai to make a list, that I, or Russel bhai is there, to make a list of 20 of our companies. In these 20 companies, how can we, since we are working together, sell things like software development, AI implementation, business development to them. In that way, we have to prepare some pitches, some presentations, so that we, for example, from 20 clients, if we approach 20 people, won't we get one or two from there?
I hope so. I mean, I am optimistic, actually.
No, no, I know, I... I will get it from 10. Yes, instead of one from 20, I am optimistic about getting from 10. One. God willing. So, these things we now, I mean, we have to bring into our process. So, what I want from Arif bhai or what I want from Russel bhai, is for you to invest your time in our business development activities here. So, I will make some schedules with Ross, and after scheduling, prepare this channel properly, on how we can do process-based work. Plus, our thing, this CRM is more or less in finalization, how we can introduce processes into the work. That an employee understands on their own that they are taking six hours for a three-hour job and for that, they will have to be fined. If we don't introduce these things, then our process or the employee's, that thing, the ownership will not be created. Now, maybe we are not able to measure. We will introduce this measurement, God willing. So that an employee can understand or the owner's side can understand that an employee has given his 100%, and after giving it, he is in a good place. An employee may not have given 100%, he has given 50%, he has to improve his 50%. If he does not improve that within a specific time, the company does not need that employee, because no one will benefit from it. We will slowly introduce these decisions so that the business process and the execution run beautifully together.

Okay.
Okay.
And in this case, if you have any suggestions, we have a group on WhatsApp, you can also tell me via email. If there are any suggestions or anything. So, what we, now what we'll do, if you have nothing to say, I will give a recap of what we talked about. Then maybe we can close the meeting. Do you have anything to say or add, Russel bhai, Arif bhai, or Zakir?

No, thank you.
Okay. So, what we discussed today... Neshar bhai, my, you spoke about the external market, let me say a little about that. Our very primary intention was that JarP would cover all industries, it would be that kind of ERP. Like, for example, if we want to sell a building, that will be possible. If you want to sell gas, that will be possible. If I want to sell medicine, that will be possible. So at this moment, we are more or less prepared for the pharmaceuticals industry, that we can cover all of that. So, related to this, we can probably cover some more businesses, but our ambition was like that, so that one software can cover all industries. I just added that for you, in case it is of any use to you for your convenience.
Yes, yes, no, that will be useful. What I said before, you maybe, I will write this, when I send the email for today's meeting, that is, we have now done the pharmaceuticals one. So, for each individual element, we have to do individual work. Now, for pharmaceuticals, we will only give priority to pharmaceuticals and finish it. Now, suppose we want to bring in construction. The construction module and the pharmaceuticals module are not the same. The process of construction or the parts section of construction or the different sections are also not the same. So, what we will do now is we have identified pharmaceuticals. Now we will finalize and lock the pharmaceuticals part completely, that yes, this is our pharmaceuticals version 0.1. When this 0.1 is finished, then we, for example, will create a wishlist of which market we want to do next.
Okay? Then we will finalize it... Okay Neshar bhai, let me interrupt a bit here. What Russel bhai said, our actual main objective was, this one ERP product of ours, here we will not specify that this is pharmaceuticals or this is FMCG, this is real estate or something like that. Whoever wants to use it from wherever, their process will be automated and our original design is actually made like that, that if it's not a pharmaceutical company, if it's a gas company, it will cover. If it's a food manufacturing company, it will cover. If it's even implemented in a lottery shop, it will cover it. Maybe it won't cover 100% of the business. For pharma too, I am assuming my 90-95% of business is covered. Maybe if I take this to medical devices, it will cover maybe 80-85%. If I take this to food manufacturing, it will cover 70% or 75%. Even if taken to gas, it will cover 80-85%. So, we want to identify the remaining parts bit by bit, whatever is not covered by us, domain by domain. Once we sit in a domain, we will understand how much of a gap we have. If we don't implement the thing in any domain, then the gap, actually, we won't be able to find it just by sitting in the laboratory all day. We have to get on the field for that.
Thank you Arif bhai, that's what I was saying, that we are doing pharmaceuticals now, if we want to take this to another domain now, then we will need proper analyzation. That is why we are doing the analyzation. The first analyzation we will do now is 'current JarP, future JarP'. Now, in future JarP, we can go into infinite domains, there's no problem with that. The current JarP, its, which modules are more relevant to other production sites, if as you said, production, lottery or manufacturing or this. Then what we will do is the mapping. What you said is, our pharmaceuticals now, to lock that. Then the modules it has, those modules, let's say 85% are going to your garments industry. So, with this 80% production, how much more percent do we need to develop for it to be for garments. We will get those things ready through analyzation. And for that reason, I said we have to select a domain. That yes, we are doing pharmaceuticals, after pharmaceuticals, which domain do we want to go to.
Now we can say that... Okay, the next domain, the next domain is already selected, medical device. We will implement it in that syringe.
Okay. We have almost everything ready.
Okay. So what we, as you said, we can't make it infinite, and in the case of marketing or the market, we can't sell it without specifications. So, in that case, what has been done now, we will sell that. In marketing, we might add two or three more domains here, maybe a maximum of five domains we will add. That we will get it ready or market it in these five domains. This will have two sides. One is to onboard clients through marketing so that we can sell this. Number one. Another is to create it as a SaaS so that people can come and do these tests, meaning create a demo account, test it, and they can understand that yes, they need this thing. In this way, we have to do some work. Now, for example, not all versions are available in a demo. Now, the 85% that has been built, if we add another 5% to it, for example, or 30% has been built, if we make it 40% from here, that this module of ours is this much percent done, but since every business is different, so the things you will need, we can build it because we already have the mechanism, we already have the schemas, we already have the thinking, we have the team, we have everything. So, these things can be done, if you give the requirements, we will build it for you. Okay? We will proceed in that way, because if we want to build everything completely and then market it, we will never be able to go to the market. Are you able to understand me clearly?
Clear, clear, I have understood.
So, that's why we will do the analysis part. It will take some time, at least one or two months for analysis and to get everything done. But we will understand that yes, and in the meantime, we will not stop, for example, developing our landing page, getting this thing ready, getting it ready for marketing, all these things will continue together. So, those things will also happen together, God willing. So, what we now, if I recap today's discussion, is that we will analyze the entire JarP system, and after analyzing and reverse engineering, we will identify its documentation or the gaps it has, and after identifying, we will go for proper documentation. This is one part of ours. The second part is, with each of our employees, we will have a career development interview, a discussion, and in the discussion, we will bring the best ones from there into career development. And career development will include DevOps, full stack development, and AI innovation. One person can go into all three sides, no problem with that. But the company will decide whether to teach one person everything or give different things to different people. Okay? The company will decide that, that's one thing. Another thing is, we will create a methodology, in which one part is, we are now doing pharmaceuticals, after that we will go to manufacturing as you said, you will tell me three more domains, that we want to go into these three domains, so what I will do is, taking these five domains, our total methodology and its connectivity with JarP, we will analyze that, that yes, we want to go into these five domains, we want to start marketing in these five domains and, for these five domains, creating demo users, doing this, doing that, starting marketing, which territories we will go to or whether we will go to Europe or America or some other sub-continent or some other continent, finalizing these methodologies and then executing. And I am 100% confirmed that if we proceed with the whole thing like this, then our income will be generated plus the current things we have will also be finished. Okay. And one last thing we will do is, the total workflow that exists now, we will divide it into three parts. One is current service, which is to provide service to the current users of JarP. Second is, we will prepare for internal, external work. We will select 20 companies, among those 20 companies we will prepare them, whether they need ERP or something else or AI innovation, whatever they need, we will work on that for them and we will give them business development if needed. And another wing will work on innovative ideas, what we can do in the future to become market leaders, both in Bangladesh and globally. We will do something about that. So, more or less, this is my recap of today's meeting. If you have anything, you can kindly add it.
No, it's okay. I have nothing to add to this.
Okay, alright. And Russel bhai?
No, thank you, Neshar bhai. I have nothing for now. Thank you.
Okay. Sorry. Alright, then goodbye for today. I will make a schedule and add it to the email, Arif bhai and Russel bhai, so that we can talk to at least two or three people from tomorrow. For our next step.
Sure, sure.
Okay.
Peace be upon you.
Okay, then goodbye. Peace be upon you.
Peace be upon you.