Transcription
We are going to follow a step-by-step procedure. Like, a client has come to you. Okay? What can be the processes after that? And after that, how will your processes be followed? On that entire process, we are going to follow an A to Z structure, step by step, to understand what processes are, how they are followed, and what scenarios exist. Okay? First of all, if you have come to learn about Agentic, the motive again is that you have to use Agentic in your business in the future, within your systems. Okay? So, I will break it down for you: you can have two roles. You have to identify. Your roles will be two. Your first role will be that you are going freelance. Okay? Going towards business. Your second role will be that you have to go to the job slide. Getting my point? Today, we are going to briefly explain both these roles and move towards Agentic to understand the processes, what the process of Agentic AI is on the back end. Okay? If you have understood the process today, and in the next lecture, God willing, we will understand the process. Then, if you have understood the process, you will have an understanding of the process, then, God willing, you will be able to build any agent in the world, God willing. Okay? Your first scenario is that you do freelance. Okay? You have outreached to a client. What will be the methods of outreach? How to outreach, classes for that will also be delivered to you. Okay? You have outreached to the client. Okay? You have outreached to the client. Now, you will get three types of clients. Either you will get three types of clients within Agentic. Okay? I will break down all three types of clients for you step by step. The first type of client will be someone who has no interest in AI. No interest at all in AI. The second type of client will be someone who is interested, but doesn't know where to implement AI. Okay? The third type of client will be someone who is interested and will also give you a hypothesis. I have used the word "hypothesis" here. The purpose of using the word "hypothesis" is that today we are going to find out what actually is a hypothesis, and what its role is in the process of Agentic AI. That is what we will be looking at today. And today's lecture will basically revolve around that. If we get the hypothesis, then we can build any agent in the world, God willing. But if we derive the hypothesis incorrectly, or if we don't understand the process of deriving the hypothesis, then no matter how many tools we get, no matter how much coding we know, no matter how many processes we understand, no matter how much understanding of nodes we have, those nodes that we read in the last lecture, they will be of no use. Getting my point? We have to understand the hypothesis. What actually is a hypothesis? Then I will break it down for you. And the second process I told you was that if you do a job, then either you will have to create the hypothesis yourself, or the hypothesis will be given to you. After that, you have to start your process. Okay? The things we are going to cover today, you will not find anywhere on YouTube. I have researched this extensively. Okay? So far, whatever has been built, if there is any confusion, any lack of clarity, tell me. You have two possibilities: either you will be freelancing, or you will be working a job. If you are freelancing, you will catch clients. Clients can be of three types. Okay? There is one person who has no interest at all. Okay? In AI. Okay? We will develop their interest in AI. After developing their interest, we will derive their hypothesis. The second type of client is interested, but doesn't know where to implement AI, so we will derive their hypothesis. Okay? The third type of client is interested and also knows. They also know the hypothesis. They will tell you the hypothesis. They will also tell you their interest. This is the client who will be our easiest to target client. Okay? They are telling us their interest, and they are also telling us what the process will be. Okay? In this case, we have to develop interest and define the hypothesis. In this case, we only have to define the hypothesis. And the second case is a job. In a job, either you will be given information and you have to create the hypothesis yourself, or you will be given the hypothesis, and then you have to start further implementation on it. Either way, tell me, let's move forward on the hypothesis. What is a hypothesis? If we understand the hypothesis with clarity, then our Agentic process will become crystal clear. Okay? Let's delve deeper into the hypothesis. Now, the concept of hypothesis is understood. In further lectures, we will also learn how to derive it. Okay? How it is structured. Okay? How it will be structured for a client who doesn't know AI at all. Okay? If you get the hypothesis, if you get this thing, then your Agentic AI process will be streamlined. Okay? Further, let's first understand what this word is that I have been repeating for so long. What does it mean? Hypothesis. Shall we move forward? Any confusion of any kind? Okay. Let's move on. Hypothesis means your flow. In simple terms, I will explain it further. In simple terms, your flow is called a hypothesis. If you understand this flow. For example, for example, I am using the example of tea. Okay? So that you all have an understanding from the first lecture. The hypothesis for tea will be, you know what it will be? Go to the kitchen, which we also call an algorithm in coding. Step-by-step process. Okay? After that, you go to the kitchen, or the A to Z step-by-step process that you will be following. Yes, absolutely. We will follow the process. For example, the client's client wants to build software. What does the client say? The client says, "Hey, I want to automate LinkedIn." So, what will you do first? You will draft a hypothesis in English. Write the hypothesis in English. Later, you will convert it into a diagram. The first step is to find the hypothesis, then convert it into the form of a diagram. If you have this done, then you just have to find the nodes. Your only task will be this much. Come to Agentic and just find the nodes. If this thing is clear to you, then this thing will be clear. If this thing is clear, then you just have to find the nodes. Nothing else will remain. 10 to 15. Yes, we will look at this further. That notations and gates, XOR gates, these are not taught in Agentic by anyone in my research. Business Process Management is not taught. This is called Business Process Management. Basically, if your Business Process Management becomes clear, then building an Agentic will become, as they say, a piece of cake. Hypothesis is the English explanation of the problem. Simple. A problem will come to me. Okay? I will define that problem in English. If it is a student management or student admission portal. Then first of all, the student goes to the university admission office. Okay? The admission office submits their details. The admission office officer processes their information and then sends it to the faculty staff, and the entire flow, you have to write it in English. Your first step will be to take the flow and write it in English. That's it. If there is any confusion up to here, tell me. If there is any confusion of any kind, tell me. Let's see an example. You have also kept the notes. These are university notes. Okay? University 11 notes, God willing, I will give you these in the classroom, God willing. Sir, tell me, is my laptop screen shared? And then let's continue on the laptop. Create a share so that I can continue. Okay, best. Sir, my screen is still not sharing, only your picture is coming. Let me see. No, still getting a problem. Others, please tell me. Is it showing to others? Sir, they need to change the view. There are different views from the bottom, so kindly ask the lady to change the view. Your view is coming from the bottom, please change it. Okay, sir. Where have you pinned me? No, no, it normally comes, right? Do this, you rejoin so that there is clarity. Is it showing to others? Okay? Show the notes. Okay? Now I will give you some examples of hypotheses. Here, all these are methods. Theory. We don't study in theory. We will be doing practical implementation. Okay? For butter, I will share it with you, God willing. I will show you an example for a process. I will show you a very basic example. Look at this, this is a hypothesis. Okay? Let's try to read it. The client is also done, right? Now I will break down the hypothesis into small parts. This is a process that this is an IT company, a construction company. Okay? Which specializes in doing this work. So, the existing process of the business works like this: whenever site engineers need any rental equipment, they fill out a form. Meaning, whatever processes are there, in short, whatever process we are going to automate, we have to write that process in short. This is your hypothesis. If you write this, then further things will start from here, and today we will see how to create a hypothesis. What are the processes? How do we create a hypothesis? We are going to see this process A to Z. Okay? Shall we move forward? Once we have the hypothesis, then tomorrow we will learn to draw the diagram, and then convert it. Okay? You will get diagrams and notations, and conversion will be up to you. I will share these notes with you, brother. Okay? Here you will find what the methods of process discovery can be. Back to my screen on the tab. What is the process? We follow. Okay? Sir, while creating a hypothesis, how will we know if our hypothesis is correct or not? We will see that too. Okay? This is all part of our testing, our evaluation. This research, if our research is not happening correctly, then what do we say? We will see further. We will be drawing diagrams on copy-pencil. Okay? There is also a concept of coding: the more your coding practice is on copy-pencil, the better your concepts will be, your logic will be better. Developers make the mistake of trying to jump directly onto the IDE, like VS Code, whatever it is. So, we have to do research first. Okay? This is a famous quote: If I have 10 hours to cut down a tree, I will spend 8 hours sharpening my axe. I will not jump directly to cutting the tree. I will prepare my tools. I will do my research. Okay? So, further, if we have to understand the direction in which our process is going, what things we have to do. Okay? If we have crystal clarity, then we will know that for this process, this activity is happening at this time. Okay? So, which node should be applied to this? If we gain knowledge of the nodes, what does this node do? What does it do? Okay? And if we don't know where it can be used, then what is the benefit of knowing what it does? Okay? Back to the steps. Okay? Our client is onboarded. The first type of client is not interested. We have to develop their interest. Whose interest? These are selling tricks. Communication skills. If some people from my previous batch are here, they know how much I focus on communication skills. So, this interest is related to my communication skills. For that, when I went for freelancing, you have further, they don't know where to implement AI in their business. They just don't know. Now, interest in AI has developed in their business. We told them that AI is this much, all and all and all. After that, they don't know where to implement AI. Okay? So, what will we do first? We will gather information from them. We will conduct interviews, meetings with them. Okay? Our very first task will be to meet them and audit their business. Business audit. That's why experienced Agentic AI engineers charge $1000 even for building a small agent. Although you might think, "Hey, it's just connecting nodes." So why such high charges? Connecting these nodes is the final process. Okay? 90% of developers are not doing the research. Because of this, scalability issues arise. Okay? In the future, if you want to scale, you won't be able to scale. If you haven't followed the right pattern. Okay? You have a lot of maintenance issues. Anytime. If you haven't used the right direction, the right pattern. Okay? Experienced people will do all this process first. That's why they charge so much. First, they will meet the client. They will audit the client's entire business. They will understand the client's business, how this business works. Okay? What processes are followed? Every business will be different. Every business will be different. Or you think that I will only work in healthcare. They can be similar. You should be open to work with anybody. Every business's processes will be different. If it's a construction business, it will operate differently. If it's a real estate business, it will operate differently. They will never give you 100% information. They will never give it to you because their business is running. You have to gather information from them, as much as possible, in these two or three meetings. And if you have the capacity to understand things, then in one or two meetings, you will understand their business, as they say, inside out, from vendor to delivery, what process is happening. You will understand the A to Z process because if you don't understand the process, how can you automate it? Okay? For example, if I have to automate the process of building a house, and I don't know how to build a house, how will I automate it? So, the first step would be to understand it myself, understand their business. And we don't have knowledge of every business. We have knowledge of agents. In the first meetings, we will get clarity on what this business is, what it does, what its processes are. Like the example of the admission office or IT company that I showed you earlier, how it works is that first, if its site engineer needs any new material, raw material, then they fill out a form, then the rental request goes, if the rental request is approved, then it goes to the vendor, raw material arrives, and so on and so on. These are all delivery processes. I understood this. After understanding this, I wrote it down. I kept all the information summarized with me. Okay? Now I have to interview. This is the hectic part. Here are the main processes. Okay? Our main process, our concern is not much with Agentic, because at the end, we will have the hypothesis. We will have its flow diagram. So, does it even matter if we use Agentic, Make, or custom coding? We are not dependent on tools, right? We have figured out the entire flow, how we need to automate this. So, it doesn't matter whether we are using Agentic, Make, or Zapier. For the sake of the course, we are using Agentic. Okay? We can use Langchain. Leng.com. It will be very easy for you to shift to tools later. Are you getting some clarity? That first, you will have meetings and understand their business, what their business does. Okay? You will audit their business, and you will do it for free, kind of, so that you want to do it. This process can be automated. This process cannot be automated at all, it totally depends on manpower and the production unit. So, you might understand that 10 processes can be automated, maybe three processes, based on business to business again. You understand that their customer care department uses 100 employees, and you can change that by building a bot. Okay? Or the meetings department, you can automate this. Or the production department, you can automate this to this extent. You will know this after understanding the business. Or you are basically offering this to the client as a pre-audit, but some companies also charge for this audit. But it depends on experience to experience, what your worth is in the market. You audit it, this is your investment, initial investment. You audit it and tell them the pain points. Okay? You onboard them. Now your further research process starts. Your hypothesis has not come out yet. Your research is still going on. Okay? If there is any confusion up to here, tell me. I am going a bit fast today. If there is any confusion, tell me. Is there clarity on things? Sir, I am understanding this, but it feels like a very big agency owner. Meaning, they are working at that level. If they have to meet someone or call them, then you will do it, God willing. If you are single, then our first step will be, for us, to approach someone, then have a meeting, travel, or call. We are learning Agentic, right? I told you that if you are only doing a job, the hypothesis will either be given to you beforehand by the company, because in 90% of cases, we give the hypothesis to our developers, and then they create diagrams and processes. Or in some cases, they say to derive the hypothesis yourself. If your scenario is that you want to go towards a job, then this will be your roadmap. But in either case, it is my duty to tell you how to derive the hypothesis. Sooner or later, you will have to follow this process, have meetings. Okay? Right now, you are small. So, you have to have the mindset. You should not think that if I am small today, I will operate at this level for my entire life, God forbid. Sooner or later, you will be closing big client meetings, big client deals. And if you don't know this process, then you will jump directly onto Agentic, you will build automation, you will build agents. I am not saying you won't build agents, but will it be scalable? Will its maintenance be done in the way it will be done after this research? Okay? If your foundation is clear, then things will align. What about the hypothesis? Sir, does it really matter if we are small or big? Meaning, the process is the process, right? Yes.
The process will remain the process. But do you know what the scenario is? The majority of developers are using n.com's tools in a particular way. They are directly jumping into the tools. 90 to 95% of development is happening this way. Because nobody knows about Business Process Management. I haven't seen Business Process Management in the process of any agent yet. In all the research I've done so far. Maybe it's happening somewhere. Okay? But according to my research so far, Business Process Management is zero in any process. Okay? And Business Process Management is a very old process. Okay? If there is an owner of a software house here, they will know that Business Process Management is an old concept, and without it, your things don't work. In this way, if you bring in a digital marketing client, you are still researching the client. Things are different. You don't directly start running Facebook ads for them. Just because I have a client, I'll start running their Facebook ads tomorrow, or if I have to do SEO, I'll start working on SEO today, or if I have to do website development, I have a client, I'll open my laptop and start coding. Things happen this way. I'm not saying they don't happen, but they are not scalable, they are not effective. Okay? Scalability, good programming, bad programming – these are the things that matter in the longer run. Inshallah, you will also be building on SaaS. Okay? So on SaaS, if direct sense is being used, software as a service that you are building, tools N10 are also being used in development. So, for example, if you get 1000 users and your program logic is wrong, your entire investment will crash. Or, for example, a client is coming. They are bringing their investment, and because of you, they are incurring a loss, so this is not justified. You have to code. You have to do any client's project. So, you should have this in mind: you are building a tool. Okay? There should also be empathy. I don't just mean that I have provided a service, I have to take money and leave. You will be processing every line of code, every thing. You are doing this as a trust. You should not do it in a way that you quickly hand over the work. So these things matter a lot. Scalability. Users are coming, so it's fine. It's working for 10 users. Your logic is not so good that 1000, 2000 users are coming, your tool crashes, your software crashes, then what will you be doing? Okay? So these things matter a lot. If your research is not correct, even if you are building a house, you are doing anything, you can do research. We have learned since childhood that the better the foundation, the better the building will be. If your foundation is not clear, and you are jumping onto NDM, then how much scalability are you talking about? Okay? So the best way to organize these things is BPM, Business Process Management. If someone is at the university level, this is a whole subject in university, Business Process Management. If someone is doing software engineering, they will have an idea. So where were we? We had done the audit. Sir, this is understood, Masha'Allah. But now, since we are all starting startups, we don't have that kind of training yet. So we have to start small, right? Everyone will do one or two projects slowly, slowly, slowly, and then it will happen. So what should our startup be? What should be the first step? Should we approach or our friend? How should we stand? How will we achieve the first client? That's about client acquisition. Client acquisition will be provided to you next, and I will also tell you further how to acquire. You are asking how to bring clients. Right now, I will do the agent's process, meaning what to do after the client comes to you. Okay? So you have to follow these steps. This is what I've been telling you from the beginning: if a client comes to you, there will be three types of clients. One person won't be interested at all. One will be interested. One will know what process they want to automate. From the beginning, this is what we are catering to. Okay? You will get clients. You will have three types of clients. Okay? Getting my point? Is it clear here, or should I explain again, Danish? Okay. You are acquiring clients. Can you hear me now? Yes, sir. Okay. You are acquiring clients, so you have to start this further process for the client. You have to follow the A to C journey. You have audited the business. After that, you will conduct further related interviews. For example, let's define a process. A business makes tea. Okay? You have found out that the process of making tea is this. You are getting a hypothesis. Now, someone asked how we will know if the hypothesis we have derived is correct or not. We will know this by conducting interviews. The first step will be to conduct interviews. For example, I will go and interview my grandmother about how she makes tea. Okay? Does this match my hypothesis? So my hypothesis, I'm calling them interviews, I follow it this way, I do it this way, it's correct. My hypothesis is correct here. We conduct interviews. Besides that, there are different sources. You read documentations. Your concern is that we are starting small, so they won't be that complex. Things will become complex, but you are not going to do only small projects, God forbid. You should have clarity that in the future, how you will build a house. You shouldn't have the concern that even if you are taking the first step, you will go up, Inshallah. You are reading documentations. Okay? You are conducting interviews. You are managing the process. This documentation also comes from the company's profile. The clients give it to you. Interviews tell you whether your hypothesis is correct or not. Otherwise, your hypothesis will become clear. Then your things will become clear. Your roles will become clear, right? For example, you have seen which roles are involved in this process. Okay? Like, in this process, there is an administrator. There is a student portal. Any process is working. You should have knowledge of all of them. Because if you have little knowledge, you will do wrong work, and that will cause loss. Sir, the sound is missing. And clients are non-technical. Is the sound clear now? Yes, sir, clear. All the methods I've mentioned so far are understood. If there is any confusion anywhere, please ask me. Okay? So, roles are defined here. For example, I am going to do a process. Okay? I'm giving the example of tea. So I have to automate making tea. Okay? The business makes tea. It says, "Please automate my process." Let's take an example. A business has come to me. Okay? It makes tea. It is interested in AI. It doesn't know where to implement AI in its process. Okay? Business makes tea. We will have a meeting with them. We will ask them, "What is your business process?" They will give you something like, "First, we do this, then we do this, then we do this, then we do this." You can define it on that page. Done. Okay? Okay. This will not be your final diagnosis. Again, you have done all this research, you have defined the hypothesis. You have told them. You can re-audit this. You can give an audit based on experience. This is how I have automated. Based on that hypothesis. Okay? After that, you will take the project. We will study what things are in "Win." What is the detention? I will share it with you, Inshallah. Now your project has started. You have made a graph hypothesis of how tea is made. Now you need to refine it. You need to test it, this hypothesis. After testing, you will make its diagrams, give it a flow. But the first task will be to test it, to test the hypothesis first, whether it is made correctly or not. Okay? For that, you will conduct interviews. How will you conduct interviews? You will ask the person who makes tea, "How do you make tea?" The owner has told you that this is our process. Tea is made. Okay? You will ask them how they make tea. They will give you a step-by-step process. You will match that step with your hypothesis. If it matches, well and good. Okay? Your hypothesis is correct. If not, you will conduct interviews again, analyze, and try to correct it. Who did it? Sorry, I lost my connection. I am not in my office right now. The internet connection is unstable. Where did we leave off last? Can someone please explain? What we left off last was testing the hypothesis. Sir, you said we have to test if the information we received actually works that way. We look at interviews. Okay? Whoever is involved in it, we look at them and interview them, asking, "How do you do it?" Okay? Like making tea. I will interview them about how they make tea. Okay? They will explain the process: "I make it this way." Then I will match it with my hypothesis to see if it's correct or not. If it's not, I will try to refine it and reach the hypothesis. Okay? Getting my point. See, once this thing is defined for you, your further tasks will become very easy. That is the English representation of a process, just okay. How are your processes managed? Your process is defined. Your process is explained. You have understood the process. Until you understand the process, how can you automate it? It's a logical question, isn't it? You don't understand the process, and you are going to automate it. So, these are the sequence of steps: how do I understand the process? Without understanding this, you can do automation, but it might be correct, or it might not be. Your probability of being correct is not very strong. If there is any confusion up to this point, please tell me. Let's move on to further notes. Yes, sir. This is okay, Masha'Allah. But in this, this is a whole process that you have explained so far. Now, if we follow this process, obviously the main work is what we have to create for them, and it will take time in all scenarios. Now, someone wakes up, sees a general problem, chooses a tech, thinks this business might have this problem. They generally create a solution in a week, run ads, and we are still in the research phase of what to give them, and they have already bought it by seeing their ad. First of all, you should not think that clients are very few and we won't get them. In every market, there are all kinds of clients. You have to find the right market. You will find the same agent's process for $300, $1000, $2500. Being in the market, I am telling you things, telling you the reality. You will get the same process for $300, $1000, $2500, and it can even be $5000. Now it's based on you. Okay? How you present yourself. You go to a restaurant. Okay? You go to a fancy restaurant. They bring you a boiled egg. You must have seen reels. Okay? There is a big fancy restaurant outside, in America, if I'm not wrong. There, a boiled egg is sold for who knows how many thousands of dollars. So they have presented the boiled egg in a different way. The way they present, the way you present yourself in the market, you will be getting similar projects. It's up to you. So there is so much work in the agentic field right now, and right now, I'm not bragging about how much work there is or isn't. Those who are in the market will know how much work there is in the agentic field right now. Okay? So you should not think that if I stay in this research, my client will leave. A client who is serious will understand that these are the things. Without this, I will tell you that without this, I will build it for you. I will build one. Okay? If you have a business, forget everyone. Okay? You have a business. One person is following the same process with you. And another person is saying, "Well, I'll build it for you." Okay? You are about to build a house. One person is saying, "First, I will look at the house. Then I will see how it should be designed." One person is designing it, looking at the intricacies, meaning proper work is being done. Then the other person is saying, "I will build the house for you in 10 days." As a business owner, whom would you prefer? So these are logical terms. So you should not be afraid that if I stay in research, the client will leave. I do my own software research. I have clients, Alhamdulillah. Okay? So this research pattern is followed in the market by big software houses. Business Process Management is a field of study. You can search only Business Process Management. So it's a field of study, and it cannot be neglected. Getting my point? Yes. Okay? So when you say client onwards, these things will matter. Okay? Do you want to capture high-ticket clients? My old students will know how much I have focused on this: capturing high-ticket clients. Not just because you get more money from them. Don't just capture high-ticket clients for that reason. You should capture high-ticket clients because they give you mental satisfaction. Okay? You will read about these things in freelancing lectures: what is a high-ticket client, what is a low-ticket client, how to approach them, what is the hunting process, and A to C things. Okay? Shall we move on? Yes. Yes, I will share samples with you, Inshallah, that are being shared in our software. Why not? Inshallah, because we will see processes, Inshallah, so that you get an idea, so that you get motivation, you get confidence. Okay? Hypothesis. Yes, Inshallah, we will see. If the hypothesis is clear, meaning this is the logical thing: you are going to automate a process, okay, using AI. If you don't know what it is, if there is no research on it, then how can you automate it effectively? I am asking a simple logical question. You don't know what something is, what that process is. How will you automate it? Tell me yourself. It will only be automated if we do it this way, right? The automation process will only start when I know that this process is managed in this way, this way, this way. Okay? Now, the hypothesis will tell me in English how this process works. Next, what do your diagrams do? I'll give you a diagram right away. Okay? We will see what a diagram is later. Looking at this diagram, can you easily convert it into N.T. or not? If you know the meaning of all these, how easy will it be for you to convert it into N.T.? If you know the meaning of all this, it will be very easy, right? Regardless of whether you are using .com, you are using it. Okay? Then you will not be tool-dependent. You have understood Business Process Management. You have understood management. You will just use the tool and say, "Oh, this is an hour's work. Just do it and deliver it." So, we derive diagrams from the hypothesis. Okay? Our first step is the hypothesis. The second step is diagrams. And after getting those diagrams, we automate the process using tools, actually getting our hands dirty. Okay? In some processes, okay? You will become so experienced, so experienced, Inshallah, that you will understand the process hypothesis in the first meeting. Okay? Time to time, based on experience to experience. Then, if these things are taking 10 days now, then all this work will be done in 2 days. Okay? Then it might be that all your work is done in one day. You have practiced, right? You have done client projects. You have understood client processes. Has the answer to your question also come: things will become faster? The first time you learned to write 'Alif' and 'Bay', you would write slowly, but now your handwriting is so fast. The more experienced you become, the easier things will become for you, right? Obviously. Okay? So it might take you a week for the first client, another week for the second client, but when you do 10, 20, 50 clients, are you sure it will still take you a week to do all these things? Okay? So I will show you an example. Our next process will be that you will be given an assignment in which I will only give you interviews of people. Okay? I will give you meeting notes. You will have to create the hypothesis. Okay? I will give some interviews. I will tell you some rules, and you will have to submit the hypothesis to me: this could be its hypothesis. Okay? Next, this will be your assignment: I will say, "Look, this is a company. Okay? This is the company's process. That company does this. After that, there are some employees of the company. We conducted an interview with them. So this is what they said. Okay? Now tell me, what will be its? Okay? What will be its process discovery? What will be the steps of the process? Okay? This is an assignment for the next lecture, and all previous assignments that have been completed must be submitted by me on Google Classroom. Whatever deadline I give you. Okay? This is something, if my screen is visible to you. Yes, Abdul Hafeez, thank you very much, sir. Okay, let's suppose a question for my clarification: can one hypothesis mean one, for the entire process, do we have to make one hypothesis? One hypothesis is one. Meaning, one process is one, right? I am automating it. Hypothesis means that, like, I am automating this process. So all the information about this process is with me. In short, in simple terms, this is my process.
Here are the details. I have to automate this now. It's possible that this is not a story-telling idea; there's no story-telling idea within it. These are all the details of the project, man. I have these, these are correct. All the details are here. Now I have to automate this. It's possible that we might have to design this ourselves. It's possible that the client might give it to us directly. Now, I have three types of clients. Right, right. Okay. Okay. Thank you. Okay. Because you won't always get a client who tells you exactly what they need. Some clients don't even know themselves what they want to automate. They just know that, "Hey, I'm interested here." So, you should also know how to handle them, right? You shouldn't lose them. Okay? You shouldn't lose them. So, for such clients, you will be discovering these requirements yourself. Some clients will surely give you hypotheses. Okay? We built this exact thing in the beginning, and they will be your most enjoyable clients. You won't have to waste any time on them. You get the hypothesis. You create the diagram, the automation, and the work is done. Okay? But if you haven't even done the process discovery, then it's nearly impossible to build it correctly, with testing, with scalability, with higher maintenance. Okay? So, our job isn't just to build automation. Our job is to build scalable, deployable, maintainable applications. Okay? Which we can use in the future for ourselves, for clients, and using tools. Okay? Shall we move on? My screen is shared. Okay? I have done process discovery for you. This is basically a method. You don't need to memorize it. Okay? This is a whole field of study. Business Process Management. Understanding business processes. Okay? But you absolutely don't need to memorize it. You need to understand the things. Okay? I'll tell you what can happen. You can conduct interviews. You can do observations. Okay? What is observation? You can go and sit in a restaurant yourself and start observing how tea is made. Okay? Observation. But how will you do observation online? So, observation won't be of much use to you online. Okay? You need to conduct interviews. Okay? See, your hypotheses are being validated through interviews. Okay? First, you collected relevant information. Okay? After collecting relevant information. Yes, I will upload it. Okay. It's not uploaded yet. I will upload it. That was a subject I studied in university. Okay? This is a subject that was taught to us in university. Business Process Management. Okay? This is your field study. I am taking this from my Google Classroom. It's an old subject from my teacher. Okay? Business Process Management is very important for you to know. After that, what do they say here? An interview was conducted here. Through this interview, we validated the hypothesis. We drafted the hypothesis. Okay? You don't need to do observation. Okay? Because observation is nearly impossible in online systems, in online workflows. Okay? After that, after taking all the information, you derived a hypothesis. Now, once you have the hypothesis, you will get the information for diagrams. The hypothesis arrived. It was represented visually. You represented it visually, so you knew what node was working at what time for what step. You just need to come to the tool. We understood all the nodes in that lecture. Okay? If it's a data processing node, go to data processing. Okay? If there's a human-in-the-loop node, use that one. If there are app actions, use the app one. Whatever the use, you will know that this node is for this app. Click, drag, apply. Then you will have this. In two to three hours, you will have all your specifications. In the next lecture, God willing, we will learn to create diagrams. Then we will move to further advanced steps on the tool, where we will look at advanced things. We will create processes ourselves. We will look at the concepts of the tool. We will be building a chatbot for the tool. We will look at the concept of MCP, what it is. Okay? Further, we still have a lot of the course left. Okay? Today is only our third lecture. We will be building advanced processes. We will be managing advanced APIs. We will be setting up advanced nodes. You will build three to four processes. Not even three to four, let's say you build ten processes. You will get a handle on one node. Okay? Because right now, you won't have a handle on the nodes at all. Right now, you will have the information that, "Hey, this node does this." It also has node settings. We still need to look at that. Okay? So, we will cover all these things, God willing, in future lectures. So, you will only start automation when you know what you need to automate. And if you don't even know what you need to automate, then what will you automate? Okay? So, your first step is to discover what I am going to automate. It's possible the client will give it to you. It's possible the client won't. But you won't waste your potential on that client, will you? You will say, "No, I will only start once you give me the requirements." Okay? You will let go of such a client, thinking, "Hey, they aren't interested in AI." I'll let them go. Or they don't even know where to implement it. I'll let them go. I'll only look for clients who know what they need. Who know they want to get a chatbot built. Who know they want to get an AI receptionist built. Okay? Don't look for clients like these. You need to look for all types of clients. Now, if you find such clients, you won't need to define hypotheses for them. They will come and tell you, "Hey, I have a business. This is my business. I need an AI receptionist for my business." They will also give you the details. I will also tell you how to train it. So, you have the hypothesis. Okay? But this is only 1/3 of the market. You have ruined your entire potential for the rest of the market. If I tell you now there are three types of clients, you are ignoring two types of clients. How much potential are you losing? And most software houses revolve around that type of client who gives you requirements upfront. And there is so much work in that field too. If someone has a software house, they will know. There is so much work in this area right now. Meaning, right now, AI is a gold mine industry. Billion-dollar startups are being built in AI right now. Okay? Specifically in Artificial Intelligence. If there is any confusion, any lack of clarity, let me know. All clear. Okay? I will briefly explain what we learned today. You people are about to enter the market. God willing, soon you will have two options. Two roads. Either you do freelancing, or you get a job. Okay? When you go for a job, you will be given requirements like, "Hey, build this automation for me." You got an automation. You built it. Or it's possible the owner or your project manager will say, "Hey, also get these requirements from the client." So, you will get the requirements, and you will build the automation. Okay? This is your job role. If you want to do freelancing, you will hunt for clients first. Okay? You will hunt for clients yourself first. When you are hunting for clients, you will find three types of clients. The first type of client will have no interest in AI. They won't know anything about AI, nor are they interested. You will educate them that, "Hey, AI is a booming industry. You can benefit from AI. You can grow your business." You will educate them. Now, they are educated. Now they have developed an interest. But they don't even know where to implement AI in their business. They just have an interest developed that, "Yes, AI is a good thing." So, you will have to figure out what automation to do in their business, right? If you don't even know what automation to do, then what will you do? Okay? The second type of client will say, "Yes, I am interested, but I don't even know where to implement automation in my business." So, how will you do their automation? You will tell that client, "Okay, I don't know the office." You will also do the automation for their business, right? The client is telling you, "Yes, I am interested. I have an interest in AI, but I don't know where to implement it." So, what will you do with that client? This is what you will do. You will discover the process first to see where I can do their automation. The third type of client will give you the requirements upfront. "Hey, I have this receptionist. I want to build an AI receptionist. Here are my company details. Here are my processes. Here is my data. Train it on this. Do this, do that." They gave it upfront. You worked on it and handed it over. Okay? So, these are the three types of clients. You need to capture the first two in the market. The first two are also a very big market. Okay? If there are 100 businessmen, only 10 businessmen out of 100 will know their requirements. That they need this specific requirement and they are hiring someone for it. 90 people will just have interest, or some won't have any interest at all. So, you will eliminate such a large addressable market. You need to capture that too. Okay? So, then all these processes will be followed for process discovery: "Hey, what do I need to automate?" This is the process discovery method. First, you will take them into meetings. You will audit their business. Okay? You will understand their business, thinking, "Hey, I need to automate their business. I don't even know what their business is. So, what will I automate?" I understood their business. I did a requirements analysis. I came up with a hypothesis. Now I need to see if this hypothesis is correct or not. I just came up with this by having meetings. Then I will conduct interviews with people who actually work there. Okay? It could be their project manager. It could be their technical staff. It could be their HR. By interviewing them, I will confirm my hypothesis that, "Yes, this is the thing that I need to automate." Now, okay? Now, again, it's possible the client will give you the requirements upfront. The client might not give them to you. The client who is giving you these requirements upfront is only 1/3 of the market. So, you will neglect 2/3 of the market this way if you don't know these things. Okay? And so far, in my research, I haven't seen anyone talking about this. Maybe some are. Okay? I am not sure about it. But as much as I have researched on YouTube, I haven't found it, nor have I seen among my acquaintances that anyone is trying to capture this area. Okay? So, you people need to capture this too. There is huge potential out there. You shouldn't just chase after those clients who have upfront requirements. Okay? If there is any confusion, let me know. All clear? Okay? Okay? Now, your next assignment will be this. All previous assignments that have been completed need to be submitted to Google Classroom. Okay? And your next assignment will be. I will give you business information. I will give you interviews. Okay? Collected, saying this is the scenario. You need to create a hypothesis for it. In the next lecture, from that hypothesis, we will be creating a BTM diagram. Once you have the diagram, then we will convert it into a tool. Clear? We will learn to convert to a tool after learning diagrams. We will learn at an advanced level on the tool. But before that, you need to know the process, right? What is it that I need to automate? If you don't even know that, then how will you do automation? It's possible the client will tell you. It's possible they won't. Clear? Okay. Then, God willing, I will update this on Google Classroom. God willing. And if anyone has any questions, any confusion, let me know. All clear. Okay? And we will end today's session, God willing. We will meet again in the new session, God willing. And if you have any questions, you can ask. Half.