How to Land Your First Freelance Client as a Student (With No Experience)

Everyone says "just start freelancing." Nobody says how you get the first client when you have no reviews, no portfolio full of paid work, and no idea what to charge.

That's the catch-22: clients want experience, and you need clients to get experience.

I'll be honest up front. Your first client rarely arrives from a magical platform or a viral post. It comes from a small, specific offer put in front of the right person. This guide walks through exactly how to do that, step by step, without pretending it's easy or promising numbers I can't back up.

1. A Quick Reality Check

Before we get into tactics, let's set expectations:

• The first client is the hardest. The second is easier, the third easier still.
• It's slow at the start. Expect weeks, not days.
• Money will be small at first. The bigger prize is proof: a real project, a real testimonial, a real story.
• It's a skill of its own. Finding clients, scoping work, and communicating well matter as much as coding.

None of this should discourage you. It should make you patient, which is the trait that separates people who land clients from people who give up after three cold messages.

2. Think of It as Fishing in the Right Pond

Imagine fishing in the middle of the ocean with a huge net. You'll catch a lot of water and very little else.

Now imagine picking one small pond where you know the fish are hungry, and using the right bait. Much better odds.

Beginner freelancers usually do the ocean version: "I'm a developer, hire me!" posted everywhere, aimed at everyone. Nobody knows what to do with that. The winning move is the pond version: choose one type of client and one specific problem you solve for them.

3. Pick Your Pond (Your Niche)

Look close to home, at people who need something simple built and don't know where to start:

• Local shops, cafés, salons, and restaurants without a website, or with an outdated one
• Coaching centers, tuition teachers, and training institutes
• Student clubs, college events, and societies
• Small event organizers, photographers, and freelancers who need a portfolio site
• Family-run businesses that still take orders by phone or chat

Pick one group you understand. Knowing your audience makes your pitch sound sharper, because you can speak their language.

4. Make One Narrow, Clear Offer

"Full-stack web developer" tells a shop owner nothing. Compare that with:

• "I build simple one-page websites for local restaurants, with menu, location, and a contact button."
• "I redesign outdated landing pages so they load fast and look good on phones."
• "I set up a small online booking form for salons and coaching centers."

A narrow offer is easier to understand, easier to price, and easier to say yes to. You can always widen it once you have clients. Start with something you can deliver confidently in a couple of weeks.

5. Build Proof Before You Pitch

You don't have paid work yet, so create the next best thing.

• Make two or three sample projects that match your offer. A demo restaurant site, a mock landing page for a coaching center, a booking form.
• Do a concept redesign of a real local business's site or page, clearly labeled as a concept, and share it with the owner. Get their permission before you publish anything with their name or branding.
• Put it all in a portfolio with a short explanation of the problem and what you built. If you don't have one yet, my post on building your first portfolio site covers it, and the one on GitHub profiles helps too.

Three solid samples beat ten half-finished ones. What people want to see is that you can take a real need from idea to a working result.

6. Where to Find Your First Client

Start warm, then go wider.

1. People you already know. Family, friends, classmates, teachers, club mentors. Tell them clearly what you do, and ask if they know anyone who needs it. This is how a huge number of first clients actually happen.

2. Local businesses. Walk in, message on social media, or send an email. Mention something specific you noticed, like their site loading slowly on a phone or having no online menu.

3. Communities. Student groups, local tech communities, Discord servers, and group chats. Be useful first. Answer questions, share what you're building, and let people see you're capable.

4. LinkedIn and social media. Post about your projects, share what you learn, and tell people you're open to small projects. Consistency pays off here.

5. Freelance platforms. Upwork, Fiverr, and similar sites exist, but they're crowded, and newcomers with no reviews have a tough time. They can work if you take a few small, well-scoped gigs to collect reviews, though I wouldn't make them your only plan.

7. How to Reach Out Without Being Annoying

Cold messages work when they're short, specific, and easy to say yes to. Compare a lazy message with a good one.

Lazy:

Hi, I'm a web developer. Do you need a website? I can build anything.

Better:

Hi [Name], I came across [Business] while looking for [something they offer] and noticed the site is hard to use on a phone. I'm a student developer who builds simple, fast websites for local businesses. I put together a quick mockup of what a mobile-friendly version could look like. Would you like me to send it over? No pressure at all.

Why the second works:

• It shows you actually looked at their business
• It names a real problem
• It offers something small and concrete
• It asks for a tiny next step, not a big commitment

Send a polite follow-up after several days if you hear nothing. People are busy, and silence usually isn't a no. Don't send fifty identical messages, though. A handful of thoughtful ones beats a flood of copy-paste.

8. What to Charge

This is the scary part, so let's make it simple.

• Don't work free forever. Free work attracts people who don't value it and teaches you to undervalue yourself. One low-priced or discounted project in exchange for a testimonial and permission to show the work is a reasonable trade for a first client.
• Estimate your time. How many hours will this really take? Add a buffer, since almost everything takes longer than planned.
• Check what others charge. Look at local market rates for similar work, and adjust for your experience honestly.
• Quote a fixed price per project when you're starting out, so the client knows what they're paying for.
• Never work "for exposure" with no clear scope. If a client can't say what they want, that's a warning sign.

Your prices will go up with every project. Your first quote is a starting point, not a life sentence.

9. Agree on Scope in Writing

Most freelance horror stories come from vague expectations. Before any work starts, write down (even in a simple email or document):

• What you'll deliver, in plain words
• How many rounds of changes are included
• The timeline
• The price and when you'll be paid, ideally with an upfront deposit
• Who provides what, like text, images, and logos
• Who owns the accounts. Hosting and domain accounts should be in the client's name.

Anything extra later is a new request with a new price. This isn't rude. It's what makes the project smooth for both sides.

I'm not a lawyer, so for bigger projects consider getting proper advice. Also check the local rules about reporting income and any policies your college has about outside work.

10. Running the Project Well

Winning the client is half the job. Keeping them happy is the other half.

1. Start with a short call. Ask what problem they're solving, who their customers are, and what a good result looks like.
2. Send a clear proposal summarizing what you heard and what you'll deliver.
3. Show progress early. A rough version in the first week prevents nasty surprises.
4. Reply within a day. Fast, calm communication is the easiest way to stand out.
5. Under-promise, over-deliver. Give yourself a buffer on deadlines.
6. Hand over cleanly. Share the files, explain how to update things, and make sure they own their accounts.
7. Ask for a testimonial while they're happy, and for permission to add the project to your portfolio.

If you use AI tools while building, treat their output the way you would a stranger's code: review it, test it, and never paste client data or secrets into places they shouldn't go.

11. Mistakes to Avoid

• Saying yes to everything. A project you can't deliver hurts more than turning it down.
• No written agreement. It's how small misunderstandings become big fights.
• Underpricing wildly. It exhausts you and resets clients' expectations.
• Scope creep. "Can you just add one more small thing?" repeated ten times is a whole new project.
• Going silent when things get hard. Communicate early if you're running late.
• Overloading yourself. Balance projects with classes and rest, or you'll hit the burnout wall I wrote about in a recent post.
• Building before understanding. Ask questions first, or you'll rebuild the same thing twice.

12. After Client One

The first project is a launchpad, not the finish line:

• Add it as a case study to your portfolio, with the problem, your solution, and the result
• Ask the client if they know anyone else who might need similar help
• Collect the testimonial and use it everywhere
• Raise your prices a little with each new project
• Decide whether you enjoy this kind of work, since freelancing isn't for everyone, and that's perfectly fine

Your Two-Week Starter Plan

Days 1 to 3: Pick your pond and write your one-sentence offer.
Days 4 to 7: Build one strong sample that matches the offer.
Days 8 to 10: List 20 possible clients: people you know and local businesses.
Days 11 to 14: Send 10 thoughtful, personalized messages, and follow up on each.

You won't hear back from everyone. You only need one yes.

Let's Connect

I'm Prayush Adhikari, currently grinding through computer engineering, leading an IT club, and building my own company on the side. I write about Linux, productivity, and the honest side of being a developer.

If you send your first pitch after reading this, tell me in the comments. I'd like to know how it goes.

• LinkedIn: linkedin.com/in/adhikareeprayush
• GitHub: github.com/adhikareeprayush
• Portfolio: prayushadhikari.com.np

What should I write next: how to build a career network when you don't know anyone in tech, or side project ideas that actually impress recruiters?