Skip to main content

How an AI Student is Earning from LinkedIn — and What I Learned from a 17-Minute Call

A few days ago I saw a post on Facebook. Someone sharing that he had started learning AI, done some projects, and was now earning from it. I asked him how. He said he got a client through LinkedIn. I asked him to elaborate. He said let's talk.

Seventeen minutes on WhatsApp. That was the whole conversation. But it connected more dots than months of reading about "the opportunity in AI."

The problem with how most people learn AI

AI is a wide field. Machine learning. Deep learning. Model development. Model deployment. Data analysis. Data analytics. Automation. Most people learning AI are aware of all of these — and that awareness becomes the problem. They keep exploring, keep switching, keep adding things to the list. A year passes and they are still learning.

He told me something simple: to stand out and to get clients, you have to focus on one thing.

His one thing is RAG — Retrieval Augmented Generation. Not AI in general. Not even a broad category within AI. One specific thing inside a specific category. That is where all his energy goes.

When you focus on one thing, you stop wondering where the clients are. You start seeing exactly where your work fits — in this business, in that business, for this problem, for that problem. And people approach you.

How he actually gets clients

He does not do outreach. He does not send cold messages. He posts his projects on LinkedIn — specifically, projects related to RAG — and shares them in a realistic and valuable way. GitHub links included. Real detail, not just a screenshot.

People see the work. They visit his profile. They reach out and ask if he can build something similar for them.

That is the entire system.

What the LinkedIn profile does

When someone lands on his post and gets interested, the next thing they do is visit his profile. So the profile has to do its job in seconds. He was clear about this — the headline and the description matter more than most people think. The headline needs to be specific and include the right keywords so he also appears in search results. The description needs to be clear about exactly what he does.

He only connects with people in his niche. Content creators and professionals posting about RAG. Everyone else he ignores. The network stays focused because the work stays focused.

One more thing he mentioned

He also attends learning institutes — physical places where people gather to learn and work together. Because he was already known for one thing, teachers there offered him projects as well. He did not ask. The focus did the work.

He experiments with new things too — AI moves fast and he stays curious. But the core never shifts. RAG is still the center.

What this made clear to me

Everyone says there is a lot of opportunity in AI. A lot of money. A lot of potential. I used to hear that and think — where exactly? I could not see it. I could not point to it.

After this conversation I understood why. The opportunity becomes visible only when the focus is narrow enough. When you know one thing deeply, you start seeing every place it can be applied. Every business that needs it. Every problem it solves. The opportunity was always there. The focus is what makes it visible.

Seventeen minutes. That was all it took.

Comments

Popular posts from this blog

Earning after the advent of AI, the 3 paths and things that matter

I have received this question more times than I can count. Are jobs gone? Is AI taking over everything? Why are internships not coming through? What do I do with my degree or my skill? Here is my honest answer — not a motivational one. AI has made things easier, and harder at the same time. Because AI can now do multiple things, the person who knows how to get the right things done from AI is preferred over the one who does not. That is the new baseline. Learn the basics of AI regardless of which path you choose — not to become an AI engineer, but to use it well in whatever you are doing. Beyond that, I see three paths. Each one has its own direction. The mistake most people make is not choosing one and going deep on it. Path 1: Build a Personal Product This is the path I am on. I will be honest about where my experience ends. Start by finding a problem — ideally one you personally face. That is your built-in validation. If you have the problem, others likely do too....

A user found the bug I should have caught myself

I was collecting user feedback on Iqra a few weeks ago. One of the users pointed out a bug. A section of the app was not working correctly. I knew the section. I had made changes to it recently — and shipped them directly to production without running through my usual testing flow. A user told me about the bug. Not my emulator. Not my test release. A user. I fixed the bug, made a few more improvements, added some things to the app. When I finally sat down to build the test release properly, this came back to me. So here it is — written down, for anyone building a product right now. The flow that actually protects you Every change, no matter how small, goes through three stages before it reaches your users. First, test on the emulator. Catch the obvious breaks early, before anything leaves your machine. Second, publish a test release and run it on a real device. The emulator lies sometimes — screen sizes behave differently, performance feels different, interactions that ...