You know how to deploy a Kubernetes cluster. You can spin up a CI/CD pipeline in your sleep. You've built full-stack apps that nobody's paying you for.
And yet — your bank account doesn't care about your GitHub commits.
I've been there. Sitting in my hostel room in Pune, mass-applying on LinkedIn, watching "how to get freelance clients" videos at 2 AM, and waking up to zero replies. I had real skills. I could build things. But the gap between knowing how to code and getting paid to code felt massive.
Then I stopped doing what everyone else was doing. I stopped applying. I stopped waiting. I started pitching.
Within 7 days, I had ₹10,000 in my UPI account. Not from a job. Not from a referral. From a cold DM to a stranger who needed something I already knew how to do.
This post is that exact playbook.
Fair warning: This is NOT a get-rich-quick scheme. There's no passive income hack here. This is an execution-heavy, slightly uncomfortable, very real blueprint. If you follow it, you'll have your first paid client by the end of the week. If you just bookmark it — well, you know how that goes.
Before We Start: You Only Need ONE Skill
Here's the lie nobody tells you: you don't need to be a full-stack wizard to get paid. You need one thing you can deliver fast and well.
Pick ONE from this list:
- Landing page development — HTML/CSS/React, delivered in 2 days
- Website speed optimization — PageSpeed audit + fixes
- UI bug fixes — that annoying button overlap, broken mobile nav
- CI/CD pipeline setup — GitHub Actions, Docker, basic deployment
- WordPress fixes — plugin conflicts, theme tweaks, migration
- Basic SEO cleanup — meta tags, heading structure, image optimization
That's it. One skill. One deliverable. You're not building a SaaS company. You're solving a small, painful problem for someone who doesn't have the time or knowledge to fix it themselves.
The bar is lower than you think. A local bakery owner with a slow Shopify site doesn't need a senior engineer. They need someone who gives a damn and can make the site stop lagging.
Day 1: Define Your Offer & Find Your Targets
Craft ONE clear offer
Not "I'm a developer, hire me for anything." That's a resume, not an offer.
Instead:
"I will improve your website loading speed by 40% — or you don't pay."
"I'll build you a clean, mobile-responsive landing page in 48 hours."
"I'll set up automated deployment for your project so you never manually FTP again."
See the difference? Specific. Outcome-based. Time-bound. Easy to say yes to.
Find 10–20 potential clients
This is where most devs give up before starting. "Where do I find clients?" Everywhere. You're just not looking.
LinkedIn — Search for "founder," "startup," or "freelancer" in your city. Look at their websites. Most are broken or slow.
Twitter/X — Search "need a developer" or "looking for someone to fix my website." People literally post this daily.
Google Maps — This one is underrated. Search "restaurants near me" or "gym in [your city]." Open their websites. Run a quick PageSpeed test. 8 out of 10 will score below 50. That's your in.
IndieHackers / Product Hunt — Founders launching MVPs often need quick dev help but can't afford agencies.
Make a simple spreadsheet: Name, Website, Problem You Spotted, Contact Info. Don't overthink it. Ten names. That's today's job.
Day 2: The Cold Pitch (This Is Where Money Lives)
This is the hardest day. Not technically — emotionally.
You're going to message strangers and offer your help. Your brain will tell you it's spammy, it's desperate, nobody will respond. Ignore it. This is how business works.
The psychology of a good pitch
Three rules:
- No begging. You're not asking for a favor. You're offering value.
- No essays. Keep it under 5 lines. Busy people don't read walls of text.
- Lead with a specific observation. Show them you actually looked at their stuff.
The template that works
Here's the exact message format. Steal it:
Hey [Name],
I checked out [business name]'s website and noticed it takes
around 5 seconds to load on mobile. That's likely costing you
visitors — Google says 53% of users leave if a page takes
over 3s.
I can get that under 2 seconds. Want me to send a quick
free audit showing exactly what's slowing it down?
— [Your name]
That's it. No portfolio link. No "I'm a full-stack developer with 2 years of experience." Nobody cares about that in a first message. They care about their own problem.
Send this to all 10–20 people on your list. LinkedIn DM, email, Twitter DM, Instagram DM — whatever works. Expect 2–3 replies. That's normal. That's enough.
The free audit trick
If someone says "sure, send me the audit" — this is your golden moment. Spend 20 minutes:
- Run their site through PageSpeed Insights
- Record a 2-minute Loom video walking through the issues
- End with: "I can fix all of this in 2–3 days. Want to hop on a quick call?"
The Loom video is the secret weapon. It takes almost no effort but feels incredibly personal and professional. Nobody else is doing this. That's your edge.
Day 3: Secure the Gig
Someone replied. They're interested. Now don't fumble it.
The call (keep it short)
If they want to talk, keep it under 15 minutes:
- Ask what's frustrating them about their site/tool/workflow
- Repeat their problem back to them (this builds trust instantly)
- Say: "Here's what I'll do, here's how long it'll take, here's what it costs."
Set the terms clearly
Don't wing it. Before you start any work, agree on:
- Scope — Exactly what you'll deliver. "Improve PageSpeed score from 35 to 75+" is clear. "Make the site better" is not.
- Timeline — 2–3 days for most small projects. Be realistic.
- Price — ₹5,000 to ₹10,000 for your first gig is the sweet spot. Don't undersell yourself, but don't price yourself out either. You're building proof, not maximizing revenue yet.
- Payment — 50% upfront, 50% on delivery. Non-negotiable. UPI, bank transfer, whatever's easy. If they refuse to pay anything upfront, walk away. Seriously.
Send a short WhatsApp or email summary of what you agreed on. Nothing fancy — just the scope, timeline, price, and payment terms in plain text. This protects both of you.
Day 4 & 5: Deep Work — Build Fast, Build Smart
You've got the gig. Now deliver like your reputation depends on it — because it does.
The execution mindset
Two rules for these 48 hours:
Speed > Perfection. Your client doesn't care if your code is artisanally crafted. They care if their site loads fast and looks good on their phone. Ship working results.
Don't build from scratch. Use every shortcut available:
- Templates — Tailwind UI, free HTML templates, shadcn/ui
- Frameworks — Next.js, Astro, Hugo — whatever gets you to done fastest
- AI tools — Use Claude, Copilot, whatever helps you write boilerplate faster
- Open source — There's an npm package for almost everything. Use it.
If your gig is speed optimization: lazy load images, compress assets, enable caching, defer non-critical JS. You know this stuff. Just do it systematically.
If it's a landing page: grab a clean template, customize the content and colors, make it responsive, deploy on Vercel. Done in a day.
Track what you're doing
Take before/after screenshots. Record your PageSpeed scores before and after. Save them. This becomes your portfolio and proof for the next client.
Day 6: Revisions & Making Them Happy
Don't just dump a link and disappear. How you deliver matters as much as what you deliver.
Present your work properly
Record another short Loom video (3–5 minutes):
- Walk through what you built or fixed
- Show before/after metrics
- Highlight specific improvements they asked for
- End with: "Let me know if there's anything you'd like tweaked."
This takes 10 minutes of your time but makes you look incredibly professional. Most freelancers just send a link with "done." You're already ahead.
Handle revisions gracefully
They'll have feedback. Maybe the color isn't right, or they want a section moved. This is normal. Do it quickly, do it cheerfully. Two rounds of minor revisions should be included in your price. Anything beyond that is a separate conversation.
The goal today is simple: make them feel like they got way more than they paid for. That feeling is worth more than any marketing you'll ever do.
Day 7: Get Paid & Set Up Your Flywheel
Collect the remaining payment
Once they approve the work, send a polite message:
"Glad you're happy with it! Here's my UPI for the remaining ₹[amount]. Also happy to help with anything else down the road."
Clean. Professional. No awkwardness.
Now — ask for two things
This is the step that separates one-time freelancers from people who build real income:
1. A testimonial
"Hey, would you mind writing 2–3 lines about your experience? A LinkedIn recommendation would be amazing, but even a screenshot of a text message works."
Get this in writing. Screenshot it. This is your social proof for the next 10 clients.
2. A referral
"If you know anyone else who might need similar help, I'd really appreciate an intro. No pressure at all."
One happy client who refers you to two friends is worth more than 100 cold pitches. This is how freelancing actually scales — not through more cold outreach, but through warm referrals from people who trust your work.
What Happens After Day 7
You now have something 90% of developers don't:
- Proof that someone paid you for your skills
- A testimonial you can show the next prospect
- A process you can repeat
Here's the next move:
Week 2: Pitch again. But now your message includes "I recently helped [business] improve their site speed by 50%." That one line changes everything.
Week 3: Raise your price slightly. ₹7,000 → ₹10,000 → ₹15,000. Each successful project gives you leverage.
Month 2: Start posting about your work on LinkedIn and Twitter. Share before/after screenshots. Write about what you learned. The clients start coming to you.
Month 3: You're no longer cold pitching. You have a small reputation, repeat clients, and referrals. This is the inflection point.
The Real Talk Section
I'm not going to pretend this is easy. Here's what actually happens:
- You'll send 20 messages and get 18 rejections or zero replies. That's normal.
- Your first client might haggle on price. Don't take it personally.
- You'll underestimate how long something takes. Pad your timeline by a day.
- Imposter syndrome will hit hard when someone actually says yes. Push through it.
- Your first delivery won't be perfect. It doesn't need to be. It needs to be done.
The developers making money aren't more skilled than you. They just started.
Your ₹10,000 is Waiting
You already have the skills. You've built projects. You've solved problems. The only thing missing is someone paying you for it — and that's a distribution problem, not a skills problem.
Stop learning another framework. Stop watching another tutorial. Stop telling yourself you need one more project on your portfolio before you're "ready."
You're ready. You've been ready.
Your first ₹10,000 isn't about skill. It's about action. And the only action that matters right now is sending that first message.
Open LinkedIn. Find a founder. Look at their website. Send the pitch.
Seven days from now, you'll either have money in your account or another week of excuses. Your call.
If this lit a fire, my DMs are open. First 10 people who comment "START" get my DevOps / CKA / Terraform cheat sheets for free. No strings attached — just want to see you win.
Top comments (0)