I want to talk honestly about how the money actually works. Not aspirationally — concretely, with what I've charged and what the clients got.
In the last 12 months: a multi-location salon chain in Mumbai, a D2C food brand in Bangalore, a small manufacturing company in Pune, a CA firm in Delhi, and a logistics aggregator in Hyderabad. Each paid between ₹75,000 and ₹2,50,000 for custom web applications. None of them came to me through Upwork or Freelancer. All of them came through referral or direct outreach. All of them have referred at least one other client. All of them are on a monthly retainer for support and iterations.
The total from those five clients alone — project fees plus six months of retainers — is more than most employed developers earn in a full year in India. I'm not saying this to impress. I'm saying this because the path is replicable and it's not what most freelancers are doing.
Why solving problems pays more than building websites
When a client hires you to "build a website," you're in a competitive category. They have quotes from 4 other developers. The conversation is about price. When a client hires you to "fix the fact that we're losing 20% of our leads because our follow-up system is manual and slow," you're in a much smaller category. Maybe you're the only person who identified the problem and came with a specific solution. The conversation is about whether you can actually deliver, not about whether someone cheaper exists.
The problem-solving frame changes the client relationship from the start. You're not a vendor they hired to execute a spec. You're someone who understood their business well enough to identify something they'd been living with and offered a specific fix. That dynamic creates trust differently than any number of portfolio pieces or testimonials could.
How referrals actually work
Every referral I've received has come from a client who got a specific, tangible result — not from a client who was "satisfied" with the work. The salon chain's operations manager stopped manually updating a spreadsheet at the end of every day. That change was visible and impactful. When her contact at another salon chain mentioned they were looking for a developer, her recommendation was specific: "This person found the thing that was slowing us down and built something that fixed it in 3 weeks." That's a different referral than "he built a good website."
The implication: the quality and specificity of your outputs is your marketing. Every project where you identify a real problem and eliminate it is a referral-generating event. The quality of your portfolio on your website matters far less than the result you produced in the last project.
The outreach approach for new clients
When I do outreach, I don't send "Hi, I'm a web developer with 5 years of experience" cold emails. I look at a specific business, identify a visible problem — usually from their website, their Google reviews, or their public social media — and write a short message that says: "I noticed [specific thing]. Businesses in your space often have [specific underlying problem behind that thing]. I've fixed this for [similar business type]. Here's one thing you could change this week." No hard pitch. No portfolio link in the first message. Just a specific observation that shows I've thought about their situation.
The response rate on this kind of outreach is dramatically higher than generic pitches. Not because I'm a better salesperson but because the message is valuable to the recipient even if they don't respond. Some of them act on the suggestion themselves and come back later. Some respond immediately. Some ignore it but remember my name when a colleague asks for a recommendation two months later.
Building content that attracts the right clients
Posts like this one — describing the problems I solve, the process I use, and the results I produce — create inbound enquiries from founders who are dealing with exactly these issues. The person who reads about how I found and fixed the logistics company's WhatsApp-to-spreadsheet problem and immediately thinks "we have the exact same thing" will contact me. They're already pre-sold on the approach before we speak.
The content doesn't need to be frequent. It needs to be specific and real. One detailed post about a real problem you solved, what it cost the client before, and what changed after, is worth more than 30 generic "I offer web design services" posts on LinkedIn.
If you're a developer or designer who builds real things and solves real problems — the approach I'm describing here is available to you immediately. You don't need a large following. You don't need years of experience. You need the habit of asking "what problem does this person actually have" before "what should I build for them."
The pricing mindset that changed everything
The single biggest shift in how I earn money came from changing how I think about pricing. I used to price based on time: hours estimated × hourly rate. The problem: this caps your earnings at the hours you can work, and it makes every conversation with a client feel like a negotiation about time.
Now I price based on value: what is the problem worth to the client if I fix it? The manufacturing company whose manual inventory process costs ₹40,000/month in staff time — fixing that is worth ₹3–5 lakh to them. Pricing the fix at ₹1,20,000 is genuinely reasonable for both sides. When I price based on hours at my day rate, the same project might come in at ₹60,000–80,000. I'm leaving money on the table and the client still wins more.
Value-based pricing requires you to understand the problem's cost before proposing a solution. That's why the discovery session is essential — it gives me the information to price correctly. A client who tells me "we have three people spending 2 hours per day on this process" at ₹500/hour is telling me the problem costs ₹3,000/day, ₹90,000/month. My solution, whatever it is, is priced below the break-even point and the algebra is obvious to both of us.
The freelancers who earn the most in India are not the ones who work the most hours. They're the ones who've solved the right problems and understand how to price against the value they deliver rather than the time they spend. This is learnable. The first step is simply asking "what does this problem actually cost you" before you say a number.
The practical entry point: start by asking your next prospective client "what's the most time-consuming thing your team does every week that feels like it shouldn't require a person?" Most business owners have a clear answer. That answer is your discovery. The fact that they told you voluntarily means they're already half-sold on fixing it. Value-based pricing follows naturally from the diagnosis.
Also read: How I build full websites in under an hour and How I find business bottlenecks and build web apps.