About Skills Work Journey Blog Contact
Career · 6 min read · October 2025

Getting Your First Freelance Client as a Developer

The hardest part of freelancing isn't the work — it's getting the first client. Before you have case studies, before you have testimonials, before anyone has heard your name, you have to convince someone to pay you for something you've never been paid for. Here's what actually worked for me.

The Portfolio Problem

The standard advice is "build a portfolio." But most developer portfolios are useless for getting freelance work because they're built for other developers, not for clients.

A client doesn't care which libraries you used. They care about one thing: can you solve my problem?

Your portfolio needs to speak to that. For each project, lead with the outcome — not the stack. Instead of "Built a React app with Supabase backend," say "Built a job platform that helps Canadian developers find roles 40% faster." The tech is footnote material.

Who to Target First

Forget Upwork and Fiverr for your first client. The platform takes a cut, the race-to-the-bottom pricing is brutal, and you're competing with people who've already got 500 reviews.

Better targets for your first client:

  • Local businesses with bad websites. Restaurants, gyms, law firms, real estate agents — nearly every small business has a website that was built in 2015 and never updated. They know it looks bad, they just haven't got around to fixing it.
  • Your existing network. Who do you know who runs a business? A parent, a friend's parent, a former colleague? Tell them you're doing web work. You'd be surprised how often this leads somewhere.
  • Niche communities online. Find a community of people in a specific industry and become a known presence. Reddit, Discord, Slack groups for specific verticals. People hire people they recognise.

Cold Outreach That Actually Works

Most cold outreach fails because it's about the sender, not the recipient. "Hi, I'm a developer, I'd love to work with you" is not an offer. It's a request for the recipient's time and attention with nothing in return.

A better structure:

  1. Identify a specific problem — look at their website and find something genuinely broken or outdated
  2. Lead with the problem — "I noticed your site doesn't load on mobile" is something they can verify instantly
  3. Offer something small first — "I put together a quick mockup of how I'd fix the mobile layout. Happy to share it."
  4. Short and specific — three sentences max. Long emails don't get read.

The mockup offer is the key. You're doing a small amount of work upfront, but it demonstrates competence immediately and gives them something concrete to respond to. It filters for people who are actually interested rather than politely brushing you off.

Pricing Your First Project

Don't work for free. Ever. Free work attracts bad clients, devalues your time, and sets a precedent for the relationship. If you're not confident in your pricing, charge less — but charge something.

For a first project, I'd suggest pricing based on value, not hours. A new website for a local restaurant might generate them $5,000 in extra bookings over a year. Charging $800 for that is a great deal for them and fair for you. Charging $20/hour for 40 hours gets you the same money but puts you in a time-for-money trap.

A simple pricing framework for landing pages and small sites:

  • Simple landing page: $500–800
  • Multi-page business site: $1,000–2,500
  • Custom web app: scope it first, then quote

These might feel high if you've never charged before. They're not. They're below market rate. Raise them once you have one or two clients.

The First Meeting

When you get a call, don't pitch — listen. Ask them to describe the problem in their own words. Ask what they've tried. Ask what success looks like to them. Take notes.

The goal of the first meeting is to understand the problem well enough to scope a solution, not to sell yourself. If you've listened well, the proposal writes itself — you're just describing back to them what they told you, with a price attached.

After You Land It

Delivering good work is table stakes. What sets you apart as a freelancer is communication. Send a weekly update even when there's nothing dramatic to report. Tell them before a deadline slips, not after. Ask for feedback before you think you need it.

Most freelancers lose clients not because the work was bad but because the client felt out of the loop. Over-communicate and you'll get referrals.

The first client is the hardest. After that, if you do good work, referrals compound. I've never needed to cold outreach for the same industry twice — one good project in a vertical leads to more in that same vertical.
Share

More Writing