Interesting how just a few live demos convert better than lots of repos, nice one, did clients care more about UI polish or the problem solved?
How I Built a React Portfolio in 7 Days That Landed ₹1.2L in Freelance Work
7 Comments
This is such a practical and inspiring walkthrough! I love how you kept the stack minimal React, Vite, Tailwind, Vercel and focused on shipping a portfolio that actually converts rather than over-engineering. The step-by-step approach, especially the reusable ProjectCard components and live demos, makes it clear why clients responded so quickly.
It’s motivating to see that a clean, honest portfolio can lead to real freelance opportunities in just a couple of weeks. Definitely taking notes on your tips for targeting Indian clients and leveraging LinkedIn visibility. Thanks for sharing your process and results it’s exactly the kind of guidance beginners and even intermediate developers need to get started with freelance work!
Please log in to add a comment.
This is a great example of something a lot of devs underestimate: it wasn’t the portfolio itself that made the money—it was the fact that it was shipped, visible, and usable by clients.
The part that stood out to me is how strongly this reinforces a simple idea: clients don’t care about your learning journey, they care about proof of delivery. A live demo beats a GitHub repo every time because it shows you can go end-to-end, not just write code .
What’s also interesting is how “unfancy” the stack is. No over-engineering, no chasing trends—just React + Vite + Tailwind, deployed fast. That aligns with a broader pattern: reducing complexity often accelerates outcomes (both in code and in career).
If I had to add one nuance though: the portfolio got attention, but the distribution strategy did a lot of the heavy lifting too. Posting in the right places, engaging on LinkedIn, and actively reaching out is what turned a portfolio into paid work .
So the real takeaway isn’t just “build a portfolio in 7 days”—it’s:
- Ship something real
- Make it easy to trust
- Put it in front of the right people
Curious if you’ve seen this too—do you think most devs struggle more with building the portfolio, or with actually putting it out there?
Please log in to add a comment.
This is a really practical breakdown, especially the emphasis on keeping things simple and focusing on a small set of solid projects instead of overbuilding the stack.
From what I’ve seen, especially on the dev side, the biggest difference isn’t really the tech stack itself—it’s how quickly you can get something live that people can actually interact with. A working demo almost always does more for conversions than a technically “perfect” setup sitting unfinished.
I also agree with the idea of not overengineering early. A lot of devs (myself included at some point) end up spending more time optimizing the setup than actually shipping something usable.
One thing I’m curious about—did you find that certain types of projects (landing pages vs more complex apps) converted better in your case?
Please log in to add a comment.
Please log in to comment on this post.
More Posts
- © 2026 Coder Legion
- Feedback / Bug
- Privacy
- About Us
- Contacts
- Premium Subscription
- Terms of Service
- Refund
- Early Builders
More From Dharanidharan
Related Jobs
- iOS developer - React nativeInterSources · Full time · Atlanta, GA
- Android developer - React NativeInterSources · Full time · Atlanta, GA
- React.js Developer with Core .NETArtech · Full time · Minneapolis, MN
Commenters (This Week)
Contribute meaningful comments to climb the leaderboard and earn badges!