Land your first client this week:
Open LinkedIn.
Search past colleagues who became founders or managers.
Message 10 of them: "I'm taking on consulting work. If backend/scaling ever bites you, I can help."
That's it.
Warm leads beat cold pitches every time.
Land your first client this week:
Open LinkedIn.
Search past colleagues who became founders or managers.
Message 10 of them: "I'm taking on consulting work. If backend/scaling ever bites you, I can help."
That's it.
Warm leads beat cold pitches every time.
Full-time at ₹80L looks great.
Until you realize:
One client relationship.
One performance review.
One layoff away from zero.
Three clients at ₹35L = ₹1.05Cr.
More money.
Three separate reasons you don't panic when the market turns.
@arpit_bhayani I see a lot of junior developer sdon't write the code AI writes.
We had to optimize an API that took 7+ minutes recently.
When we removed db calls inside loops, without any architectural change, the latency came down to 30 seconds.
Read the code that AI writes!
The math nobody shows developers:
One full-time job: ₹1Cr/year. One boss. One point of failure.
Three consulting clients: ₹60L each. ₹1.8Cr total.
More money.
Spread risk.
If one leaves, you still have two.
Most engineers never start consulting because they wait to feel "ready."
You don't need a brand.
You don't need 10k followers.
You need one problem, one client, one invoice.
Start there.
The rest compounds.
10 years of backend work taught me one freelancing truth:
Clients don't pay for code.
They pay to stop worrying.
The engineer who says "I've got this" wins over the one with the fancier stack.
Nobody tells you this about consulting:
Your rate isn't tied to your skill.
It's tied to how expensive the problem is that you're solving.
Fix a $10k issue, charge $10k.
Learn to find those problems.
@merishabh_singh I have ~11 years of experience as a backend developer/lead.
I have worked mostly in startups.
Would love to connect to discuss potential opportunities.